Moninger at 497-6435, Andrea Ignatowski at 497-5200, or Rich Fozzard at 
	-6011. 
	 

Site location: 
	 
	New Jersey Power and Light 
	Sayreville Generating Station 
	River Road 
	Sayreville, NJ  08872 
	Ph: (908)-257-0133, ext 304 for on-site contact: Dave Ramsden 
	 
	Stack of combustion turbine (CT) #4 (furthest south) is approximately: 
	deg 28' 33.4" N   74deg 21' 09.3" W  (from USGS 7.5min topo) 
	 
	 

DOWNWASH contacts: 
	 
	Rick Osa	414-785-5951		STMI, DOWNWASH program manager 
	Norm Bowne	203-657-8910		ENSR, field program manager 
	Lloyd Schulman	508-371-4269		Sigma, ASTER PI, modeler 
	Norm Nielsen	415-859-2841		SRI, LIDAR 
	Dave Ramsden	908-257-0133, ext 304	Sayreville plant engineer  
	 

Fast T cals 
	 
	I have adjusted t.4m.cav1 and t.4m.far.  Since archiving has just 
	started, the t.4m.far cal is now saved in the data stream (about  
	:42).  We'll now calibrate t.10m.cav1 and then note the times 
	that t.4m.far and t.10m.far are saved in the data stream. 
	 

Fast T cals 
	 
	I have adjusted t.4m.cav1 and t.4m.far.  Since archiving has just 
	started, the t.4m.far cal is now saved in the data stream (about  
	:42).  We'll now calibrate t.10m.cav1 and then note the times 
	that t.4m.far and t.10m.far (16:00) are saved in the data stream. 
	 

Fast T cals 
	 
	I have adjusted t.4m.cav1 and t.4m.far.  Since archiving has just 
	started, the t.4m.far cal is now saved in the data stream (about  
	:42).  We'll now calibrate t.10m.cav1 and then note the times 
	that t.4m.far (16:05) and t.10m.far (16:00) are saved in the data stream. 
	 

Fast T cals 
	 
	I have adjusted t.4m.cav1 and t.4m.far.  Since archiving has just 
	started, the t.4m.far cal is now saved in the data stream (about  
	:42).  We'll now calibrate t.10m.cav1 and then note the times 
	that t.4m.far (16:05) and t.10m.far (16:00) are saved in the data stream. 
	 
	t.10m.up calibrated.  Cal cycle done (16:31). 
	 

uw sonic transducers changed 
	 
	Transducers Btop and Cbot on uw.10.up were bad.  Changed and reset (slightly) 
	threshold and gain settings.  Appears to be a lot better (about 1 spike/5 min), 
	but will wait for them to "settle" in a bit before getting serious about  
	'scope work.  This done about an hour ago. 
	 

ATI sonic work 
	 
	Have just gone through calib. procedure on both ati sonics, using 
	T=5C (from psycs on upwind).  However, neither "v" channel worked, 
	giving a flashing test light.  The channels appear to work somewhat, 
	but will need to do some 'scope work there too. 
	 

uw.10m.up zeros saved 
	 
	zeros done and saved into fast_cals/uw.10m.up.035.A,B,C. 
	To calculate zero for speed-of-sound, T=4.0C, rh=53%, p=1021.26mb. 
	(Thus speed-of-sound was:  
	  vpres <- 0.53*fun.satvp(4) 
	  mixr <- (0.622*vpres)/(1021.26-vpres) 
	  spec.hum <- mixr/(1+mixr) 
	  Tv <- (4+273.15)*(1+0.61*spec.hum) 
	  c <- 20.067*sqrt(Tv) 
	results in c = 334.34 m/s. 
	Pathlength for path A is 0.1999m, therefore counts should be  
	  0.1999/334.34 * 4 MHz * 16 up-and-down firings/sample = 38265 counts 
	 
	zero S was -26250 
	 

uw.10m.up zeros saved 
	 
	zeros done and saved into fast_cals/uw.10m.up.035.A,B,C. 
	To calculate zero for speed-of-sound, T=4.0C, rh=53%, p=1021.26mb. 
	(Thus speed-of-sound was:  
	  vpres <- 0.53*fun.satvp(4) 
	  mixr <- (0.622*vpres)/(1021.26-vpres) 
	  spec.hum <- mixr/(1+mixr) 
	  Tv <- (4+273.15)*(1+0.61*spec.hum) 
	  c <- 20.067*sqrt(Tv) 
	results in c = 334.34 m/s. 
	Pathlength for path A is 0.1999m, therefore counts should be  
	  0.1999/334.34 * 4 MHz * 16 up-and-down firings/sample = 38265 counts 
	 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.10m.up.035.A", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$a) 
	  zero A was -86 
	median(x$s) 
	  average S was -26250 (?) (not the "median", but the first values) 
	  thus zero S is 65536-26250=39286 - 38265 = 1021 (round to 1020) 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.10m.up.035.B", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$b) 
	  zero B was -2 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.10m.up.035.C", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$c) 
	  zero C was -67 
	 
	cal_files/uw.sonic.1 has just been updated. 
	 

uw.10m.up zeros saved 
	 
	zeros done and saved into fast_cals/uw.10m.up.035.A,B,C. 
	To calculate zero for speed-of-sound, T=4.0C, rh=53%, p=1021.26mb. 
	(Thus speed-of-sound was:  
	  vpres <- 0.53*fun.satvp(4) 
	  mixr <- (0.622*vpres)/(1021.26-vpres) 
	  spec.hum <- mixr/(1+mixr) 
	  Tv <- (4+273.15)*(1+0.61*spec.hum) 
	  c <- 20.067*sqrt(Tv) 
	results in c = 334.34 m/s. 
	Pathlength for path A is 0.1999m, therefore counts should be  
	  0.1999/334.34 * 4 MHz * 16 up-and-down firings/sample = 38265 counts 
	 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.10m.up.035.A", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$a) 
	  zero A was -86 
	median(x$s) 
	  average S was -26250 (?) (not the "median", but the first values) 
	  thus zero S is 65536-26250=39286 - 38265 = 1021 (round to 1020) 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.10m.up.035.B", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$b) 
	  zero B was -2 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.10m.up.035.C", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$c) 
	  zero C was -67 
	 
	cal_files/uw.sonic.1 has just been updated. 
	 
	Although this sonic still has a few spikes, we should be able to adjust 
	the levels slightly so these zeros will still be valid. 
	 

upwind tower erected about 30 min ago 
	 
	There was a period of about 30 minutes of adjusting level. 
	Booms were shot using sun/theodolite.  Angles to be entered 
	later by Steve or Gordon. 
	 

upwind tower erected about 30 min ago 
	 
	There was a period of about 30 minutes of adjusting level. 
	Booms were shot using sun (only partly cloudy)/theodolite.   
	Angles to be entered later by Steve or Gordon.   
	 
	Cosmos crashed during this time - apparently pretty soon after we 
	got out there to begin.  I just restarted archiving and covar. 
	 
	 

ATI sonics zeroed 
	 
	After finally grounding everything (a jury-rig, since the cav1 tower 
	is still down in the wrong location), the ATIs zeroed without any problems. 
	The few channels I looked at (u,v,w) on atik.10m.cav1 all had VERY 
	strong (12V) signals. 
	 

ATI sonics rezeroed 
	 
	While diagnosing the ATI spike problem (which turned out to be 
	interference between the two ATI sonic cables), we discovered 
	that I had associated the wrong electronics box with arrays. 
	Therefore, I've just rezeroed all ATI channels again. 
	 

uw.4m.far zeros saved 
	 
	zeros done and saved into fast_cals/uw.4m.far.036.A,B,C. 
	To calculate zero for speed-of-sound, T=6.4C, rh=55%, p=1010mb. 
	(Thus speed-of-sound was:  
	  vpres <- 0.55*fun.satvp(6.4) 
	  mixr <- (0.622*vpres)/(1010-vpres) 
	  spec.hum <- mixr/(1+mixr) 
	  Tv <- (6.4+273.15)*(1+0.61*spec.hum) 
	  cc <- 20.067*sqrt(Tv) 
	results in c = 335.85 m/s. 
	Pathlength for path A is 0.1999m, therefore counts should be  
	  0.1999/335.85 * 4 MHz * 16 up-and-down firings/sample = 38093 counts 
	 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.4m.far.036.A", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$a) 
	  zero A was 102 (not a very good value) 
	median(x$s) 
	  average S was -27042 (?) (not the "median", but by eye from histogram) 
	  thus zero S is 65536-27042=38494 - 38093 = 401 (round to 400) 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.4m.far.036.B", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$b) 
	  zero B was -211 (hist makes it look more like 211 rather than 210) 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.4m.far.036.C", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$c) 
	  zero C was 39 (not 40 from median) 
	 
	cal_files/uw.sonic.2 has just been updated. 
	 
	Will also update $ASTER/apps/calib/sonic_uw4a.c to have these values. 
	 

uw.10m.up zeros saved 
	 
	zeros done and saved into fast_cals/uw.10m.up.035.A,B,C. 
	To calculate zero for speed-of-sound, T=4.0C, rh=53%, p=1021mb. 
	(Thus speed-of-sound was:  
	  vpres <- 0.53*fun.satvp(4) 
	  mixr <- (0.622*vpres)/(1021-vpres) 
	  spec.hum <- mixr/(1+mixr) 
	  Tv <- (4+273.15)*(1+0.61*spec.hum) 
	  cc <- 20.067*sqrt(Tv) 
	results in c = 334.34 m/s. 
	Pathlength for path A is 0.1987m, therefore counts should be  
	  0.1987/334.34 * 4 MHz * 16 up-and-down firings/sample = 38036 counts 
	 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.10m.up.035.A", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$a) 
	  zero A was -86 
	median(x$s) 
	  average S was -26250 (?) (not the "median", but the first values) 
	  thus zero S is 65536-26250=39286 - 38036 = 1250 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.10m.up.035.B", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$b) 
	  zero B was -2 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.10m.up.035.C", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$c) 
	  zero C was -67 
	 
	cal_files/uw.sonic.1 has just been updated. 
	 
	Although this sonic still has a few spikes, we should be able to adjust 
	the levels slightly so these zeros will still be valid. 
	 

Krypton A/D channel seems okay 
	 
	I just used the Datel dial-a-volt to pump a few voltages 
	directly into the A/D channel at the 18-pin connector at 
	the ADAM front panel.  I read the voltages out using "prep" 
	with a prep.config which specified a normal linear gain. 
	in:	out: 
	 0.000V	 0.002V 
	 1.000V  0.998V 
	-1.000V -0.994V 
	 
	This is close to consistent with a bias of 3 mv, and a gain 
	low by 0.5%.   
	 
	I don't think this is bad enough to have caused the high humidities 
	we are seeing.  Note that the Krypton is reading about 0.168V - this 
	seems quite low. 
	 

t.10m.up interrupted 
	 
	Note that the signal from t.10m.up was interrupted when I broke into 
	the 18pin A/D cable about 15min ago. 
	 

t.10m.up interrupted 
	 
	Note that the signal from t.10m.up was interrupted when I broke into 
	the 18pin A/D cable about 15min ago. 
	 
	 
	 

boom angles from upwind 
	 
	Done yesterday by Steve S. and Gordon: 
	 
	UPWIND:    measured       actual (reciprocal) 
	uw.10m.up  155deg 07'     335deg 07' 
	prop.6m.up 155deg 09'20"  335deg 09'20" 
	prop.2m.up 155deg 08'20"  335deg 08'20" 
	 
	I'm not sure these were measured correctly - Gordon is working 
	on the far tower measurements several ways to resolve this. 
	 

boom angles from upwind 
	 
	Done yesterday by Steve S. and Gordon: 
	 
	UPWIND:    measured       actual (reciprocal) 
	uw.10m.up  155deg 07'     335deg 07' 
	prop.6m.up 155deg 09'20"  335deg 09'20" 
	prop.2m.up 155deg 08'20"  335deg 08'20" 
	 
	I'm not sure these were measured correctly - Gordon is working 
	on the far tower measurements several ways to resolve this. 
	 
	Note that these have not yet been entered - I'm going to try 
	to put them in the prop HC11's now. 
	 

boom angles from upwind 
	 
	Done yesterday by Steve S. and Gordon: 
	 
	UPWIND:    measured       actual (reciprocal) 
	uw.10m.up  155deg 07'     335deg 07' 
	prop.6m.up 155deg 09'20"  335deg 09'20" 
	prop.2m.up 155deg 08'20"  335deg 08'20" 
	 
	I'm not sure these were measured correctly - Gordon is working 
	on the far tower measurements several ways to resolve this. 
	 
	Note that these have not yet been entered - I'm going to try 
	to put them in the prop HC11's now. 
	 
	P.S. Entered D3351 into prop.2m.up (cosmos:204)  
	     and D3352 into prop.6m.up (cosmos:205) at about 15:07. 
	 

far boom angles 
	                                                          reciprocal: 
	uw.4m.far (first shot)   115deg 44'10" 
	          (second shot)  115deg 49'10" (use this one)     295.8 
	prop.10m.far             116deg 07'40"                    296.1 
	 
	Value entered into prop (ragwort:201) about 16:15. 
	 
	Will also enter angles into sonic.config.S. 
	 
	Note that it is necessary to move the theodolite (requiring a new 
	sun angle shoot) to get boom angle readings.  This was not done 
	on upwind, so we'll probably reshoot these. 
	 

Have just restarted covar on ragwort 
	 
	This done so that covar knows about the latest cal_file entry 
	with sonic zeros for uw.4m.far.  (last night's daily plots showed 
	a bias of 20 cm/s in w). 
	 

New shoot of upwind 
	 
	Gordon just repeated the shoot of the upwind tower, given the "new" 
	procedure of aligning directly with the booms.  He now gets: 
	 
	uw.10m.up	155deg 48' 00"  335.8deg 
	prop.6m.up	155deg 32' 30"  335.5deg 
	prop.2m.up	155deg 34' 10"  335.6deg 
	 
	I'll go ahead and reset the prop HC11's and sonic.config.S stuff with 
	these. 
	 

Krypton tests: 
	 
	I have tried several things today: 
	 
	 - Powered up Krypton serial #1133 in trailer - get NO voltage on the 
	    output. (I checked and do get +12VDC inside the electronics box.) 
	    I don't see a "glow" in either lamp. 
	    Thus, I think #1133 is dead. 
	 - Reseated all connectors (even on the tower) on #1101.  No change. 
	 - Swapped in electronics box for #1133 with #1101.  No large change 
	    (hard to tell exactly since I was trying to read the DVM on the 
	    ground from 10m up). 
	 - Didn't see a "glow" in either tube of #1101. 
	    Thus, I think #1101 has a weak source tube. 
	 
	We should send #1133 back to Campbell to have them get it running again, 
	and then swap back with #1101. 
	 

Size of archive files 
	 
	 
	With most instruments up and running, except for the psyc's on cav1  
	and the ENSR data loggers, the size of the archive file is 192 Mbyte/day. 
	 
	 
	 

UW sonic ID's wrong 
	 
	I've just realized that the ID's for the UW sonics are wrong. 
	(This is partly my fault, since I told Kurt I "didn't know" which 
	electronics box went with which array, but one box should have 
	gone with one array.)  The triangular array is always UW1, (since 
	it was built first) and the cal_files, uw.sonic.1 and uw.sonic.2 
	assume this.  I've just reprogrammed the HC11 IDs to reflect the 
	correct setup, and will check that the labeling of the boxes is 
	correct. 
	 
	I'll now recompute the zero calibrations of a few days ago, since 
	the pathlength used in the speed-of-sound zero calibration was 
	wrong.  I'll also make sure prep.config is pointing to the 
	correct files. 
	 
	Sometime, we should check the FOOTPRINT logbook to make sure that 
	this switch wasn't in effect then (causing wrong angles to be 
	used by the calibration routines). 
	 

uw.10m.up zeros saved ($$ rev 2/7/94 $$) 
	 
	zeros done and saved into fast_cals/uw.10m.up.035.A,B,C. 
	To calculate zero for speed-of-sound, T=4.0C, rh=53%, p=1021mb. 
	(Thus speed-of-sound was:  
	  vpres <- 0.53*fun.satvp(4) 
	  mixr <- (0.622*vpres)/(1021-vpres) 
	  spec.hum <- mixr/(1+mixr) 
	  Tv <- (4+273.15)*(1+0.61*spec.hum) 
	  cc <- 20.067*sqrt(Tv) 
	results in c = 334.34 m/s. 
	Pathlength for path A is 0.1987m, therefore counts should be  
	$$$$ wrong $$$$$  0.1987/334.34 * 4 MHz * 16 up-and-down firings/sample = 38036 counts 
	$$$$ right $$$$$  0.1999/334.34 * 4 MHz * 16 up-and-down firings/sample = 38265 counts 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.10m.up.035.A", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$a) 
	  zero A was -86 
	median(x$s) 
	  average S was -26250 (?) (not the "median", but the first values) 
	$$$$$ wrong $$$$$  thus zero S is 65536-26250=39286 - 38036 = 1250 
	$$$$$ right $$$$$  thus zero S is 65536-26250=39286 - 38265 = 1021 (round to 1020) 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.10m.up.035.B", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$b) 
	  zero B was -2 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.10m.up.035.C", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$c) 
	  zero C was -67 
	 
	$$$$ wrong $$$$ cal_files/uw.sonic.1 has just been updated. 
	$$$$ right $$$$ cal_files/uw.sonic.2 has just been updated. 
	 
	Although this sonic still has a few spikes, we should be able to adjust 
	the levels slightly so these zeros will still be valid. 
	 

uw.4m.far zeros saved ($$ rev 2/7/94 $$) 
	 
	zeros done and saved into fast_cals/uw.4m.far.036.A,B,C. 
	To calculate zero for speed-of-sound, T=6.4C, rh=55%, p=1010mb. 
	(Thus speed-of-sound was:  
	  vpres <- 0.55*fun.satvp(6.4) 
	  mixr <- (0.622*vpres)/(1010-vpres) 
	  spec.hum <- mixr/(1+mixr) 
	  Tv <- (6.4+273.15)*(1+0.61*spec.hum) 
	  cc <- 20.067*sqrt(Tv) 
	results in c = 335.85 m/s. 
	Pathlength for path A is 0.1999m, therefore counts should be  
	$$$$ wrong $$$$  0.1999/335.85 * 4 MHz * 16 up-and-down firings/sample = 38093 counts 
	$$$$ right $$$$  0.1987/335.85 * 4 MHz * 16 up-and-down firings/sample = 37865 counts 
	 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.4m.far.036.A", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$a) 
	  zero A was 102 (not a very good value) 
	median(x$s) 
	  average S was -27042 (?) (not the "median", but by eye from histogram) 
	$$$$ wrong $$$$  thus zero S is 65536-27042=38494 - 38093 = 401 (round to 400) 
	$$$$ right $$$$  thus zero S is 65536-27042=38494 - 37865 = 629 (round to 630) 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.4m.far.036.B", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$b) 
	  zero B was -211 (hist makes it look more like 211 rather than 210) 
	x <- scan("/home/aster/projects/DOWNWASH94/fast_cals/uw.4m.far.036.C", 
		list(id="",nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	median(x$c) 
	  zero C was 39 (not 40 from median) 
	 
	$$$$ wrong $$$$ cal_files/uw.sonic.2 has just been updated. 
	$$$$ right $$$$ cal_files/uw.sonic.1 has just been updated. 
	 
	Will also update $ASTER/apps/calib/sonic_uw4a.c to have these values. 
	 

uw.4m.far speed-of-sound bias 
	 
	counts approx -27000 +/-50 
	 
	temp approx 6.5 C 
	rh approx 42 % 
	Pres 1020 mb 
	 
	 

speed-of-sound biases 
	 
	uw.4m.far 
	 
	counts approx -27000 +/-50 
	 
	temp approx 6.5 C 
	rh reads 42 %, but adjust by bias (noticed from dailyplots) of 2% = 40% 
	Pres 1020 mb 
	 
	c = 335.8 
	counts should be 37868 @ 0.1987 m 
	bias = 65536-27000 = 38536-37868 = 668 (round to 650) 
	 
	HOWEVER, values changed to -26550 without chamber. 
	Therefore, the chamber appears to alter the thermal environment 
	of the path.  The correct zero value should be 650+450=1100. 
	 
	uw.10m.up 
	 
	Similarly, without the chamber, uw.10m.up reads: -26350. 
	at 10m, T=6.5 C also 
	RH = 38 % (about the same as 40, above) 
	c = 335.8 
	counts should be 38097 @ 0.1999 m 
	bias = 65536-26350 = 39186-38097 = 1089 (round to 1100) 
	 

Snow started about 1 hour ago 
	 
	It started sticking almost immediately - now about 1/2". 
	See the ORG.700.rain signal for exact time - it is seeing 
	this stuff easily. 
	 

pyg.in battery replaced 
	 
	Two batteries were waiting for me at the hotel last night, so 
	I've just replaced the one in the Eppley Pyrgeometer and have 
	just reinstalled it.  Values from cshow are about 250, so I 
	assume it's working. 
	 

pyg.in battery replaced 
	 
	Two batteries were waiting for me at the hotel last night, so 
	I've just replaced the one in the Eppley Pyrgeometer and have 
	just reinstalled it.  Values from cshow are about 250, so I 
	assume it's working. 
	 
	I notice that the dome and case temperatures are cooling quickly 
	from being inside the trailer.  It may be a good idea to wait  
	another 1/2 hour or so before trusting the data from this  
	instrument.  (Also note that the snow melted on the dome, which 
	presumably is above freezing. I didn't notice snow on the psp.in.) 
	 

3 fast T's died in snow 
	 
	I've just pulled the t.4m.cav1 (this tower is still not erected) 
	probe to avoid having it be the last casualty. 
	 

Fast T cals 
	 
	I have adjusted t.4m.cav1 and t.4m.far.  Since archiving has just 
	started, the t.4m.far cal is now saved in the data stream (about  
	:42).  We'll now calibrate t.10m.cav1 and then note the times 
	that t.4m.cav1 (16:05) and t.10m.cav1 (16:00) are saved in the data stream. 
	 
	t.10m.up calibrated.  Cal cycle done (16:31). 
	 

morning status 
	 
	Weather: High overcast. Not snowing now. Snow depth along transect E to fence:  
	         16, 10, 10, 15, and 12 cm.  Elsewhere, some drifts are much (3 times?) 
	         higher.  Also note that flooding has brought water up to cover the  
	         baseplates of the radiation sawhorse.   
	 
	Plant:   CT4 still down with crane present.  No work since about 0900 (local) 
	         yesterday due to "inclement weather" clause in worker's contract. 
	 
	cav1/cav2:  cav1 still not staked, laying down beside cav2.   
		    cav2 is down in position 
	  t.4m.cav1: Probe removed during snow yesterday 
	  t.10m.cav1: Probe broke during snow yesterday 
	  psycs: Not installed yet since tower down 
	  atik.4m.cav1:  Working, some spikes (may be software spikes) 
	  atik.10m.cav1: Working, some spikes (may be software spikes) 
	  NOx.ENSR: Not plugged in, since crashes marigold software (Gordon is working 
	       on this).  Logger is running with analyzers in our data trailer. 
	  props: Working 
	  met.ENSR: Not deployed 
	 
	far: Tower up 
	  t.4m.far: Probe broke during snow yesterday 
	  rain: Working?  showed snow yesterday 
	  radiometers:  Working.  Battery in pyg.in replaced yesterday.   
	       dailyplot shows sumrad about 20 W/m2 (constant, throughout 
	       day and night) while net is about 0.  I trust net in this case, thus 
	       there probably is a problem with one of the pyrgeometers. 
	       Is a new calibration of pyg.in needed with the new battery? 
	       Note from earlier comment that radiometers are above ice now. 
	  uw.4m.far: Working.  A fair number of spikes, hopefully just snow related. 
	  prop: Working. 
	 
	upwind: Tower up 
	  t.10.up: Probe broke during snow yesterday. 
	  h2o.10m.up: Still giving high humdities (20 g/kg) due to low voltage output. 
	       Our other sensor (#1133) is being worked on by Campbell now and should 
	       be back by Monday. 
	  psycs: Working. dayplots still show a bias of about 3% on psyc.6m.up 
	       relative to the others.  I have a call into Steve S. to assist with 
	       this. 
	  baro: Working. 
	  props: Working. 
	  uw.10m.up: Working. No spikes recently! 
	 
	Rooftop logger: Installed Monday afternoon.  Should be "dumped" tomorrow. 
	  Still not a weathertight installation - we'll bring a roll of tape when 
	  we go up tomorrow. 
	 
	   
	 

Playing with psycs 
	 
	I've just put a new psych measuring at 0.5m on upwind and connected it 
	as cosmos:201 (replacing psyc.6m.up).  We'll run this unit for 2-24 hours 
	to see if its RH matches the 2m and 10m units.  If it does, 
	we'll move it to 6m and replace the "innards" with one of the spares 
	for use on cav1. 
	 

Processing fast T cals 
	 
	Here are the results of my new fastT calibration routine. 
	The resulting coefficients are to be entered into a cal_file 
	(and prep.config changed to use td_linear), which I'll do after  
	exiting logbook. 
	 
	 

Processing fast T cals 
	 
	Here are the results of my new fastT calibration routine. 
	The resulting coefficients are to be entered into a cal_file 
	(and prep.config changed to use td_linear), which I'll do after  
	exiting logbook. 
	 
	[Sorry for all the arguments in this fun.fastT.cal.get function -  
	Gordon may make a routine to lookup adam, channel, and archive file root 
	from the did.name sometime in the future to eliminate some of them. 
	Note some manual work interpreting the output - but here are some examples.] 
	 
	t.4m.cav1: 
	 
	fun.fastT.cal.get("t.4m.cav1","marigold",100,35,16,02,"cav/fast035160000", 
		nummin=2) 
	gain = 0.001508249 
	 
	t.10m.cav1: 
	 
	Need to run this twice since cal split between archive files; 
	 
	dT1 <- fun.fastT.cal.get("t.10m.cav1","marigold",101,35,15,59, 
		"cav/fast035153540",nummin=1) 
	dT2 <- fun.fastT.cal.get("t.10m.cav1","marigold",101,35,16,00, 
		"cav/fast035160000",nummin=1) 
	gain <- (50/32768)*(5/mean(abs(c(dT1[5:10],dT2[1:4])))) 
	gain = 0.001505667 
	 
	t.4m.far: 
	 
	dT <- fun.fastT.cal.get("t.4m.far","ragwort",100,35,15,41, 
		"far/fast035153519",nummin=2) 
	gain <- (50/32768)*(5/mean(abs(dT[4:13]))) 
	gain = 0.001496293 
	 
	t.10m.up: 
	 
	dT <- fun.fastT.cal.get("t.10m.up","cosmos",100,35,16,26, 
		"upwind/fast035160000",nummin=2) 
	gain <- (50/32768)*(5/mean(abs(dT[5:13]))) 
	gain = 0.001528624 
	 

Misc problems: 
	 
	. There is a minor leak around the top of the "boot" on the chem trailer 
	   side. 
	 
	. While attempting to shovel snow off the roof (near the boot), I found out  
	   that the roof has a thin coating, which I scraped off of a few rivet heads 
	   on the chem trailer near the door.  I attempted to patch them with RTV, 
	   but it didn't stick too well given that it was snowing at the time and 
	   cold. 
	 
	. Also, the chem trailer air conditioner has been making weird sounds -  
	   like a bearing is bad in the fan.  The fan appears to stop and then 
	   there are strange smells while on "heat".  Thus, we've been leaving 
	   it off altogether.  The data trailer unit appears to heat both adequately. 
	 

morning status 
	 
	Weather: High overcast. Not snowing now. Snow depth along transect E to fence:  
	         16, 10, 10, 15, and 12 cm.  Elsewhere, some drifts are much (3 times?) 
	         higher.  Also note that flooding has brought water up to cover the  
	         baseplates of the radiation sawhorse.   
	 
	Plant:   CT4 still down with crane present.  No work since about 0900 (local) 
	         yesterday due to "inclement weather" clause in worker's contract. 
	 
	cav1/cav2:  cav1 still not staked, laying down beside cav2.   
		    cav2 is down in position 
	  t.4m.cav1: Probe removed during snow yesterday 
	  t.10m.cav1: Probe broke during snow yesterday 
	  psycs: Not installed yet since tower down 
	  atik.4m.cav1:  Working, some spikes (may be software spikes) 
	  atik.10m.cav1: Working, some spikes (may be software spikes) 
	  NOx.ENSR: Not plugged in, since crashes marigold software (Gordon is working 
	       on this).  Logger is running with analyzers in our data trailer. 
	  props: Working 
	  met.ENSR: Not deployed 
	 
	far: Tower up 
	  t.4m.far: Probe broke during snow yesterday 
	  rain: Working?  showed snow yesterday 
	  radiometers:  Working.  Battery in pyg.in replaced yesterday.   
	       dailyplot shows sumrad about 20 W/m2 (constant, throughout 
	       day and night) while net is about 0.  I trust net in this case, thus 
	       there probably is a problem with one of the pyrgeometers. 
	       Is a new calibration of pyg.in needed with the new battery? 
	       Note from earlier comment that radiometers are above ice now. 
	  uw.4m.far: Working.  A fair number of spikes, hopefully just snow related. 
	  prop: Working. 
	 
	upwind: Tower up 
	  t.10.up: Probe broke during snow yesterday. 
	  h2o.10m.up: Still giving high humdities (20 g/kg) due to low voltage output. 
	       Our other sensor (#1133) is being worked on by Campbell now and should 
	       be back by Monday. 
	  psycs: Working. dayplots still show a bias of about 3% on psyc.6m.up 
	       relative to the others.  I have a call into Steve S. to assist with 
	       this. 
	  baro: Working. 
	  props: Working. 
	  uw.10m.up: Working. No spikes recently! 
	 
	Rooftop logger: Installed Monday afternoon.  Should be "dumped" tomorrow. 
	  Still not a weathertight installation - we'll bring a roll of tape when 
	  we go up tomorrow. 
	 
	   
	 

morning status 
	 
	Weather: High cirrus overcast, some lower clouds, snow still on ground 
	 
	Plant: CT4 still down - maybe today?! 
	 
	cav1/cav2:  Both towers still lying down.  Data not being archived or 
	        "covar"ed since Gordon is developing software on marigold. 
	  t.4m.cav1:  Still no probe - we should replace these today 
	  t.10m.cav1: Still no probe - we should replace these today 
	  psycs: Not connected 
	  atik.4m.cav1: ? 
	  atik.10m.cav1: ? 
	  NOx.ENSR: Operating, .far signals are real. 
	  props: ? 
	  met.ENSR: Not installed 
	 
	far: Tower up 
	  t.4m.far: Still no probe - we should replace these today 
	  rain: Working.  Showed snow yesterday. 
	  radiometers:  All working.  pyg.in cals should be good now 
	  uw.4m.far: Working.  Had some spikes last night. (I count 25.) 
	  prop: Working 
	 
	upwind: Tower up 
	  t.10.up: Still no probe - we should replace these today 
	  h2o.10m.up: Operating.  Signal level low.  Waiting for replacement 
	  psycs: Working.  The 6m level is still connected to a unit at 0.5m.  We  
	        should move this unit up to 6m today. 
	  baro: Working.  Pressure is rising! 
	  props: Working. 
	  uw.10m.up: Working.  Had some spikes last night. (I count 18.)  tc is low. 
	 
	Rooftop logger:  Needs to be dumped today.  We should make a serial cable 
	  to avoid climbing the roof.  Also will bring tape to weatherize the box 
	  better. 
	 

All towers up! 
	 
	cav1 and cav2 were erected about 1 hour ago, and signals have just been 
	reconnected.  Marigold is coming up now and archiving and covars will be 
	started. 
	 
	Note: 
	psyc at 2m is not in, since I haven't changed out the "innards" with 
	a replacement (hopefully, with no RH bias). 
	 
	t.10m.cav1 has not been calibrated. 
	 
	We're going back as soon as marigold behaves itself. 
	 

morning status 
	 
	Sorry we didn't get this done yesterday - my mind was frozen by the sleet/snow. 
	 
	Today Gordon and I are taking off to go to Manhatten, since the weather still 
	isn't conducive to working on critical items (i.e., no sun for theodolite 
	shoot.) 
	 
	Weather: Overcast, LOTS of snow on the ground from yesterday and the previous  
	 	night (line to the fence eastward: 28, 29, 21, 28, 24, 25 cm deep). 
	 
	Plant:  Hasn't operated yet that we`ve seen (or heard) 
	 
	cav1/cav2:  Both towers need to be leveled with theodolite (they look pretty good  
		using the carpenter's level) 
	  t.4m.cav1: Broken. 
	  t.10m.cav1: Broken. 
	  psycs: Working. Dailyplots show that the cav1 profile is quite different 
		from upwind.  This might be real. 
		psyc.2m.cav1 is really only at about 1.8m - the highest I could 
		reach without climbing the icy tower. 
	  atik.4m.cav1:  Working.  Some spikes (100?) overnight, but looks okay now. 
	  atik.10m.cav1:  Dead.  Serial output weird.  ATI is expressing a new CPU board 
		to arrive Monday. 
	  NOx.ENSR: Working.  All lines connected at appropriate heights as of 
		the night before last.  Reporting 5 minute values 
	  props:  Working. 
	  met.ENSR: Working.  Tower installed yesterday about noon.  Also reporting 
		5 minute values. 
	 
	far:  
	  t.4m.far: Broken. 
	  rain: Working.  There was some precip yesterday. 
	  radiometers: Working.  I think we should try to get a real calibration for 
		dome and case pyg.in temperatures, since still some (albeit small)  
	 	differences with net/sumrad 
	  uw.4m.far:  Working.  Some (50?) spikes last night, probably precip related. 
	  prop: Working. 
	 
	upwind:  
	  t.10.up: Broken. 
	  h2o.10m.up: Working with low output.  Still waiting for the repaired unit 
		from Campbell.  (Should arrive Monday?) 
	  psycs: Working.  Dailyplots show that the temperature in the replaced psyc.6m.up 
		may be a bit (0.1 C?) high.  RH is still a bit high (1%), but pretty close. 
	  baro: Working.  Pressure is rising. 
	  props: Working. 
	  uw.10m.up: Working. Some (20?) spikes last night. 
	 
	Rooftop logger: Dumped yesterday about 3pm local.  My serial cable didn't work - 
		we might try some 4-5, 8-20 jumpering. 
	 

morning status (unchanged since yesterday) 
	 
	Weather: Overcast/hazy.  Intermittent freezing rain.  No new snow on the  
		ground. 
	 
	Plant:  Still hasn't run.  Ops for tomorrow cancelled. 
	 
	Other: We missed the conference call this morning because we forgot and 
		had a leisurely Sunday breakfast.  We'll remember next time. 
	 
	Trailer:  The fan on the chem trailer still squeals, so we haven't turned 
		it on.  The sink tanks may have frozen because of this, so we aren't 
		using it.  The boot is still leaking, so I've chipped the ice  
		(1" thick) out of the bottom and drilled a hole to let melting ice 
		drip out. 
	 
	cav1/cav2:  Still need to be theodolite leveled.  We'll do this today. 
	  t.4m.cav1: Broken. 
	  t.10m.cav1: Broken. 
	  psycs: Working.  Dailyplots show higher temps (and more variable) than  
		upwind.  2m.cav1 had lower (2%) RH for most of yesterday than all  
		other psychs. 
	  atik.4m.cav1:  Working.  Spikes overnight, may be due to lack of grounding. 
		We'll do this today. 
	  atik.10m.cav1:  Off.  Waiting for CPU card from ATI (tomorrow).   
		(sonic dailyplots aren't coming out, apparently since this is down) 
	  NOx.ENSR: On. 
	  props: Working.   
	  met.ENSR: On. 
	 
	far:  
	  t.4m.far: Broken. 
	  rain: Working.  Measured some overnight. 
	  radiometers:  Working. sumrad-net shows larger differences during day than  
		night, so some of the difference is due to short wave radiation. 
	  uw.4m.far:  Working.  Order of 50 spikes overnight, none now. 
	  prop: Working. 
	 
	upwind:  
	  t.10.up: Broken. 
	  h2o.10m.up:  Still waiting for Campbell replacement.  Many spikes (rain) last 
		night. 
	  psycs: Working.  Still not quite monotonic T profiles, though errors would 
		be less than 0.1 C.  RH differences are less than 1%. 
	  baro: Working.  Pressure falling. 
	  props: Working. Comparison between these is better than any other props. 
	  uw.10m.up: Working.  Lots of spikes last night. 
	 
	Rooftop logger: Needs to be dumped by Tuesday afternoon.  Monday would be 
		better. 
	 
	 

finally raised psyc.2m.cav1 to 2m 
	 
	This done about an hour ago. 
	It had been about 1.8m - as high as I could reach in the snow. 
	 

cav1 and cav2 towers leveled with theodolite 
	 
	Gordon and I just spent the last 3 hours doing this. 
	 

cav1 tower grounded 
	 
	This should improve performance from atik.4m.cav1. 
	 

prop.10m.far bad 
	 
	Its giving speeds which are quite low most of the time over 
	today (44) and the early part of yesterday.  The collar is 
	spinning along with the prop, so it is not a mechanical problem. 
	We've also cycled power twice.  Thus, tomorrow, we will have to 
	swap this unit out.  Hopefully, we have a replacement. 
	 

morning status 
	 
	Weather: Clouds on horizon, clear overhead.  Good weather predicted. 
		Snow on ground has crust. 
	 
	Plant: Hasn't operated yet. 
	 
	cav1/cav2: Leveled.  Still need theodolite shoot (today) 
	  t.4m.cav1: Broken. 
	  t.10m.cav1: Broken. 
	  psycs: Working.  psyc.2m.cav1 now at 2m.  I'm still not sure if 
		calibrations are right. 
	  atik.4m.cav1: Working.  I only see one obvious spike overnight. 
		(Now that it is grounded.)  Large w fluctuations probably 
		are real in the cavity. 
	  atik.10m.cav1: Waiting for CPU board from ATI (today).  Note tower vibration 
		sensed by level sensors. 
	  NOx.ENSR: Working.  Gordon is working on a dailyplot for this. 
	  props: Working. 
	  met.ENSR: Working.  Gordon is working on a dailyplot for this. 
	 
	far:  
	  t.4m.far: Broken 
	  rain:  
	  radiometers:   
	  uw.4m.far:  
	  prop:  
	 
	upwind:  
	  t.10.up: Broken 
	  h2o.10m.up:  
	  psycs:  
	  baro:  
	  props:  
	  uw.10m.up:  
	 
	Rooftop logger:  
	 

morning status 
	 
	Weather: Clouds on horizon, clear overhead.  Good weather predicted. 
		Snow on ground has crust. 
	 
	Plant: Hasn't operated yet. 
	 
	cav1/cav2: Leveled.  Still need theodolite shoot (today) 
	  t.4m.cav1: Broken. 
	  t.10m.cav1: Broken. 
	  psycs: Working.  psyc.2m.cav1 now at 2m.  I'm still not sure if 
		calibrations are right. 
	  atik.4m.cav1: Working.  I only see one obvious spike overnight. 
		(Now that it is grounded.)  Large w fluctuations probably 
		are real in the cavity. 
	  atik.10m.cav1: Waiting for CPU board from ATI (today).  Note tower vibration 
		sensed by level sensors. 
	  NOx.ENSR: Working.  Gordon is working on a dailyplot for this. 
	  props: Working. 
	  met.ENSR: Working.  Gordon is working on a dailyplot for this. 
	 
	far:  
	  t.4m.far: Broken.  Apparently switched to zero. 
	  rain: Working.  None yesterday. 
	  radiometers: Working.  Still viewing snow/ice 
	  uw.4m.far: Working.  Many (50?) spikes last night. 
	  prop: Working now.  Wasn't working last night.  May need to replace. 
	 
	upwind:  
	  t.10.up: Broken 
	  h2o.10m.up: Operating.  Still waiting for Campbell replacement (today?) 
	  psycs:  Working.  Still not sure about calibrations 
	  baro: Working.  Pressure is rising. 
	  props: Working. 
	  uw.10m.up: Working.  About 14 spikes last night. 
	 
	Rooftop logger: Should be dumped today, at least by tomorrow pm. 
	 

Sonic and Prop azimuths 
	 
	Shot orientation of ATI sonics on cav1 tower: 
		Sighted on V transducers 
		10m	128 deg 34 min 20 sec 
		 6m	127 deg 18 min 45 sec 
	 
	Shot prop orientation of props on cav2 tower: 
		Sighted from rear, aligned tower pipe with prop upright support. 
	 
							 
		2m	306 deg 00 min 20 sec 
		6m	306 deg 29 min 30 sec 
		10m	305 deg 47 min 10 sec 
	 
		The props were then initialized with these boom angles: 
			time	 
		2m	165533	306.0 
		6m	165635	306.5 
		10m	165723	305.8 
			 
	 
	 
	 
	 
	 
	 

Sonic and Prop azimuths 
	 
	Shot orientation of ATI sonics on cav1 tower: 
		Sighted on V transducers 
		10m	128 deg 34 min 20 sec 
		 6m	127 deg 18 min 45 sec 
	 
	 

Cav2 prop azimuths 
	 
	Shot prop orientation of props on cav2 tower: 
		Sighted from rear, aligned tower pipe with prop upright support. 
	 
							 
		2m	306 deg 00 min 20 sec 
		6m	306 deg 29 min 30 sec 
		10m	305 deg 47 min 10 sec 
	 
		The props were then initialized with these boom angles: 
			time	 
		2m	165533	306.0 
		6m	165635	306.5 
		10m	165723	305.8 
	 

Cav1 sonic azimuths 
	 
	Shot orientation of ATI sonics on cav1 tower: 
		Sighted on V transducers 
		10m	128 deg 34 min 20 sec 
		 6m	127 deg 18 min 45 sec 
	 
	 

Cav2 prop azimuths 
	 
	Shot prop orientation of props on cav2 tower: 
		Sighted from rear, aligned tower pipe with prop upright support. 
							 
		2m	306 deg 00 min 20 sec 
		6m	306 deg 29 min 30 sec 
		10m	305 deg 47 min 10 sec 
	 
		The props were then initialized with these boom angles: 
			time	 
		2m	165533	306.0 
		6m	165635	306.5 
		10m	165723	305.8 
	 

marigold temperature sensor added 
	 
	There was a bent pin on the 6-pin connector, which broke when 
	I bent it back.  I replaced the pin and reinstalled "hot". 
	 

atik.10m.cav1 back on line 
	 
	This happened about 12:20, when we received the new board from ATI. 
	It was necessary to do: 
	/OT 
	/AN 2 
	/AO 0 
	to get the correct settings. 
	 
	I had to bring marigold down to install the new channel_config 
	(since the ati channel was commented out.)  This took about 2 minutes. 
	 
	This sonic is not zeroed.  We will have to do this, but should also 
	record what the zeros are now, since we are now in a good run. 
	 

First CT run is now! 
	 
	They started the CT about 1130, and put it into low power mode about 1200. 
	The sonics and fast T see thermal spikes from the plume. 
	 

t.4m.cav1 installed 
	 
	This done to test whether sonic temperature spikes are real.  Most are! 
	We have not calibrated this, though I did put the switch through its various 
	settings 0-oper-cal-oper..., with 2 sec per setting just after replacing 
	the fast T.  This should have been about 1704. 
	 

t.4m.cav1 installed 
	 
	This was done about 1204 (local) so I was climbing during the IOP. 
	 
	This done to test whether sonic temperature spikes are real.  Most are! 
	We have not calibrated this, though I did put the switch through its various 
	settings 0-oper-cal-oper..., with 2 sec per setting just after replacing 
	the fast T.  This should have been about 1704. 
	 

Cav2 and ENSR prop azimuths 
	 
	Shot prop orientation of props on cav2 tower: 
		Sighted from rear, aligned tower pipe with prop upright support. 
							 
		2m	306 deg 00 min 20 sec 
		6m	306 deg 29 min 30 sec 
		10m	305 deg 47 min 10 sec 
	 
		The props were then initialized with these boom angles: 
			time	 
		2m	165533	306.0 
		6m	165635	306.5 
		10m	165723	305.8 
	 
		The ENSR vane boom was also shot: 
			102 deg 47 min 
	 

car moved about 5 minutes ago 
	 
	Our rental car was still reasonably close to the towers, so we've moved 
	it away.  There still are 3 JCP&L vehicles in front of CTs 3&4. 
	 

Cav2 and ENSR prop azimuths 
	 
	Shot prop orientation of props on cav2 tower: 
		Sighted from rear, aligned tower pipe with prop upright support. 
							 
		2m	306 deg 00 min 20 sec 
		6m	306 deg 29 min 30 sec 
		10m	305 deg 47 min 10 sec 
	 
		The props were then initialized with these (wrong) boom angles: 
			time	 
		2m	165533	226.0 
		6m	165635	226.5 
		10m	165723	225.8 
	 
		Note that these numbers are wrong! (Gordon's math error). 
		They should have been the following.  These were then 
		entered at these times: 
	 
			time	 
		2m	182240	306.0 
		6m	182300	306.5 
		10m	182320	305.8 
	 
	 
		The ENSR vane boom was also shot: 
			102 deg 47 min 
	 

Cav2 and ENSR prop azimuths 
	 
	Shot prop orientation of props on cav2 tower: 
		Sighted from rear, aligned tower pipe with prop upright support. 
							 
		2m	306 deg 00 min 20 sec 
		6m	306 deg 29 min 30 sec 
		10m	305 deg 47 min 10 sec 
	 
		The props were then initialized with these (wrong) boom angles: 
			time	 
		2m	165533	226.0 
		6m	165635	226.5 
		10m	165723	225.8 
	 
		Note that these numbers are wrong! (Gordon's math error). 
		They should have been the following, which were entered  
		into the props at these times: 
	 
			time	 
		2m	182240	306.0 
		6m	182300	306.5 
		10m	182320	305.8 
	 
	 
		The ENSR vane boom was also shot: 
			102 deg 47 min 
	 

OPS extended to 3pm local 
	 
	This is being done since the lidar is now fixed.  It is on location 
	as of about 5 min ago. 
	 

First CT run is now! 
	 
	They started the CT about 1130, and put it into low power mode about 1200. 
	The sonics and fast T see thermal spikes from the plume. 
	 
	 
	 

DOWNWASH contacts: 
	 
	Rick Osa	414-785-5951		STMI, DOWNWASH program manager 
	Norm Bowne	203-657-8910		ENSR, field program manager 
	Lloyd Schulman	508-371-4269		Sigma, ASTER PI, modeler 
	Norm Nielsen	415-859-2841		SRI, LIDAR 
	Dave Ramsden	908-257-0133, ext 304	Sayreville plant engineer  
			257-9545 - fax 
	 
	NJCPL 
	 

Cav2 and ENSR prop azimuths 
	 
	Shot prop orientation of props on cav2 tower: 
		Sighted from rear, aligned tower pipe with prop upright support. 
							 
		2m	306 deg 00 min 20 sec 
		6m	306 deg 29 min 30 sec 
		10m	305 deg 47 min 10 sec 
	 
		The props were then initialized with these (wrong) boom angles: 
			time	 
		2m	165533	226.0 
		6m	165635	226.5 
		10m	165723	225.8 
	 
		Note that these numbers are wrong! (Gordon's math error). 
		They should have been the following, which were entered  
		into the props at these times: 
	 
			time	 
		2m	182240	306.0 
		6m	182300	306.5 
		10m	182320	305.8 
	 
		The prop boom correction angles were entered into 
			$ASTER/cal_files/prop.cor, 
		so if we re-run covar, things should be hunky-dory. 
	 
		The ENSR vane boom was also shot: 
			102 deg 47 min 
	 

radiometer shadow 
	 
	Now from two diagonal legs of big power line tower. 
	 

radiometer shadow 
	 
	Now from two diagonal legs of big power line tower. 
	 
	 

atik.10m.cav1 zeroed 
	 
	This done about 40 minutes ago.  We'll have to look carefully at the data 
	during the first few seconds to get a zero to be used to adjust the data 
	from yesterday.  I forgot to take more data on these zeros. 
	 
	All sonics should ready now. 
	 

Fast T's zeroed 
	 
	t.10m.cav1 adjusted.  Cal sequence saved to archive 0825. 
	t.4m.cav1 adjusted.  Cal sequence saved to archive 0848. 
	 

t.4m.far zeroed 
	 
	New probe.  cals cycle done about 1535. 
	 

Fast T's zeroed 
	 
	t.10m.cav1 adjusted.  New probe.  Cal sequence saved to archive 0825. 
	t.4m.cav1 adjusted.  This was the probe we installed yesterday. 
	Cal sequence saved to archive 0848. 
	 

t.10m.up replaced 
	 
	New probe.  Adjusted.  Cal cycle done 1703 (GMT). 
	 

noon status 
	 
	Weather: Started out as mostly clear, but now overcast.  Light East winds, so 
		no downwash.  Still crusty snow on the ground. 
	 
	Plant: Ran yesterday from 1130-1615 (local).  1200-1500 was on low load (4 MW) 
		and 1500-1615 was at "baseline" load (62 MW). 
		We thought we saw downwash with high temperature bursts, but most of 
		these probably were the air from the heat exchanger.  NOx concentrations 
		were all low; however, the LIDAR claimed to see downwash.  Lloyd will 
		have fun sorting all this out. 
	 
		Today, we were to have run from 1100-1500, but the CT's fuel injecters 
		are clogged.  We are now waiting for them to be cleaned, which should 
		take an hour or so.  If they start up, it will be a "plume rise" ops, 
		which shouldn't need much from ASTER. 
	 
	cav1/cav2:  
	  t.4m.cav1: Replaced and calibrated this morning. 
	  t.10m.cav1:  Calibrated this morning. 
	  psycs: Working. 
	  atik.4m.cav1:  Working.  About 30 spikes since last night, most probably 
		while we were calibrating the fast T. 
	  atik.10m.cav1: Working.  About 30 spikes since last night, most probably 
		while we were calibrating the fast T. 
	  NOx.ENSR: Working. 
	  props:  Working 
	  met.ENSR: Working.  Yesterday, we changed the calibration routine to adjust 
		for the "arm" of the tower being at 102.8 deg, instead of 90 deg. 
	 
	far:  
	  t.4m.far: Replaced and calibrated this morning. 
	  rain: Working.  no precip recently. 
	  radiometers:  Working.  Dips indeed seem to be caused by shadowing.   
		(see logbook entry earlier this morning) 
	  uw.4m.far: Perfect - no spikes since last night, including the fast T cal! 
	  prop: Working. 
	 
	upwind:  
	  t.10.up: Replaced and calibrated this morning. 
	  h2o.10m.up: Operating, still waiting for replacement.  (Steve is working 
		on this from Boulder.) 
	  psycs: Working.  Dailyplots shows some weird things. 
	  baro: Working.  Pressure is falling. 
	  props: Working. 
	  uw.10m.up: Working.  About 15 spikes since last night.  Absolute  
		value of tc looks low.   
		Calibration routine has been throwing out data from this sonic, 
		even though data are good.  This is why fast.dailyplots haven't 
		been working.  Gordon is working on this. 
	 
	Rooftop logger: Dumped yesterday.  Data look okay.  Next time for dump 
		is Thurs./Fri. PM. 
	 

morning status 
	 
	Weather: Clear, light W winds.  Still snow on the ground, but it is melting. 
	 
	Plant: Never ran yesterday due to injector problem.  Scheduled to be 
		running now, but isn't. 
	 
	cav1/cav2:   
	  t.4m.cav1: Working. 
	  t.10m.cav1: Working. 
	  psycs: Working. 
	  atik.4m.cav1: Working.  No spikes since yesterday afternoon! 
	  atik.10m.cav1: Working.  No spikes since yesterday afternoon! 
	  NOx.ENSR: Working. 
	  props: Working. 
	  met.ENSR: Working. 
	 
	far:  
	  t.4m.far: Working. 
	  rain: Working.  (No rain.) 
	  radiometers: Working. 
	  uw.4m.far: Working. 12 spikes since yesterday afternoon. 
	  prop: Working. 
	 
	upwind:  
	  t.10.up: Working. 
	  h2o.10m.up: Operating.  Replacement will be shipped Thurs. 
	  psycs: Working. 
	  baro: Working.  Pressure is rising. 
	  props: Working. 
	  uw.10m.up: Working.  32 spikes since yesterday afternoon. 
	 
	Rooftop logger: Next backup due Thurs/Fri. 
	 

DOWNWASH contacts: 
	 
	Rick Osa	414-785-5951		STMI, DOWNWASH program manager 
	Norm Bowne	203-657-8910		ENSR, field program manager 
	Lloyd Schulman	508-371-4269		Sigma, ASTER PI, modeler 
	Norm Nielsen	415-859-2841		SRI, LIDAR 
	Dave Ramsden	908-257-0133, ext 304	Sayreville plant engineer  
			257-9545 - fax 
			525-8290 (at other plant) 
	NJCPL 
	 

Biases for atik.10m.cav1 
	 
	These are taken from the few seconds just before zeroing yesterday, since 
	we needed biases to apply to the day 45 run. 
	 
	:05:09.820 - 13:05:14.110  u-comp. range: 0.02 - 0.05, median 0.03 
	:05:53.860 - 13:05:57.460  v-comp. range: -0.17 - -0.13, median -0.15 
	:06:46.460 - 13:06:49.860  w-comp. range: -0.17 - -0.11, median -0.13 
	 
	I'll enter these in a file to be used in a time-dependent calibration. 
	 

Biases for atik.10m.cav1 
	 
	These are taken from the few seconds just before zeroing yesterday, since 
	we needed biases to apply to the day 45 run. 
	 
	Command used: 
	prep -Du.atik.10m.cav1:v.atik.10m.cav1:w.atik.10 
	m.cav1 -B 130400 -E 130700 -j 46 -r 0 -f fast046080000 -t | more 
	 
	Results: 
	:05:09.820 - 13:05:14.110  u-comp. range: 0.02 - 0.05, median 0.03 
	:05:53.860 - 13:05:57.460  v-comp. range: -0.17 - -0.13, median -0.15 
	:06:46.460 - 13:06:49.860  w-comp. range: -0.17 - -0.11, median -0.13 
	 
	I'll enter these in a file to be used in a time-dependent calibration. 
	 

t.4m.cav1 cal prior to yesterday's adjustment 
	 
	There wasn't time to do a good cal when we installed t.4m.cav1, but 
	I did go through a quick cal cycle without having the chamber installed. 
	The data are noisy, but I've just played around in S, and Gordon and 
	I agree that the jump corresponded to about 4.4 C.  Thus, the  
	gain should be 0.00173 for the period between installation at 
	 on jday 45 and the adjustment at about 1348 on jday 46.  I'll 
	update the cal_files after processing the jday 46 calibration. 
	 

Fast T's adjusted 
	 
	t.10m.cav1 adjusted.  New probe.  Cal sequence saved to archive 0825. 
	t.4m.cav1 adjusted.  This was the probe we installed yesterday. 
	Cal sequence saved to archive 0848. 
	 

t.4m.far adjusted 
	 
	New probe.  cals cycle done about 1535. 
	 

processed fast T cals from yesterday 
	 
	 

processed fast T cals from yesterday 
	 
	t.4m.cav1: 
	 
	dT <- fun.fastT.cal.get("t.4m.cav1","marigold",100,46,13,46, 
		"cav/fast046080000") 
	(50/32768)*(5/mean(abs(dT[4:13]))) = 0.001512266 
	 
	t.10m.cav1: 
	 
	dT <- fun.fastT.cal.get("t.10m.cav1","marigold",101,46,13,27, 
		"cav/fast046080000") 
	(50/32768)*(5/mean(abs(dT[3:14]))) = 0.001502217 
	 
	t.4m.far: 
	 
	 

All ADAMS crashed. 
	 
	This happened about 5 min. ago.  It took 2 tries, but Gordon got everything 
	going again.  Still don't know what caused it. 
	 

processed fast T cals from yesterday 
	 
	t.4m.cav1: 
	 
	dT <- fun.fastT.cal.get("t.4m.cav1","marigold",100,46,13,46, 
		"cav/fast046080000") 
	(50/32768)*(5/mean(abs(dT[4:13]))) = 0.001512266 
	 
	t.10m.cav1: 
	 
	dT <- fun.fastT.cal.get("t.10m.cav1","marigold",101,46,13,27, 
		"cav/fast046080000") 
	(50/32768)*(5/mean(abs(dT[3:14]))) = 0.001502217 
	 
	t.4m.far: 
	 
	dT <- fun.fastT.cal.get("t.4m.far","ragwort",100,46,15,32, 
		"far/fast046080000") 
	(50/32768)*(5/mean(abs(dT[3:12]))) = 0.001495845 
	 
	t.10m.up: 
	 
	dT <- fun.fastT.cal.get("t.10m.up","cosmos",100,46,16,03, 
		"upwind/fast046160000") 
	(50/32768)*(5/mean(abs(dT[3:14]))) = 0.001512296 
	 

processed fast T cals from yesterday 
	 
	The following values have all been entered into appropriate cal_files 
	 
	t.4m.cav1: 
	 
	dT <- fun.fastT.cal.get("t.4m.cav1","marigold",100,46,13,46, 
		"cav/fast046080000") 
	(50/32768)*(5/mean(abs(dT[4:13]))) = 0.001512266 
	 
	t.10m.cav1: 
	 
	dT <- fun.fastT.cal.get("t.10m.cav1","marigold",101,46,13,27, 
		"cav/fast046080000") 
	(50/32768)*(5/mean(abs(dT[3:14]))) = 0.001502217 
	 
	t.4m.far: 
	 
	dT <- fun.fastT.cal.get("t.4m.far","ragwort",100,46,15,32, 
		"far/fast046080000") 
	(50/32768)*(5/mean(abs(dT[3:12]))) = 0.001495845 
	 
	t.10m.up: 
	 
	dT <- fun.fastT.cal.get("t.10m.up","cosmos",100,46,16,03, 
		"upwind/fast046160000") 
	(50/32768)*(5/mean(abs(dT[3:14]))) = 0.001512296 
	 

morning status 
	 
	Weather: Clear, light W winds.  Still snow on the ground, but it is melting. 
	 
	Plant: Never ran yesterday due to injector problem.  Scheduled to be 
		running now, but isn't. 
		P.S. (1725 EST), the plant ended up running from 1030-1330 at 4 MW, 
		1330-1430 at 30 MW, and 1430-1630 at 62 MW, then spun down to shut 
		off at about 1650. 
	 
	cav1/cav2:   
	  t.4m.cav1: Working. 
	  t.10m.cav1: Working. 
	  psycs: Working. 
	  atik.4m.cav1: Working.  No spikes since yesterday afternoon! 
	  atik.10m.cav1: Working.  No spikes since yesterday afternoon! 
	  NOx.ENSR: Working. 
	  props: Working. 
	  met.ENSR: Working. 
	 
	far:  
	  t.4m.far: Working. 
	  rain: Working.  (No rain.) 
	  radiometers: Working. 
	  uw.4m.far: Working. 12 spikes since yesterday afternoon. 
	  prop: Working. 
	 
	upwind:  
	  t.10.up: Working. 
	  h2o.10m.up: Operating.  Replacement will be shipped Thurs. 
	  psycs: Working. 
	  baro: Working.  Pressure is rising. 
	  props: Working. 
	  uw.10m.up: Working.  32 spikes since yesterday afternoon. 
	 
	Rooftop logger: Next backup due Thurs/Fri. 
	 

morning status 
	 
	Weather: Clear.  Light (<1 m/s) winds from the E. 
	 
	Plant: Off now.  Scheduled to run 0800-1200 (EST) this morning. 
		Ran from 1030-1630 (EST) yesterday.  1030-1330 at 4 MW, 
		1330-1430 at 30 MW, and 1430-1630 at 62 MW. 
	 
	cav1/cav2:  Marigold died between 1040-1140 (GMT). 
	  t.4m.cav1: Working.  Cals installed in cal_files yesterday. 
	  t.10m.cav1: Working.  Cals installed in cal_files yesterday. 
	  psycs: Working. 
	  atik.4m.cav1:  Working.  ~5 spikes overnight. 
	  atik.10m.cav1: Working. 
	  NOx.ENSR: Working. 
	  props: Working. 
	  met.ENSR: Working. 
	 
	far:  
	  t.4m.far: Working.  Cals installed in cal_files yesterday. 
	  rain: Working. (no rain) 
	  radiometers:  Working. 
	  uw.4m.far: Working.  about 6 spikes overnight. 
	  prop: Working?  Light winds make it hard to tell. 
	 
	upwind:  
	  t.10.up: Working.  Cals installed in cal_files yesterday. 
	  h2o.10m.up: Working.  Replacement should be shipped today. 
	  psycs: Working. 
	  baro: Working.  Pressure is rising. 
	  props: Working. 
	  uw.10m.up: Working.  About 15 spikes overnight (some may be software 
		spikes - we rebooted last night to eliminate lots of them) 
	 
	Rooftop logger: Needs to be dumped today or tomorrow.  Hopefully, Steve 
		is bringing a ribbon cable to make it easier. 
	 
	 

morning status 
	 
	Weather: Clear.  Light (<1 m/s) winds from the E. 
	 
	Plant: Off now.  Scheduled to run 0800-1200 (EST) this morning. 
		Ran from 1030-1630 (EST) yesterday.  1030-1330 at 4 MW, 
		1330-1430 at 30 MW, and 1430-1630 at 62 MW. 
	 
	cav1/cav2:  Marigold died between 1040-1140 (GMT). 
	  t.4m.cav1: Working.  Cals installed in cal_files yesterday. 
	  t.10m.cav1: Working.  Cals installed in cal_files yesterday. 
	  psycs: Working. 
	  atik.4m.cav1:  Working.  ~5 spikes overnight. 
	  atik.10m.cav1: Working. 
	  NOx.ENSR: Working. 
	  props: Working. 
	  met.ENSR: Working. 
	 
	far:  
	  t.4m.far: Working.  Cals installed in cal_files yesterday. 
	  rain: Working. (no rain) 
	  radiometers:  Working.  Net and sumrad sometimes disagree due to shadowing  
		of individual instruments. 
	  uw.4m.far: Working.  about 6 spikes overnight. 
	  prop: Working?  Light winds make it hard to tell. 
	 
	upwind:  
	  t.10.up: Working.  Cals installed in cal_files yesterday. 
	  h2o.10m.up: Working.  Replacement should be shipped today. 
	  psycs: Working. 
	  baro: Working.  Pressure is rising. 
	  props: Working. 
	  uw.10m.up: Working.  About 15 spikes overnight (some may be software 
		spikes - we rebooted last night to eliminate lots of them) 
	 
	Rooftop logger: Needs to be dumped today or tomorrow.  Hopefully, Steve 
		is bringing a ribbon cable to make it easier. 
	 
	 

morning status 
	 
	Weather: Clear.  Light (<1 m/s) winds from the E. 
	 
	Plant: Off now.  Scheduled to run 0800-1200 (EST) this morning. 
		Ran from 1030-1630 (EST) yesterday.  1030-1330 at 4 MW, 
		1330-1430 at 30 MW, and 1430-1630 at 62 MW. 
	 
	cav1/cav2:  Marigold died between 1040-1140 (GMT). 
	  t.4m.cav1: Working.  Cals installed in cal_files yesterday. 
	  t.10m.cav1: Working.  Cals installed in cal_files yesterday. 
	  psycs: Working. 
	  atik.4m.cav1:  Working.  ~5 spikes overnight.  tc bias about -4C (why?). 
	  atik.10m.cav1: Working.  tc bias about -8C (why?). 
	  NOx.ENSR: Working. 
	  props: Working. 
	  met.ENSR: Working. 
	 
	far:  
	  t.4m.far: Working.  Cals installed in cal_files yesterday. 
	  rain: Working. (no rain) 
	  radiometers:  Working.  Net and sumrad sometimes disagree due to shadowing  
		of individual instruments. 
	  uw.4m.far: Working.  about 6 spikes overnight. 
	  prop: Working?  Light winds make it hard to tell. 
	 
	upwind:  
	  t.10.up: Working.  Cals installed in cal_files yesterday. 
	  h2o.10m.up: Working.  Replacement should be shipped today. 
	  psycs: Working. 
	  baro: Working.  Pressure is rising. 
	  props: Working. 
	  uw.10m.up: Working.  About 15 spikes overnight (some may be software 
		spikes - we rebooted last night to eliminate lots of them) 
	 
	Rooftop logger: Needs to be dumped today or tomorrow.  Hopefully, Steve 
		is bringing a ribbon cable to make it easier. 
	 
	 

DOWNWASH contacts: 
	 
	Rick Osa	414-785-5951		STMI, DOWNWASH program manager 
	Norm Bowne	203-657-8910		ENSR, field program manager 
	Lloyd Schulman	508-371-4269		Sigma, ASTER PI, modeler 
	Norm Nielsen	415-859-2841		SRI, LIDAR 
	Dave Ramsden	908-257-0133, ext 304	Sayreville plant engineer  
			257-9545 - fax 
			525-8290 (at other plant) 
	Nat Reese       908-932-8032            Rutgers prof/forecaster 
	 

backhoe and truck by garage 
	 
	The backhoe has been uncovering a tarp between cav2 and far.  I 
	don't see its emissions in the NOx sensors, and won't worry 
	about the turbulence since this is a plume rise experiment. 
	(Although they have created a pile of snow in front of far.) 
	 

morning status 
	 
	Weather: Clear, Winds light (<1 m/s) from SW.  Still snow on the ground, 
		but it is melting. 
	 
	Plant: Ran yesterday for plume rise, 1000-1400 EST. 
	 
	Other: Visitors yesterday:  1 prof and 3 students with Nat Reese - a Rutgers 
		professor;  4 reps. from NJ/DEP (EPA equiv);  Tom & Steve show up. 
	 
	cav1/cav2:  
	  t.4m.cav1: Working. 
	  t.10m.cav1: Working. 
	  psycs: Working. 
	  atik.4m.cav1:  Working.  3 spikes last night. 
	  atik.10m.cav1: Working.  No spikes. 
	  NOx.ENSR: Working. 
	  props: Working. 
	  met.ENSR: Working. 
	 
	far:  
	  t.4m.far: Working. 
	  rain: Working.  No precip. 
	  radiometers: Working. 
	  uw.4m.far: Working.  9 spikes overnight. 
	  prop: Working. 
	 
	upwind:  
	  t.10.up: Working. 
	  h2o.10m.up: Operating.  Replacement may show up today! 
	  psycs: Working. 
	  baro: Working.  Pressure is rising. 
	  props: Working.  Very light winds at the moment. 
	  uw.10m.up: Working.  16 spikes overnight. 
	 
	Rooftop logger: Needs to be dumped today. 
	 

morning status 
	 
	Weather: Clear, Winds light (<1 m/s) from SW.  Still snow on the ground, 
		but it is melting. 
	 
	Plant: Ran yesterday for plume rise, 1000-1400 EST. 
		Today plan another plume rise in stable conditions, 1600-2000 EST. 
	 
	Other: Visitors yesterday:  1 prof and 3 students with Nat Reese - a Rutgers 
		professor;  4 reps. from NJ/DEP (EPA equiv);  Tom & Steve show up. 
	 
	cav1/cav2:  
	  t.4m.cav1: Working. 
	  t.10m.cav1: Working. 
	  psycs: Working. 
	  atik.4m.cav1:  Working.  3 spikes last night. 
	  atik.10m.cav1: Working.  No spikes. 
	  NOx.ENSR: Working. 
	  props: Working. 
	  met.ENSR: Working. 
	 
	far:  
	  t.4m.far: Working. 
	  rain: Working.  No precip. 
	  radiometers: Working. 
	  uw.4m.far: Working.  9 spikes overnight. 
	  prop: Working. 
	 
	upwind:  
	  t.10.up: Working. 
	  h2o.10m.up: Operating.  Replacement may show up today! 
	  psycs: Working. 
	  baro: Working.  Pressure is rising. 
	  props: Working.  Very light winds at the moment. 
	  uw.10m.up: Working.  16 spikes overnight. 
	 
	Rooftop logger: Needs to be dumped today. 
	 

Survey done of near-CT towers 
	 
	Yesterday, I measured the alignment of the towers and the alignment of the 
	CT stack.  Today, I measured distances.  These are summarized in an idraw 
	figure, "survey": 
	 
	Tower angle:  337deg 46'30" 
	CT angle: 351deg 43'40" 
	 
	Distance along back of CT to reference point (black tape): 4.06m 
	ref to cav1: 8.00m 
	cav1 to cav2: 9.90m 
	cav2 to far: 20.95m 
	cav1 to ENSR: 6.37m 
	cav2 to ENSR: 8.90m 
	 

SODAR 
	 
	Operators from JCP&L: 
		Steve Lucadano 
		Joe Salander (Steve's boss):  525-8490 
	 
	Radian tech: 
		Wally Pratt 512 244-0100 
	 
	Current status, according to Rick Osa (S&TM): 
		Sodar has not been operating reliably - crashing. 
		Wally Pratt believes it may be a full hard disk, or 
		incorrect MSWindows config. 
	 
		Data has not been checked by a meteorologist. 
	 
	Dial-up Line: 525-8625 
		I could connect to that modem from ASTER, but was not 
		able to connect to the PC. 
		Wally Pratt plans to use that line for remote management. 
	 
	The project may contract directly with Radian for the sodar operations. 
		 
	 

uw boom angles 
	 
	The uw calibration routines use a coordinate system which has zero azimuth 
	as the angle between the two path "A" transducers.  Gordon (Wed.) and  
	I (Thur.) have reshot these sonics, aligning the faces of the "yellow" 
	and "blue" transducers vertically.  These angles are: 
	 
	uw.4m.far: 120deg 21'40" 
	uw.10m.up: 154deg 37'20" 
	 
	I've just entered these into sonic.config.S. 
	 
	We should remember to shoot path A in the future.  (Gordon thinks we 
	should align the sonics with the boom.  In fact, either would work 
	now that we "know" the difference between these angles.) 
	 

A plume rise run started at 20:00 gmt. 
	 

A plume rise run started at 21:00 gmt. 
	 
	 

Tower vibration 
	 
	I've noticed that the sonics "yaw" in high winds.  This probably is due 
	to having the psycs on the same tower, increasing the wind loading. 
	We should look at v-component spectra to look for this.  An easy way to 
	check for periods when this happens is to look at the variance of  
	alev and blev - I think blev especially - on the ATI's. 
	 
	Also note that the level signals on atik.10m.cav1 are not on scale.  They 
	indicate that the tower is not level, although we adjusted it with the 
	theodolite.  I don't think the tower has shifted, since I recall that these 
	signals have always been off since we got the tower up. 
	 

CT4 now running for plume rise 
	 
	This run is supposed to be 1600-2000 EST, for plume rise in stable 
	conditions. 
	 

CT4 now running for plume rise 
	 
	This run is supposed to be 1600-2000 EST, for plume rise in stable 
	conditions.  According to the upwind sonic, it became near-neutral  
	about 1500 EST. 
	 
	 

DOWNWASH contacts: 
	 
	Rick Osa	414-785-5951		STMI, DOWNWASH program manager 
	Norm Bowne	203-657-8910		ENSR, field program manager 
	Lloyd Schulman	508-371-4269		Sigma, ASTER PI, modeler 
	Norm Nielsen	415-859-2841		SRI, LIDAR 
	Dave Ramsden	908-257-0133, ext 304	Sayreville plant engineer  
			257-9545 - fax 
			525-8290 (at other plant) 
	Nat Reese       908-932-8032            Rutgers prof/forecaster 
	 
	If Dave Ramsden isn't available: 
	Rich Brevogel x203 
	Neil MacIntosh x205 
	Shift Foreman x280 (plant operations, gate security if closed) 
	 

PLUME RISE OPS STOPPED 
	 
	 Plume rise ops stopped at 01:00 GMT. 
	All systems on ASTER worked ok. There 
	was some spiking on the cav1 sonic at 
	m. Also a few spikes on the uw upwind 
	sonic. 
	 

DOWNWASH contacts: 
	 
	Rick Osa	414-785-5951		STMI, DOWNWASH program manager 
	Norm Bowne	203-657-8910		ENSR, field program manager 
	Lloyd Schulman	508-371-4269		Sigma, ASTER PI, modeler 
	Norm Nielsen	415-859-2841		SRI, LIDAR 
	Dave Ramsden	908-257-0133, ext 304	Sayreville plant engineer  
			257-9545 - fax 
			525-8290 (at other plant) 
	Nat Reese       908-932-8032            Rutgers prof/forecaster 
	 
	If Dave Ramsden isn't available: 
	Rich Brevogel x203 
	Neil MacIntosh x205 
	Shift Foreman x280 (plant operations, gate security if closed) 
	Another gate extension x299 
	 

PLUME RISE OPS STOPPED 
	 
	 Plume rise ops stopped at 01:17 GMT. 
	All systems on ASTER worked ok. There 
	was some spiking on the cav1 sonic at 
	m. Also a few spikes on the uw upwind 
	sonic. 
	 

morning status 
	 
	Weather: 
	 Sunny, light winds from the S, SW. 
	Highs today near 60. 
	 
	Plant: 
	 Plan for a plume rise from 10:00 to 14:00 
	local time. 
	 
	cav1/cav2: 
	  t.4m.cav1: working 
	  t.10m.cav1: working 
	  psycs: working 
	  atik.4m.cav1: working, about 40 to 50 spikes 
	  atik.10m.cav1: working, no spikes 
	  NOx.ENSR: working 
	  props: working 
	  met.ENSR: working 
	 
	far: 
	  t.4m.far: working 
	  rain: working, no rain 
	  radiometers: working 
	  uw.4m.far: working, 2 spikes 
	  prop: working 
	 
	upwind: 
	  t.10m.up: working 
	  h2o.10m.up: responding, still unknown 
	  psycs: working 
	  baro: working 
	  props: working 
	  uw.10m.up: working, alot of spikes 
	 
	Rooftop logger: working, data downloaded yesterday 
	 

cosmos rebooted: 
	 
	 Due to no response on the wind plots for 
	cosmos and the burst mode on cockpit cosmos 
	was rebooted via mxreset. 
	 

cosmos rebooted: 
	 
	 Due to no response on the wind plots for 
	cosmos and the burst mode on cockpit cosmos 
	was rebooted via mxreset. 
	 

morning status 
	 
	Weather: 
	 Sunny, light winds from the S, SW. 
	Highs today near 60. 
	 
	Plant: 
	 Plan for a plume rise from 10:00 to 14:00 
	local time. 
	 
	cav1/cav2: 
	  t.4m.cav1: working 
	  t.10m.cav1: working 
	  psycs: working 
	  atik.4m.cav1: working, about 40 to 50 spikes 
	  atik.10m.cav1: working, no spikes 
	  NOx.ENSR: working 
	  props: working 
	  met.ENSR: working 
	 
	far: 
	  t.4m.far: working 
	  rain: working, no rain 
	  radiometers: working 
	  uw.4m.far: working, 2 spikes 
	  prop: working 
	 
	upwind: 
	  t.10m.up: working 
	  h2o.10m.up: responding, still unknown 
	  psycs: working 
	  baro: working 
	  props: working 
	  uw.10m.up: working, alot of spikes. These 
	             spikes maybe due to a software glitch 
	             in cockpit, refer to next message 
	 
	Rooftop logger: working, data downloaded yesterday 
	 

cosmos rebooted: 
	 
	 Due to no response on the wind plots for 
	cosmos and the burst mode on cockpit cosmos 
	was rebooted via mxreset. 
	 Spikes from uw sonic could have been false 
	due to a software glitch in cockpit. 
	 

CT started at 9:20 local time 
	 

Survey done of near-CT towers 
	 
	Yesterday, I measured the alignment of the towers and the alignment of the 
	CT stack.  Today, I measured distances.  These are summarized in an idraw 
	figure, "survey": 
	 
	Tower angle:  337deg 46'30" 
	CT angle: 351deg 43'40" 
	 
	Distance along back of CT to reference point (black tape): 4.06m 
	ref to cav1: 8.00m 
	cav1 to cav2: 9.90m 
	cav2 to far: 20.95m 
	cav1 to ENSR: 6.37m 
	cav2 to ENSR: 8.90m 
	 
	Feb. 19: 
	 
	SRS and TWH surveyed the bases of the nearby towers relative to the base  
	of the CT stack.  We used the theodolite to measure the relative heights  
	of a constant elevation `surface' above the CT and ASTER tower bases: 
	 
				measurement	calculated relative heights 
	CT stack concrete pad: 	0.75 m		0.00 m 
	CAV1 base:		0.94 m  	0.19 m  lower than CT base 
	CAV2 base:		1.60 m		0.85 m  lower than CT base 
	FAR  base:		2.13 m		1.38 m  lower than CT base 
	 
	 

morning status 
	 
	Weather: Foggy, no winds, possible rain 
	later today. 
	 
	Plant: Down day due to moisture 
	 
	cav1/cav2:   
	  t.4m.cav1: working 
	  t.10m.cav1: working 
	  psycs: working 
	  atik.4m.cav1: working  
	  atik.10m.cav1: working 
	  NOx.ENSR: working 
	  props: working 
	  met.ENSR: working 
	 
	far:  
	  t.4m.far: working 
	  rain: working, no rain 
	  radiometers:  working 
	  uw.4m.far: working 
	  prop: working 
	 
	upwind:  
	  t.10.up: working 
	  h2o.10m.up: still unknown 
	  psycs: working 
	  baro: working 
	  props: working 
	  uw.10m.up: working, about 30 spikes 
		     over the last 2 days 
	 
	Rooftop logger: to be downloaded today 
	 
	 

Tethersonde data saved 
	 
	 Tethersonde data has been downloaded 
	to ASTER. Directory is /data/DOWNWASH94/raw_data/tsonde. 
	We may try to modem this data to Norm. 
	 

prop.2m.up has suspicious wind direction; 
	it is about 10 deg higher than that of 
	prop.6m.up.  We will keep an eye on it. 
	 
	 

The rain has set in. 
	 
	 It started to rain around noon today. 
	Very light conditions. The uw sonic at 
	far has been spiking since the rain started. 
	everybody else is looking good. 
	 

UW sonic at far spiking 
	 
	 The uw sonic at far has been spiking. 
	It appears to be due to the rain. 
	This started at about 12:00 local time. 
	 

UW sonic at far spiking 
	 
	 The uw sonic at far has been spiking. 
	It appears to be due to the rain. 
	This started at about 12:00 local time. 
	The v axis looks good while u, w, and tc 
	are bad. This may mean the set of transducers 
	along the boom direction are questionable. 
	 

The 10m cav1 is now spiking! 
	 I assume it is due to the rain. 
	 

The 10m cav1 is now sending -9999's 
	 

The rain has stopped 
	 
	 The rain has stopped and the sonics 
	have come back to life. 
	 

morning status 
	 
	Weather: Sunny, cooler temperatures with 
	         winds out of the N,NW. Good day 
	         for downwash. 
	 
	Plant: Plan calls for a downwash day. Possible 
	       smoke bomb tests. 
	 
	cav1/cav2: 
	  t.4m.cav1: working 
	  t.10m.cav1: working 
	  psycs: working, 6m rh looks high 
	  atik.4m.cav1: working 
	  atik.10m.cav1: spiking at night, 
			 looks good now 
	  NOx.ENSR: working 
	  props: working 
	  met.ENSR: working 
	 
	far: 
	  t.4m.far: working 
	  rain: working, rain yesterday 
	  radiometers: working 
	  uw.4m.far: working 
	  prop: no wind speed info 
	 
	upwind: 
	  t.10.up: working 
	  h2o.10m.up: still unknown 
	  psycs: working, 2m rh questionable at night 
	  baro: working 
	  props: 6m speed very low 
	  uw.10m.up: working with a few spikes 
	 
	Rooftop: Data downloaded yesterday 
	 
	 

Props out: 
	 
	 The 6m prop is reading low speed. Assume 
	this is due to low temperatures and high 
	humidity. The 10m far prop gives zero 
	speed. 
	 

`Fixed' props 
	 
	Around 8am est, SRS climbed far tower and applied  
	heat gun to first the electronics and then the  
	optical chopper of the 10m prop.  It began outputting  
	a believable wind speed only after he heated the  
	optical chopper.  Then he climbed the upwind tower 
	and heated the optical chopper of the 6m prop.  This  
	also fixed it.  By that time, the 10m.far prop was not 
	functioning again, so Steve heated it again, bringing 
	it back on line about 10 am est.  We'll see how long  
	they last. 
	 
	 

CT started then turned off 
	 
	 The CT was started at about 8:45 local. 
	System was running on gas due to clog in 
	oil system. Tryed to switch to oil but system 
	did not work. CT was shut down at 10:45 am local. 
	 

Modem configuration file 
	 
	is /usr/local/etc/dp/log/+aster: 
	 
	AT 
	 
	 
	OK 
	 
	 
	ATDT9,13034499513 
	 
	 
	CONNECT 9600/ARQ/V32/LAPM 
	 
	\016c\016b\036b\016c\016cNb 
	 
	 

morning status 
	 
	Weather: Snow with strong winds from the 
	         east. Snow expected most of the 
		 day turning to freezing rain. 
	 
	Plant: No ops today. Next planned op is for 
	       Friday. 
	 
	cav1/cav2: 
	  t.4m.cav1: still good 
	  t.10m.cav1: down 
	  psycs: working 
	  atik.4m.cav1: spikes during the night. 
		        presently down. 
	  atik.10m.cav1: working with spikes 
	  NOx.ENSR: working 
	  props: working 
	  met.ENSR: working 
	 
	far: 
	  t.4m.far: down 
	  rain: snow detected 
	  radiometers: working 
	  uw.4m.far: responding but spiking all the time 
	  prop: working 
	 
	upwind: 
	  t.10.up: down 
	  h2o.10m.up: responding 
	  psycs: working 
	  baro: working 
	  props: working 
	  uw.10m.up: working, spikes during the night 
	 
	Rooftop: Will download data tomorrow 
	 
	 

Weather Conditions at 9 AM EST on 23 FEB 94 for Newark, NJ. 
	Temp(F)    Humidity(%)    Wind(mph)    Pressure(in)    Weather 
	======================================================================== 
	   28          96%           NE at 14       30.41      moderate snow 
	 
	 
	 
	 
	 ..WINTER STORM WARNING TODAY AND EARLY TONIGHT... 
	 ..FLOOD WATCH LATE TONIGHT AND EARLY THURSDAY FOR POOR DRAINAGE AND 
	URBAN FLOODING... 
	 
	 TODAY...SNOW...MIXING WITH SLEET AND FREEZING RAIN LATE IN THE DAY. 
	ACCUMULATIONS OF 4 TO 6 INCHES. HIGH IN THE LOWER TO MID 30S. WIND 
	NORTHEAST INCREASING TO 15 TO 25 MPH. CHANCE OF PRECIPITATION NEAR 
	 PERCENT. 
	 
	 TONIGHT...SLEET AND FREEZING RAIN CHANGING TO ALL RAIN DURING THE 
	EVENING. RAIN BECOMING HEAVY AT TIMES. CHANCE OF A THUNDERSTORM. 
	TEMPERATURES RISING TO AROUND 40. NORTHEAST WIND 20 TO 30 MPH 
	AND GUSTY. CHANCE OF PRECIPITATION NEAR 100 PERCENT. 
	 
	 THURSDAY...MILDER WITH RAIN ENDING IN THE MORNING...BECOMING 
	PARTLY CLOUDY BY AFTERNOON. HIGH AROUND 50. CHANCE OF RAIN 70 
	PERCENT. 
	 
	 EXTENDED FORECAST... 
	 FRIDAY...VARIABLE CLOUDINESS WITH A CHANCE OF LIGHT SNOW AT NIGHT. 
	LOWS IN THE 20S COAST AND TEENS INLAND. HIGHS IN THE UPPER 20S TO LOW 
	S. 
	 SATURDAY...BECOMING PARTLY CLOUDY AND COLD. LOWS IN THE TEENS COAST 
	AND SINGLE NUMBERS INLAND. HIGHS IN THE 20S. 
	 SUNDAY...SUNNY BUT CONTINUED QUITE COLD. LOWS IN THE TEENS COAST AND 
	SINGLE NUMBERS INLAND. HIGHS IN THE 20S. 
	 
	 

4m fast T on cav1 is dying! 
	 

10m far wind speed starting to die! 
	 

The 6m upwind prop is going bad! 
	 
	  Wind speeds are dying at prop.6m.up. 
	 

ENSR met tower blown over! 
	 
	 The ENSR tower was blown over. 
	We will set it back up and see if 
	it is still working. Based on Splus 
	plot this event occurred just before 
	:00 gmt. Data does not seem to be 
	coming in. 
	 

ENSR met running again! 
	 
	 Tom and Steve seet the ENSR met tower 
	back up. The wind direction vane was bent so 
	we tryed to fix it. The alignment for direction 
	is probable bad since the orientation of the 
	tower has changed. The logger is responding. 
	 

4m ati on cav1 backup! 
	 

Late afternoon status: 
	 
	 Since the snow/rain has stopped, the sonics 
	have come back to life. There is still a lot 
	of spiking going on. 
	 All fast T's are dead. 
	 The 10m.prop.far speed is still bad. 
	 The 6m.prop.upwind speed is bad. 
	 

morning status 
	 
	Weather: The weather outside is frightful! 
		 Freezing rain/rain, overcast with 
		 the feeling of doom in the air. 
		 Possible flooding later today at the 
		 far tower. 
	 
	Plant: Down day 
	 
	cav1/cav2:  
	  t.4m.cav1: down 
	  t.10m.cav1: down 
	  psycs: working 
	  atik.4m.cav1: responding but bad data 
	  atik.10m.cav1: responding, bad data 
	  NOx.ENSR: working 
	  props: working, ice on props 
	  met.ENSR: still standing 
	 
	far: 
	  t.4m.far: down 
	  rain: its raining 
	  radiometers: working, assume ice on domes 
	  uw.4m.far: responding, bad data 
	  prop: speed bad 
	 
	upwind: 
	  t.10.up: down 
	  h2o.10m.up: responding 
	  psycs: working 
	  baro: working 
	  props: 6m prop speed bad 
	  uw.10m.up: responding, bad data 
	 
	Rooftop: will download data today 
	 
	 

Weather forecast: 
	 
	NEWARK AND VICINITY FORECAST                         
	NATIONAL WEATHER SERVICE NEWARK NJ  
	 AM EST THU FEB 24 1994 
	 
	 ..FREEZING RAIN ADVISORY THROUGH MID MORNING... 
	 
	 THIS MORNING...FREEZING RAIN...CHANGING TO RAIN BY MID TO LATE 
	MORNING. RAIN MAY BE HEAVY AT TIMES WITH A CHANCE OF A THUNDERSTORM. 
	TEMPERATURES RISING THROUGH THE 30S. WIND EAST 15 TO 25 MPH. 
	 
	 THIS AFTERNOON...RAIN ENDING WITH SKIES BECOMING PARTLY SUNNY. HIGH 
	 TO 45 BEFORE TEMPERATURES DROP BY MID AFTERNOON. WINDY. WIND WEST 
	 TO 30 MPH. CHANCE OF PRECIPITATION NEAR 100 PERCENT. 
	 
	 TONIGHT...PARTLY CLOUDY. LOW IN THE MID 20S. WIND WEST 15 TO 20 MPH. 
	 
	 FRIDAY...BECOMING CLOUDY WITH A CHANCE OF LIGHT SNOW BY LATE 
	AFTERNOON. HIGH IN THE MID 30S. CHANCE OF SNOW 30 PERCENT. 
	 
	 
	AM 
	 
	 
	 
	 EXTENDED FORECAST... 
	 FRIDAY NIGHT...CLOUDY WITH A CHANCE OF SNOW. LOWS FROM THE 
	TEENS INLAND TO LOWER 20S ALONG THE COAST. 
	 SATURDAY...BECOMING PARTLY CLOUDY AND COLD. HIGHS IN THE 20S. 
	 SUNDAY...PARTLY CLOUDY AND COLD. LOWS IN THE TEENS ALONG THE COAST 
	AND SINGLE NUMBERS INLAND. HIGHS IN THE LOWER TO MID 20S. 
	 MONDAY...FAIR AND COLD. LOWS IN THE TEENS ALONG THE COAST AND SINGLE 
	NUMBERS INLAND. HIGHS IN THE 20S. 
	 
	 

Weather Forecast at 9 AM EST on 23 FEB 94 for Newark, NJ. 
	Temp(F)    Humidity(%)    Wind(mph)    Pressure(in)    Weather 
	======================================================================== 
	   28          96%           NE at 14       30.41      moderate snow 
	 
	 
	 
	 
	 ..WINTER STORM WARNING TODAY AND EARLY TONIGHT... 
	 ..FLOOD WATCH LATE TONIGHT AND EARLY THURSDAY FOR POOR DRAINAGE AND 
	URBAN FLOODING... 
	 
	 TODAY...SNOW...MIXING WITH SLEET AND FREEZING RAIN LATE IN THE DAY. 
	ACCUMULATIONS OF 4 TO 6 INCHES. HIGH IN THE LOWER TO MID 30S. WIND 
	NORTHEAST INCREASING TO 15 TO 25 MPH. CHANCE OF PRECIPITATION NEAR 
	 PERCENT. 
	 
	 TONIGHT...SLEET AND FREEZING RAIN CHANGING TO ALL RAIN DURING THE 
	EVENING. RAIN BECOMING HEAVY AT TIMES. CHANCE OF A THUNDERSTORM. 
	TEMPERATURES RISING TO AROUND 40. NORTHEAST WIND 20 TO 30 MPH 
	AND GUSTY. CHANCE OF PRECIPITATION NEAR 100 PERCENT. 
	 
	 THURSDAY...MILDER WITH RAIN ENDING IN THE MORNING...BECOMING 
	PARTLY CLOUDY BY AFTERNOON. HIGH AROUND 50. CHANCE OF RAIN 70 
	PERCENT. 
	 
	 EXTENDED FORECAST... 
	 FRIDAY...VARIABLE CLOUDINESS WITH A CHANCE OF LIGHT SNOW AT NIGHT. 
	LOWS IN THE 20S COAST AND TEENS INLAND. HIGHS IN THE UPPER 20S TO LOW 
	S. 
	 SATURDAY...BECOMING PARTLY CLOUDY AND COLD. LOWS IN THE TEENS COAST 
	AND SINGLE NUMBERS INLAND. HIGHS IN THE 20S. 
	 SUNDAY...SUNNY BUT CONTINUED QUITE COLD. LOWS IN THE TEENS COAST AND 
	SINGLE NUMBERS INLAND. HIGHS IN THE 20S. 
	 
	 

afternoon status: 
	 
	 The weather has improved. The sun is out 
	and the snow is melting. The 6m upwind prop 
	and the 10m ar prop are still not reading 
	wind speed correctly. We hope to fix the 
	fast T's this afternoon. All sonics are working 
	and the new Krypton has arrived. 
	 

morning status 
	 
	Weather: Light snow falling with sunshine. 
	 
	Plant: Plan for a downwash day today starting 
	       at 13:00 local time. 
	 
	cav1/cav2: 
	  t.4m.cav1: down 
	  t.10m.cav1: down 
	  psycs: working 
	  atik.4m.cav1: working 
	  atik.10m.cav1: working 
	  NOx.ENSR: working 
	  props: working 
	  met.ENSR: working, direction in question 
		    because tower fell down the other day. 
		    need to shoot a new angle. 
	far: 
	  t.4m.far: down 
	  rain: working 
	  radiometers: working 
	  uw.4m.far: working 
	  prop: working, 10m looks good 
	 
	upwind: 
	  t.10.up: down 
	  h2o.10m.up: running 
	  psycs: working 
	  baro: working 
	  props: working, 6m looking good 
	  uw.10m.up: working, some spikes from yesterday 
	 
	Rooftop: will download data tomorrow 
	 
	 

Weather Forecast: 
	 
	 
	Weather Conditions at 7 AM EST on 26 FEB 94 for Newark, NJ. 
	Temp(F)    Humidity(%)    Wind(mph)    Pressure(in)    Weather 
	======================================================================== 
	   26          84%        NORTH at 14       29.72      light snow 
	 
	 
	 
	NEWARK AND VICINITY FORECAST 
	NATIONAL WEATHER SERVICE NEWARK NJ 
	 AM EST SAT FEB 26 1994 
	 
	 ..SNOW ADVISORY FOR THIS MORNING...                                 
	 
	 TODAY...SNOW ENDING BEFORE NOON WITH ACCUMULATIONS OF A COUPLE OF 
	INCHES...THEN PARTLY SUNNY...WINDY AND COLD. HIGH IN THE MID 30S. 
	WIND BECOMING NORTHWEST 20 TO 25 MPH AND GUSTY.                  
	 
	 TONIGHT...CLEAR. WINDY AND COLD. LOW 15 TO 20.  WIND NORTHWEST   
	 TO 20 MPH AND GUSTY. 
	 
	 SUNDAY...SUNNY...WINDY AND COLD. HIGH AROUND 30. 
	 
	 EXTENDED FORECAST... 
	 
	 MONDAY...FAIR SKIES BUT CONTINUED COLD. LOWS IN THE TEENS COAST AND 
	SINGLE NUMBERS INLAND. HIGHS IN THE 20S COAST AND TEENS INLAND. 
	 TUESDAY...CLOUDING UP WITH A CHANCE OF SNOW LATE IN THE DAY. LOWS IN 
	THE TEENS COAST AND SINGLE NUMBERS INLAND. HIGHS IN THE 20S COAST AND 
	TEENS INLAND. 
	 WEDNESDAY...A CHANCE OF SNOW. STILL COLD WITH THE LOWS IN THE TEENS 
	AND THE HIGHS IN THE 20S. 
	 
	~ 
	 

fast T at cav1 4m replaced 
	 
	 Fast T at 4m was replaced and calibrated. 
	Gain factor = 0.001515009 
	This was done at 14:30 to 14:40 gmt 
	 

marigold went down! 
	 
	 This occurred about 1/2 hour ago. 
	 

CT started at 13:00 gmt for downwash 
	 

marigold went down! 
	 
	 This occurred sortly after 15:00 gmt. 
	The station was backup at 16:00. Tryed 
	a "mxreset" but it did not work. At this 
	time no obvious reason. 
	 
	 

marigold down again! 
	 
	 Marigold crashed again at 19:15 gmt. 
	It was back up at 19:25 gmt. A hardware 
	reset was required. 
	 

ENSR_met wind direction: 
	 
	 Tony and Barry provided an update to 
	the ENSR_met wind direction angle. The 
	calibration function has been changed and 
	with the latest crash of marigold the covar 
	files should have the new angle. 
	 

marigold down again! 
	 
	 Marigold crashed again at 19:15 gmt. 
	It was back up at 19:25 gmt. A hardware 
	reset was required. 
	 
	 The syslog file does not give much of a  
	clue as to why marigold went down. Response 
	was "marigold No activity, INGEST stopped". 
	 

Corrupt ENSR.NOx.covar file 
	 
	 This file got corrupted when marigold 
	crashed. This resulted in the net.cdf file 
	not being created for the ENSR data. Modified 
	the covar file to correct problem. This required 
	the removal of one 5 minute block of data. 
	 

CT ops status 
	 
	  ASTER has been working good since the last 
	marigold crash. The sonics and fast T at cav1 
	are responding to the CT. 
	 

Weather forecast: 
	 
	Weather Conditions at 7 AM EST on 27 FEB 94 for Newark, NJ. 
	Temp(F)    Humidity(%)    Wind(mph)    Pressure(in)    Weather 
	======================================================================== 
	   12          51%          WNW at 17       30.21      Clear 
	 
	 
	 
	NEWARK AND VICINITY FORECAST...CORRECTED 
	NATIONAL WEATHER SERVICE NEWARK NJ 
	 AM EST SUN FEB 27 1994 
	 
	 TODAY...SUNNY.  WINDY AND COLD.  HIGH 25 TO 30.  WIND NORTHWEST 20 
	TO 25 MPH AND GUSTY. 
	 
	 TONIGHT...CLEAR AND COLD WITH DIMINISHING WIND.  LOW 10 TO 15. WIND 
	NORTHWEST DECREASING TO AROUND 15 MPH. 
	 
	 MONDAY...SUNNY EARLY WITH INCREASING CLOUDS LATE IN THE DAY.  HIGH 
	 TO 35. 
	 
	 EXTENDED FORECAST... 
	 
	 TUESDAY...MOSTLY CLOUDY WITH A CHANCE OF FLURRIES. LOWS IN THE TEENS. 
	HIGHS IN THE 20S. 
	 WEDNESDAY...CHANCE OF SNOW. LOWS IN THE TEENS. HIGHS IN THE 20S. 
	 THURSDAY...CHANCE OF SNOW. LOWS IN THE 20S COAST AND TEENS INLAND. 
	HIGHS NEAR 30. 
	 
	 

morning status 
	 
	Weather: Sunny, windy, and cold! 
	 
	Plant: Planned ops at 9:00 am local 
	 
	cav1/cav2: 
	  t.4m.cav1: working 
	  t.10m.cav1: down 
	  psycs: working 
	  atik.4m.cav1: working, spikes during the night 
	  atik.10m.cav1: working, some spikes 
	  NOx.ENSR: working, having problems with covar 
	  props: working 
	  met.ENSR: working, problem with covar refer to 
		    logbook entry 
	 
	far: 
	  t.4m.far: down 
	  rain: working 
	  radiometers: working 
	  uw.4m.far: working 
	  prop: working 
	 
	upwind: 
	  t.10.up: down 
	  h2o.10m.up: running, still unknown 
	  psycs: working 
	  baro: working 
	  props: working 
	  uw.10m.up: working 
	 
	Rooftop: will download data today 
	 
	 

CT started at 9:00 am local time 
	 

Problems with ENSR covar/netcdf 
	 
	 The covar file for the ENSR data looks 
	funny. This occurred a little after 23:00 gmt. 
	 

Problems with ENSR covar/netcdf 
	 
	 The covar file for the ENSR data looks 
	funny. This occurred a little after 23:00 gmt. 
	 
	 The wind direction changed about 250 degrees. 
	Looking at rserial, the input data shows a similar 
	change. The wind vane may have loosen after the 
	fall. This needs to be looked at. 
	 

Problems with ENSR covar/netcdf 
	 
	 The covar file for the ENSR data looks 
	funny. This occurred a little after 23:00 gmt. 
	We did not get the remaining 1.5 hours of ENSR 
	data from the daily plots. After playing around for 
	awhile discovered the reason why was the covar was 
	writing to the wrong file. This was due to an 
	edit done on the covar file. Covar was writing to 
	ENSR_NOx.covar~. 
	  All has been corrected (we hope!) 
	 
	 
	 
	  
	 

ENSR wind direction bad! 
	 
	 The data coming from the ENSR met 
	wind direction looks bad. It is off 
	by 260 degrees. The last fall may have 
	loosen the vane head from the shaft. 
	This will be looked at when conditions 
	are favorable. 
	 

ENSR wind direction bad! 
	 
	 The data coming from the ENSR met 
	wind direction looks bad. It is off 
	by 260 degrees. The last fall may have 
	loosen the vane head from the shaft. 
	This will be looked at when conditions 
	are favorable. 
	 
	 It was also noted that the lastest update 
	in the calibration routine for ENSR_met is 
	not being used. This update was a correction 
	in the orientation of the boom. After the 
	tower was setup Barry took a new reading. 
	The calibration routine was "made" along with 
	"preprocess". "preprocess" was installed. 
	 

ENSR wind direction bad! 
	 
	 The data coming from the ENSR met 
	wind direction looks bad. It is off 
	by 260 degrees. The last fall may have 
	loosen the vane head from the shaft. 
	This will be looked at when conditions 
	are favorable. 
	 
	 It was also noted that the lastest update 
	in the calibration routine for ENSR_met is 
	not being used. This update was a correction 
	in the orientation of the boom. After the 
	tower was setup Barry took a new reading. 
	The calibration routine was "made" along with 
	"preprocess" and "prep". "preprocess" and 
	"prep" were installed. 
	 

ENSR tower down for a short time 
	 
	 Tony and Steve lowered the ENSR tower to 
	look at the wind direction sensor. There was 
	no obvious damage relating to the direction error. 
	There is damage to the sensor's shaft. 
	This was done at 18:15-18:20 gmt. 
	 

CT shut down at 21:00 gmt. 
	 

Sonic despiking may be difficult 
	for the cavity sonics, particularly 
	during periods in which the combustion 
	turbine was running, because of the 
	highly intermittent nature of the 
	turbulent flow.  I have looked at several 
	periods with high winds, using fun.plot.prep, 
	and the full time series sonic data look good.  
	 
	 

morning status 
	 
	Weather: clear and cold. Light winds 
		 from the NNW. 
	 
	Plant: CT running at 6:00 am local time 
	       for a plume rise study. 
	 
	cav1/cav2: 
	  t.4m.cav1: working 
	  t.10m.cav1: down 
	  psycs: working 
	  atik.4m.cav1: working 
	  atik.10m.cav1: working 
	  NOx.ENSR: working 
	  props: working 
	  met.ENSR: working, direction questionable 
	 
	far: 
	  t.4m.far: down 
	  rain: working, no rain 
	  radiometers: working 
	  uw.4m.far: working 
	  prop: working 
	 
	upwind: 
	  t.10.up: down 
	  h2o.10m.up: running, questionable 
	  psycs: working 
	  baro: working 
	  props: working 
	  uw.10m.up: working, spikes during the night 
	 
	Rooftop: data downloaded yesterday 
	 
	 

CT4 has gone done. At 
	this time the reason is unknown. 
	Time is 14:15 gmt. 
	 

fast T at 4m far replaced. 
	 
	 The fast T at 4m.far was replaced at 18:45 gmt. 
	The new calibration gain is 0.0015315. 
	This has been entered in the cal_files. 
	 

fast T at 4m far replaced. 
	 
	 The fast T at 4m.far was replaced at 18:45 gmt. 
	The new calibration gain is 0.00153135. 
	This has been entered in the cal_files. 
	 

10m fast T on cav1 still down 
	 
	 An attempt to fix the 10m fast T on 
	cav1 failed due to cold temperatures! 
	 

morning status 
	 
	Weather: Sunny, light winds, cold. 
	 
	Plant: Down day 
	 
	cav1/cav2:  
	  t.4m.cav1: working 
	  t.10m.cav1: down 
	  psycs: working 
	  atik.4m.cav1: working 
	  atik.10m.cav1: working 
	  NOx.ENSR: working 
	  props: working 
	  met.ENSR: working, wind direction questionable 
	 
	far: 
	  t.4m.far: working 
	  rain: working, no rain 
	  radiometers: working 
	  uw.4m.far: working 
	  prop: working 
	 
	upwind: 
	  t.10.up: down 
	  h2o.10m.up: running, data questionable 
	  psycs: working 
	  baro: working 
	  props: working 
	  uw.10m.up: working, some spikes during the night 
	 
	Rooftop: download data tomorrow 
	 
	 

CT4 has gone down. 
	 At this time the reason is unknown. 
	Time is 14:15 gmt. The reason they 
	shutdown was because they wanted to! 
	 
	 During this ops they had to turn on 
	 of the CTs for power requirements. 
	 

morning status - CT running at 6:00 am 
	 
	Weather: clear and cold. Light winds 
		 from the NNW. 
	 
	Plant: CT running at 6:00 am local time 
	       for a plume rise study. 
	 
	cav1/cav2: 
	  t.4m.cav1: working 
	  t.10m.cav1: down 
	  psycs: working 
	  atik.4m.cav1: working 
	  atik.10m.cav1: working 
	  NOx.ENSR: working 
	  props: working 
	  met.ENSR: working, direction questionable 
	 
	far: 
	  t.4m.far: down 
	  rain: working, no rain 
	  radiometers: working 
	  uw.4m.far: working 
	  prop: working 
	 
	upwind: 
	  t.10.up: down 
	  h2o.10m.up: running, questionable 
	  psycs: working 
	  baro: working 
	  props: working 
	  uw.10m.up: working, spikes during the night 
	 
	Rooftop: data downloaded yesterday 
	 
	 

CT4 shutdown yesterday because of problem! 
	 
	 CT4 was shutdown because of leak in the 
	transfer case. They should finish repairs today. 
	 

ENSR met tower down 
	 
	 Barry is working on the ENSR met sensors. 
	 

CT4 shutdown yesterday because of problem! 
	 
	 CT4 was shutdown because of leak in the 
	transfer case. They should finish repairs today. 
	 

ENSR tower backuo 
	 
	 Barry and Tony setup the tower. 
	The wind direction looks better. They 
	will shoot the direction later. 
	 

ENSR tower backup 
	 
	 Barry and Tony setup the tower. 
	The wind direction looks better. They 
	will shoot the direction later. 
	 

Fast T installed at 10m cav1 
	 
	 The fast T.10m.cav1 was installed 
	around 16:45 gmt. Calibration factor 
	was entered in cal_files. 
	 

Processing fast T cals 
	 
	Here are the results of my new fastT calibration routine. 
	The resulting coefficients are to be entered into a cal_file 
	(and prep.config changed to use td_linear), which I'll do after  
	exiting logbook. 
	 
	[Sorry for all the arguments in this fun.fastT.cal.get function -  
	Gordon may make a routine to lookup adam, channel, and archive file root 
	from the did.name sometime in the future to eliminate some of them. 
	Note some manual work interpreting the output - but here are some examples.] 
	 
	t.4m.cav1: 
	 
	fun.fastT.cal.get("t.4m.cav1","marigold",100,35,16,02,"cav/fast035160000", 
		nummin=2) 
	gain = 0.001508249 
	 
	t.10m.cav1: 
	 
	Need to run this twice since cal split between archive files; 
	 
	dT1 <- fun.fastT.cal.get("t.10m.cav1","marigold",101,35,15,59, 
		"cav/fast035153540",nummin=1) 
	dT2 <- fun.fastT.cal.get("t.10m.cav1","marigold",101,35,16,00, 
		"cav/fast035160000",nummin=1) 
	gain <- (50/32768)*(5/mean(abs(c(dT1[5:10],dT2[1:4])))) 
	gain = 0.001505667 
	 
	t.4m.far: 
	 
	dT <- fun.fastT.cal.get("t.4m.far","ragwort",100,35,15,41, 
		"far/fast035153519",nummin=2) 
	gain <- (50/32768)*(5/mean(abs(dT[4:13]))) 
	gain = 0.001496293 
	 
	t.10m.up: 
	 
	dT <- fun.fastT.cal.get("t.10m.up","cosmos",100,35,16,26, 
		"upwind/fast035160000",nummin=2) 
	gain <- (50/32768)*(5/mean(abs(dT[5:13]))) 
	gain = 0.001528624 
	 

PROCEDURE for FAST T cals: 
	 
	 These are notes on fast T cal procedures. 
	 
	Tower work: 
	 
		tools:	2 DVOMs 
			1 small screwdriver 
			1 thermocouple cover with meter unit 
			1 new fast T probe if needed 
			1 long cable to interface to splitter 
			1 splitter box for getting fast T signal 
	 
	 The splitter box allows you to monitor the signal from the 
	fast T while the signal is still going to the ADAM. The 9 
	pin cable going to the fast T along with the long meter 
	cable attach to the splitter. The other end of the splitter 
	goes to the breakout box (attached to the channel for the 
	fast T). 
	 Attach the other end of the meter cable to one of the 
	DVOMs. Set it to dc volts. If the fast T probe is broken 
	the meter will read greater than 5 volts. 
	 Attach the other meter to the thermocouple unit. Set the 
	meter to dc 300 mvolts. Also set the thermocouple unit 
	to degrees C. It will read temperature in degrees C 
	( 12.3 mvolts = 12.3 C). 
	 You want to place these meters such that you can read 
	both of them at the same time when adjusting the bridge. 
	 Replace the fast T probe if required and place the 
	thermocouple unit over the probe. Allow the temperature 
	to stabilize. 
	 
	Adjustment procedure: 
	 
	 While monitoring both meters adjust the offset pot so 
	that the absolute value of the fast T agrees with the 
	thermocouple (remember the output for the fast T should 
	be multiplied by 10). The toggle switch should be in the 
	operate position. Now move the toggle to "cal". There 
	should be a gain of 5 degrees in the fast T output. 
	If not, adjust the gain pot. This may take a few 
	iterations of switching the toggle back and forth. 
	Once this is done you should check the absolute value 
	again. 
	 
	Collection of data set: 
	 
	 In order to determine the true gain you need a data set 
	to look at. Set the toggle switch to zero and leave for 
	 seconds. Now switch the toggle to operate for 5 seconds 
	then to cal for 5 seconds. Repeat this step for at least 
	 times. Set the switch to zzero one more time, 
	 seconds, then back to operate. Remove the thermocouple 
	unit. 
	 
	 
	  
	 

PROCEDURE for FAST T cals: 
	 
	 These are notes on fast T cal procedures. 
	 
	Tower work: 
	 
		tools:	2 DVOMs 
			1 small screwdriver 
			1 thermocouple cover with meter unit 
			1 new fast T probe if needed 
			1 long cable to interface to splitter 
			1 splitter box for getting fast T signal 
	 
	 The splitter box allows you to monitor the signal from the 
	fast T while the signal is still going to the ADAM. The 9 
	pin cable going to the fast T along with the long meter 
	cable attach to the splitter. The other end of the splitter 
	goes to the breakout box (attached to the channel for the 
	fast T). 
	 Attach the other end of the meter cable to one of the 
	DVOMs. Set it to dc volts. If the fast T probe is broken 
	the meter will read greater than 5 volts. 
	 Attach the other meter to the thermocouple unit. Set the 
	meter to dc 300 mvolts. Also set the thermocouple unit 
	to degrees C. It will read temperature in degrees C 
	( 12.3 mvolts = 12.3 C). 
	 You want to place these meters such that you can read 
	both of them at the same time when adjusting the bridge. 
	 Replace the fast T probe if required and place the 
	thermocouple unit over the probe. Allow the temperature 
	to stabilize. 
	 
	Adjustment procedure: 
	 
	 While monitoring both meters adjust the offset pot so 
	that the absolute value of the fast T agrees with the 
	thermocouple (remember the output for the fast T should 
	be multiplied by 10). The toggle switch should be in the 
	operate position. Now move the toggle to "cal". There 
	should be a gain of 5 degrees in the fast T output. 
	If not, adjust the gain pot. This may take a few 
	iterations of switching the toggle back and forth. 
	Once this is done you should check the absolute value 
	again. 
	 
	Collection of data set: 
	 
	 In order to determine the true gain you need a data set 
	to look at. Set the toggle switch to zero and leave for 
	 seconds. Now switch the toggle to operate for 5 seconds 
	then to cal for 5 seconds. Repeat this step for at least 
	 times. Set the switch to zero one more time, 
	 seconds, then back to operate. Remove the thermocouple 
	unit. 
	 
	Data Processing: 
	 
	 To compute a gain factor, use Splus to find the 
	proper time period when you were switching the 
	toggle back and forth between operate and cal. 
	This can be done using a fun routine. After 
	getting into Splus open a display window, X11(). 
	Use the following command: 
	  fun.plot.prep("didname",year,hour,"archivefilename") 
	This will create an plot of the data. Use this 
	plot along with the functions of fun.plot.prep 
	to determine the time window. 
	 Now use the function fun.fastT.cal.get to determine 
	the gain. 
	  fun.fastT.cal.get("didname","adam",channel#, 
	  
	 

PROCEDURE for FAST T cals: 
	 
	 These are notes on fast T cal procedures. 
	 
	Tower work: 
	 
		tools:	2 DVOMs 
			1 small screwdriver 
			1 thermocouple cover with meter unit 
			1 new fast T probe if needed 
			1 long cable to interface to splitter 
			1 splitter box for getting fast T signal 
	 
	 The splitter box allows you to monitor the signal from the 
	fast T while the signal is still going to the ADAM. The 9 
	pin cable going to the fast T along with the long meter 
	cable attach to the splitter. The other end of the splitter 
	goes to the breakout box (attached to the channel for the 
	fast T). 
	 Attach the other end of the meter cable to one of the 
	DVOMs. Set it to dc volts. If the fast T probe is broken 
	the meter will read greater than 5 volts. 
	 Attach the other meter to the thermocouple unit. Set the 
	meter to dc 300 mvolts. Also set the thermocouple unit 
	to degrees C. It will read temperature in degrees C 
	( 12.3 mvolts = 12.3 C). 
	 You want to place these meters such that you can read 
	both of them at the same time when adjusting the bridge. 
	 Replace the fast T probe if required and place the 
	thermocouple unit over the probe. Allow the temperature 
	to stabilize. 
	 
	Adjustment procedure: 
	 
	 While monitoring both meters adjust the offset pot so 
	that the absolute value of the fast T agrees with the 
	thermocouple (remember the output for the fast T should 
	be multiplied by 10). The toggle switch should be in the 
	operate position. Now move the toggle to "cal". There 
	should be a gain of 5 degrees in the fast T output. 
	If not, adjust the gain pot. This may take a few 
	iterations of switching the toggle back and forth. 
	Once this is done you should check the absolute value 
	again. 
	 
	Collection of data set: 
	 
	 In order to determine the true gain you need a data set 
	to look at. Set the toggle switch to zero and leave for 
	 seconds. Now switch the toggle to operate for 5 seconds 
	then to cal for 5 seconds. Repeat this step for at least 
	 times. Set the switch to zero one more time, 
	 seconds, then back to operate. Remove the thermocouple 
	unit. 
	 
	Data Processing: 
	 
	 To compute a gain factor, use Splus to find the 
	proper time period when you were switching the 
	toggle back and forth between operate and cal. 
	This can be done using a fun routine. After 
	getting into Splus open a display window, X11(). 
	Use the following command: 
	  fun.plot.prep("didname",year,hour,"archivefilename") 
	This will create an plot of the data. Use this 
	plot along with the functions of fun.plot.prep 
	to determine the time window. 
	 Now use the function fun.fastT.cal.get to determine 
	the gain. 
	  fun.fastT.cal.get("didname","adam",channel#, 
		day,hour,min,"filename",nummin) 
	 
	This function will provide a graphic display of 
	the data along with a vector of gain values based 
	on each transistion from operate mode to cal mode. 
	NOTE: the vector may have other values based on the 
	value you used for parameter nummin. 
	To calculate the proper gain value to be put into 
	cal_files, save this vector. Apply the vector to 
	the equation below. 
	 
	  gain <- (50/32768)*(5/mean(abs(dT[i:j]))) 
	  
	 This gain value will get loaded into the proper 
	cal file. Look into the directory /home/aster/cal_files 
	for the filename. 
	 
	  
	 

PROCEDURE for FAST T cals: 
	 
	Notes on fast T cal procedures. 
	 
	Tower work: 
	 
		tools:	2 DVOMs 
			1 small screwdriver 
			1 thermocouple cover with meter convertor unit 
			1 splitter box for getting fast T signal 
			1 long cable to connect one DVOM to splitter box 
			1 new fast T probe if needed 
	 
	The splitter box enables the person on the tower adjusting the fast T sensor 
	to monitor the signal without interupting the data flow to ASTER. 
	The box interposes in the data cable run, at the break-out-box. The long cable  
	is attached to the first DVOM carried up the tower. 
	This first DVOM is set on the dcvolt scale. 
	The output shown should read of the order ?.?? dcvolt.   
	 degree C corresponds to ?.? dc volts 
	If the voltage shown is > 5 volts dc then the probe is broken. 
	 
	 The splitter box allows you to monitor the signal from the 
	fast T while on the tower. The signal still goes to the ADAM. The 9 
	pin cable going to the fast T along with the long meter 
	cable attach to the splitter. The other end of the splitter 
	goes to the breakout box (attached to the channel for the 
	fast T). 
	 Attach the other end of the meter cable to one of the 
	DVOMs. Set it to dc volts. If the fast T probe is broken 
	the meter will read greater than 5 volts. 
	 Attach the other meter to the thermocouple unit. Set the 
	meter to dc 300 mvolts. Also set the thermocouple unit 
	to degrees C. It will read temperature in degrees C 
	( 12.3 mvolts = 12.3 C). 
	 You want to place these meters such that you can read 
	both of them at the same time when adjusting the bridge. 
	 Replace the fast T probe if required and place the 
	thermocouple unit over the probe. Allow the temperature 
	to stabilize. 
	 
	Adjustment procedure: 
	 
	 While monitoring both meters adjust the offset pot so 
	that the absolute value of the fast T agrees with the 
	thermocouple (remember the output for the fast T should 
	be multiplied by 10). The toggle switch should be in the 
	operate position. Now move the toggle to "cal". There 
	should be a gain of 5 degrees in the fast T output. 
	If not, adjust the gain pot. This may take a few 
	iterations of switching the toggle back and forth. 
	Once this is done you should check the absolute value 
	again. 
	 
	Collection of data set: 
	 
	 In order to determine the true gain you need a data set 
	to look at. Set the toggle switch to zero and leave for 
	 seconds. Now switch the toggle to operate for 5 seconds 
	then to cal for 5 seconds. Repeat this step for at least 
	 times. Set the switch to zero one more time, 
	 seconds, then back to operate. Remove the thermocouple 
	unit. 
	 
	Data Processing: 
	 
	 To compute a gain factor, use Splus to find the 
	proper time period when you were switching the 
	toggle back and forth between operate and cal. 
	This can be done using a fun routine. After 
	getting into Splus open a display window, X11(). 
	Use the following command: 
	  fun.plot.prep("didname",year,hour,"archivefilename") 
	This will create an plot of the data. Use this 
	plot along with the functions of fun.plot.prep 
	to determine the time window. 
	 Now use the function fun.fastT.cal.get to determine 
	the gain. 
	  fun.fastT.cal.get("didname","adam",channel#, 
		day,hour,min,"filename",nummin) 
	 
	This function will provide a graphic display of 
	the data along with a vector of gain values based 
	on each transistion from operate mode to cal mode. 
	NOTE: the vector may have other values based on the 
	value you used for parameter nummin. 
	To calculate the proper gain value to be put into 
	cal_files, save this vector. Apply the vector to 
	the equation below. 
	 
	  gain <- (50/32768)*(5/mean(abs(dT[i:j]))) 
	  
	 This gain value will get loaded into the proper 
	cal file. Look into the directory /home/aster/cal_files 
	for the filename. 
	 
	  
	 

PROCEDURE for FAST T cals: 
	 
	Notes on fast T cal procedures. 
	 
	TOWER WORK: 
	 
		tools:	2 DVOMs 
			1 small screwdriver 
			1 thermocouple cover with meter convertor unit 
			1 splitter box for getting fast T signal 
			1 long cable to connect one DVOM to splitter box 
			1 new fast T probe if needed 
	 
	The splitter box enables the person on the tower adjusting the fast T sensor 
	to monitor the signal without interupting the data flow to ASTER. 
	The box is interposed in the data cable run at the break-out-box. 
	The long cable is attached to the first DVOM carried up the tower. 
	This first DVOM is set on the dcvolt scale. 
	The output shown should read of the order ?.?? dcvolt.   
	 degree C corresponds to ?.? dc volts 
	If the voltage shown is > 5 volts dc then the probe is broken. 
	 
	The thermocouple unit is attached to the second DVOM which is set on the 
	 mvdc scale. The thermocouple unit is set to Degrees C.  
	The output will read in degrees C. 12.3 mv = 12.3 degrees C. 
	 
	When the fast T system is being adjusted both meters should be hung 
	such that they can be viewed at the same time. 
	 
	The fast T probe is replaced if required and the thermocouple unit 
	is place to enclose the probe. The temperature is allowed to stabilized. 
	 
	 
	ADJUSTMENT PROCEDURE: 
	 
	With the toggle switch in the OPERATE position adjust the ZERO or OFFSET 
	pot so that the absolute value of fast T (the first DVOM value X 101). 
	agrees with the value given by the thermocouple (the second DVOM value). 
	 
	Move the toggle switch to the CAL position. 
	The reading for the fast T  should be 5 degrees C higher than the TC temp. 
	If not adjust the GAIN pot. 
	 
	Iterate if necessary until the temperatures agree to within a few tenths 
	and the JUMP is 5 degrees C +_ 0.2 degrees C 
	 
	 
	COLLECTION OF DATA SET: 
	 
	In order to determine the true gain a data set is needed. 
	To collect such a data set:  
	    set the toggle switch to ZERO and leave for 10 seconds, 
	      set the toggle switch to OPERATE  and leave for 5 seconds, 
	      set the toggle switch to CAL  and leave for 5 seconds, 
	      repeat these OPERATE and CAL sequences at least five times, then 
	    set the toggle switch to ZERO and leave for 10 seconds. 
	 
	Remove the thermocouple unit, chech that the fast T system is still 
	functioning, collect the rest of the equipment, and climb down the tower. 
	 
	 
	DATA PROCESSING: 
	 
	To compute the gain factor use Splus functions, first to recognize 
	the time period when the calibration occured, then to define the  
	actual gain factor. 
	 
	Move to the appropriate directory, viz: /data/DOWNWASH94/raw_data/upwind 
	Evoke Splus and open a graphics window with X11(). 
	 
	 
	Run the Splus function: 
	 fun.plot.prep("didname",year,day,"archivefilename") 
	 fun.plot.prep("t.10m.up",1994,60,"upwind/fast060160000") 
	The program asks for start and stop times. On the first iteration bracket 
	the calibration period and then accurately determine the time window. 
	 
	 
	Now determine the gain with the Splus function" 
	  fun.fastT.cal.get("didname","adam",channel#,day,hour,min,"filename",nummin) 
	  fun.fastT.cal.get("t.10m.up","cosmos",100,60,20,15,"upwind/fast060160000",2) 
	 
	This function will provide a graphic display of 
	the data along with a vector of gain values based 
	on each transistion from operate mode to cal mode. 
	NOTE: the vector may have other values based on the 
	value you used for parameter nummin. 
	To calculate the proper gain value to be put into 
	cal_files, save this vector. Apply the vector to 
	the equation below. 
	 
	  gain <- (50/32768)*(5/mean(abs(dT[i:j]))) 
	  
	 This gain value will get loaded into the proper 
	cal file. Look into the directory /home/aster/cal_files 
	for the filename. 
	 
	  
	 

PROCEDURE for FAST T cals: 
	 
	Notes on fast T cal procedures. 
	 
	TOWER WORK: 
	 
		tools:	2 DVOMs 
			1 small screwdriver 
			1 thermocouple cover with meter convertor unit 
			1 splitter box for getting fast T signal 
			1 long cable to connect one DVOM to splitter box 
			1 new fast T probe if needed 
	 
	The splitter box enables the person on the tower adjusting the fast T sensor 
	to monitor the signal without interupting the data flow to ASTER. 
	The box is interposed in the data cable run at the break-out-box. 
	The long cable from the splitter box is attached to the first DVOM 
	carried up the tower. 
	This first DVOM is set on the dcvolt scale. 
	The output should correspond to (degrees C)/10 volts.   
	Thus 12.3 degree C corresponds to 1.23 volts 
	If the voltage shown is > 5 volts dc then the probe is broken. 
	 
	The thermocouple unit is attached to the second DVOM which is set on the 
	 mvdc scale. The thermocouple unit is set to Degrees C.  
	The output will read in degrees C. 
	Thus 12.3 degrees C corresponds to 12.3 mv. 
	 
	When the fast T system is being adjusted both meters should be hung 
	such that they can be viewed at the same time. 
	 
	The fast T probe is replaced if required and the thermocouple unit 
	is place to enclose the probe. The temperature is allowed to stabilized. 
	 
	 
	ADJUSTMENT PROCEDURE: 
	 
	With the toggle switch in the OPERATE position adjust the ZERO or OFFSET 
	pot so that the value for the fast T (the first DVOM value X 10). 
	agrees with the value given by the thermocouple (the second DVOM value). 
	 
	Move the toggle switch to the CAL position. 
	The reading for the fast T should jump to 5 degrees C higher than the TC temp. 
	If not adjust the GAIN pot. 
	 
	Iterate if necessary until the temperatures agree to within a few tenths 
	and the JUMP is 5 degrees C +_ 0.2 degrees C 
	 
	 
	COLLECTION OF DATA SET: 
	 
	In order to determine the true gain a data set is needed. 
	To collect such a data set:  
	    set the toggle switch to ZERO and leave for 10 seconds, 
	      set the toggle switch to OPERATE  and leave for 5 seconds, 
	      set the toggle switch to CAL  and leave for 5 seconds, 
	      repeat these OPERATE and CAL sequences at least five times, then 
	    set the toggle switch to ZERO and leave for 10 seconds. 
	 
	Remove the thermocouple unit, check that the fast T system is still 
	functioning, collect the rest of the equipment, and climb down the tower. 
	 
	 
	DATA PROCESSING: 
	 
	To compute the gain factor use Splus functions, first to recognize 
	the time period when the calibration occured, then to define the  
	actual gain factor. 
	 
	Move to the appropriate directory, viz: /data/DOWNWASH94/raw_data/upwind 
	Evoke Splus and open a graphics window with X11(). 
	 
	 
	Run the Splus function: 
	 fun.plot.prep("didname",year,day,"archivefilename") 
	 fun.plot.prep("t.10m.up",1994,60,"upwind/fast060160000") 
	The program asks for start and stop times. On the first iteration bracket 
	the calibration period and then accurately determine the time window. 
	 
	 
	Now determine the gain with the Splus function" 
	  fun.fastT.cal.get("didname","adam",channel#,day,hour,min,"filename",nummin) 
	  fun.fastT.cal.get("t.10m.up","cosmos",100,60,20,15,"upwind/fast060160000",2) 
	 
	This function will provide a graphic display of 
	the data along with a vector of gain values based 
	on each transistion from operate mode to cal mode. 
	NOTE: the vector may have other values based on the 
	value you used for parameter nummin. 
	To calculate the proper gain value to be put into 
	cal_files, save this vector. Apply the vector to 
	the equation below. 
	 
	  gain <- (50/32768)*(5/mean(abs(dT[i:j]))) 
	  
	 This gain value will get loaded into the proper 
	cal file. Look into the directory /home/aster/cal_files 
	for the filename. 
	 
	  
	 

Tempory removal of fast T sensors 
	 
	On Wednesday just as the snow started the four fast T sensors were removed from 
	their connectors and stored in labled tube holders. 
	The task was begun at 10:52 local time and completed by 11:10 local time. 
	The task was begun at 15:52 GMT and completed by 16:10 GMT. 
	 
	 

Tempory removal of fast T sensors 
	 
	On Wednesday just as the snow started the four fast T sensors were removed from 
	their connectors and stored in labled tube holders. 
	The task was begun at 10:52 local time and completed by 11:10 local time. 
	The task was begun at 15:52 GMT and completed by 16:10 GMT. 
	 
	 

PROCEDURE for FAST T cals: 
	 
	Notes on fast T cal procedures. 
	 
	TOWER WORK: 
	 
		tools:	2 DVOMs 
			1 small screwdriver 
			1 thermocouple cover with meter convertor unit 
			1 splitter box for getting fast T signal 
			1 long cable to connect one DVOM to splitter box 
			1 new fast T probe if needed 
	 
	The splitter box enables the person on the tower adjusting the fast T sensor 
	to monitor the signal without interupting the data flow to ASTER. 
	The box is interposed in the data cable run at the break-out-box. 
	The long cable from the splitter box is attached to the first DVOM 
	carried up the tower. 
	This first DVOM is set on the dcvolt scale. 
	The output should correspond to (degrees C)/10 volts.   
	Thus 12.3 degree C corresponds to 1.23 volts 
	If the voltage shown is > 5 volts dc then the probe is broken. 
	 
	The thermocouple unit is attached to the second DVOM which is set on the 
	 mvdc scale. The thermocouple unit is set to Degrees C.  
	The output will read in degrees C. 
	Thus 12.3 degrees C corresponds to 12.3 mv. 
	 
	When the fast T system is being adjusted both meters should be hung 
	such that they can be viewed at the same time. 
	 
	The fast T probe is replaced if required and the thermocouple unit 
	is place to enclose the probe. The temperature is allowed to stabilized. 
	 
	 
	ADJUSTMENT PROCEDURE: 
	 
	With the toggle switch in the OPERATE position adjust the ZERO or OFFSET 
	pot so that the value for the fast T (the first DVOM value X 10). 
	agrees with the value given by the thermocouple (the second DVOM value). 
	 
	Move the toggle switch to the CAL position. 
	The reading for the fast T should jump to 5 degrees C higher than the TC temp. 
	If not adjust the GAIN pot. 
	 
	Iterate if necessary until the temperatures agree to within a few tenths 
	and the JUMP is 5 degrees C +_ 0.2 degrees C 
	 
	 
	COLLECTION OF DATA SET: 
	 
	In order to determine the true gain a data set is needed. 
	To collect such a data set:  
	    set the toggle switch to ZERO and leave for 10 seconds, 
	      set the toggle switch to OPERATE  and leave for 5 seconds, 
	      set the toggle switch to CAL  and leave for 5 seconds, 
	      repeat these OPERATE and CAL sequences at least five times, then 
	    set the toggle switch to ZERO and leave for 10 seconds. 
	 
	Remove the thermocouple unit, check that the fast T system is still 
	functioning, collect the rest of the equipment, and climb down the tower. 
	 
	 
	DATA PROCESSING: 
	 
	To compute the gain factor use Splus functions, first to recognize 
	the time period when the calibration occured, then to define the  
	actual gain factor. 
	 
	Move to the appropriate directory, viz: 
	$ASTER/projects/DOWNWASH94/raw_data/upwind 
	Evoke Splus and open a graphics window with X11(). 
	 
	 
	Run the Splus function: 
	 fun.plot.prep("didname",year,day,"archivefilename") 
	 fun.plot.prep("t.10m.up",1994,60,"fast060160000") 
	NB only filename is needed if Splus is evolked from the appropriate directory. 
	The program asks for start and stop times. On the first iteration bracket 
	the calibration period and then accurately determine the time window. 
	 
	 
	Now determine the gain with the Splus function" 
	  fun.fastT.cal.get("didname","adam",channel#,day,hour,min,"filename",nummin) 
	  fun.fastT.cal.get("t.10m.up","cosmos",100,60,20,15,"upwind/fast060160000",2) 
	NB the directory/filename is required even if Splus evolked from appropriate 
	directory 
	 
	This function will provide a graphic display of 
	the data along with a vector of gain values based 
	on each transistion from operate mode to cal mode. 
	NOTE: the vector may have other values based on the 
	value you used for parameter nummin. 
	To calculate the proper gain value to be put into 
	cal_files, save this vector. Apply the vector to 
	the equation below. 
	 
	  gain <- (50/32768)*(5/mean(abs(dT[i:j]))) 
	  
	Then enter : 
	 gain 
	to obtain value of the gain factor. 
	 
	This gain value needs to be loaded into the proper 
	cal file. Look into the directory /home/aster/cal_files 
	for that filename. Edit that file and add the neww information 
	 
	  
	 

 
	morning status 
	 
	Weather: windy with overcast early, with blowing snow commencing at 10:45 
	         wind spedd increasing 
	 
	 
	Plant: Ct is operational, main cyclone has blown a tube and is dead. 
	 
	cav1/cav2: 
	  t.4m.cav1: removed at 11:00 
	  t.10m.cav1: removed at 11:00 
	  psycs: 
	  atik.4m.cav1: ok 
	  atik.10m.cav1: ok  
	  NOx.ENSR: 
	  props: ok  
	  met.ENSR: 
	 
	far: 
	  t.4m.farE removed at 11:00 
	  rain: snow started at 10:45 and sensor responding 
	  radiometers:ok 
	  uw.4m.far:ok 
	  prop:ok 
	 
	upwind: 
	  t.10.up: removed at 11:00 
	  h2o.10m.up:running smoothly although offset 
	  psycs:ok 
	  baro:ok 
	  props: 
	  uw.10m.up:ok 
	 
	Rooftop:will download today 
	 

 
	morning status 
	 
	Weather: windy with overcast early, with blowing snow commencing at 10:45 
	         wind spedd increasing 
	 
	 
	Plant: Ct is operational, main cyclone has blown a tube and is dead. 
	 
	cav1/cav2: 
	  t.4m.cav1: removed at 11:00 
	  t.10m.cav1: removed at 11:00 
	  psycs: 
	  atik.4m.cav1: ok 
	  atik.10m.cav1: ok  
	  NOx.ENSR: 
	  props: ok  
	  met.ENSR: 
	 
	far: 
	  t.4m.farE removed at 11:00 
	  rain: snow started at 10:45 and sensor responding 
	  radiometers:ok 
	  uw.4m.far:ok 
	  prop:ok 
	 
	upwind: 
	  t.10.up: removed at 11:00 
	  h2o.10m.up:running smoothly although offset 
	  psycs:ok 
	  baro:ok 
	  props: 
	  uw.10m.up:ok 
	 
	Rooftop:will download today 
	 

 
	morning status 
	 
	Weather: windy with overcast early, with blowing snow commencing at 10:45 
	         wind spedd increasing 
	 
	 
	Plant: Ct is operational, main cyclone has blown a tube and is dead. 
	 
	cav1/cav2: 
	  t.4m.cav1: removed at 11:00 
	  t.10m.cav1: removed at 11:00 
	  psycs: 
	  atik.4m.cav1: ok 
	  atik.10m.cav1: ok  
	  NOx.ENSR: 
	  props: ok  
	  met.ENSR: 
	 
	far: 
	  t.4m.farE removed at 11:00 
	  rain: snow started at 10:45 and sensor responding 
	  radiometers:ok 
	  uw.4m.far:ok 
	  prop:ok 
	 
	upwind: 
	  t.10.up: removed at 11:00 
	  h2o.10m.up:running smoothly although offset 
	  psycs:ok 
	  baro:ok 
	  props: 
	  uw.10m.up:ok 
	 
	Rooftop:downloaded the logger today at approx 13:00 local time. 
	 

Serial numbers of the prop-vanes 
	 
	To keep track of the suspect props I checked the seial numbers 
	 
	prop.2m.up    cosmos 204     0002 
	prop.6m.up    cosmos 205     0006 
	 
	prop.10m.far  ragwort 201    0004 
	 
	prop.2m.up    marigold  208  0003 
	prop.6m.up    marigold  209  0001 
	prop.10m.up   marigold  210  0005 
	 

 
	morning status  DisASTERous 
	 
	Weather:Overcast with intermittent freezing rain and wind. 
		Last night there was strong wind and snow followed by sleet. 
		A storm surge drove the high tide up over the base of the far site. 
		Ragwort, the electronics for the uw sonic, and the breakout boxes 
		were all submerged in salt water. The short circuit of the Ragwort 
		power system popped the circuit breaker and also switched off power 
		to Marigold and the two cav towers. 
	 
	 
	Plant: 
	 
	cav1/cav2: 
	  t.4m.cav1: 
	  t.10m.cav1: 
	  psycs: 
	  atik.4m.cav1: 
	  atik.10m.cav1: 
	  NOx.ENSR: 
	  props: 
	  met.ENSR: 
	 
	far: 
	  t.4m.far: 
	  rain: 
	  radiometers: 
	  uw.4m.far: 
	  prop: 
	 
	upwind: 
	  t.10.up: 
	  h2o.10m.up: 
	  psycs: 
	  baro: 
	  props: 
	  uw.10m.up: 
	 
	Rooftop: 
	 

 
	morning status  DisASTERous 
	 
	Weather:Overcast with intermittent freezing rain and wind. 
		Last night there was strong wind and snow followed by sleet. 
		A storm surge drove the high tide up over the base of the far site. 
		Ragwort, the electronics for the uw sonic, and the breakout boxes 
		were all submerged in salt water. The short circuit of the Ragwort 
		power system popped the circuit breaker and also switched off power 
		to Marigold and the two cav towers. 
	 
	 
	Plant: cyclone operating 
	 
	cav1/cav2: 
	  t.4m.cav1:sensors removed 
	  t.10m.cav1:sensors removed 
	  psycs:power off 
	  atik.4m.cav1:power off 
	  atik.10m.cav1:iced up 
	  NOx.ENSR: 
	  props: two blade missing on 6m prop 
	  met.ENSR: 
	 
	far:dead in the water. ADAM drowned 
	  t.4m.far:sensor removed 
	  rain: 
	  radiometers:iced over 
	  uw.4m.far:electronics full of sea water 
	  prop:prop and vane blown away 
	 
	upwind: 
	  t.10.up:sensor removed 
	  h2o.10m.up:operating 
	  psycs:operating 
	  baro: perating 
	  props:ok 
	  uw.10m.up:iced up 
	 
	Rooftop:downloaded yesterday 
	 

Damage recovery. 
	 
	Most of Thursday, 3 Mar, was spent doing damage recovery. 
	Cosmos was raised onto a pallet to keep it above the raising water level. The 
	up uw sonic electronics box was also raised. 
	Ragwort and the far uw electronics box were brought into the trailer and 
	their cards stripped out and inspected. 
	The ADAM card did not appear to have been submerged and so were patted dry 
	of the rain drops, wrapped in paper towers and sealed with dessicant in a  
	plastic box.  
	The uw cards were rinsed with DI water and then EtOH. 
	The card cages were both removed, rinsed with DI water, then with EtOH. 
	 

 
	morning status 
	 
	Weather: blue sky without any clouds, moderate wind, chilly 
	 
	 
	Plant: Cyclone operating and CT's available. CT operating for morning demand. 
	 
	cav1/cav2: 
	  t.4m.cav1:sensors still removed 
	  t.10m.cav1:sensor still removed 
	  psycs:10m psyc dead 
	  atik.4m.cav1:ok 
	  atik.10m.cav1:ok 
	  NOx.ENSR: 
	  props:center prop still missing blades 
	  met.ENSR: 
	 
	far:dead 
	  t.4m.far: 
	  rain: 
	  radiometers: 
	  uw.4m.far: 
	  prop: 
	 
	upwind: 
	  t.10.up:sensor still removed 
	  h2o.10m.up:ok 
	  psycs:ok 
	  baro:ok 
	  props:ok 
	  uw.10m.up:ok 
	 
	Rooftop:? 
	 

Replacement of fast T's,(also prop on cav2 and psyc on cav1) 
	 
	At approx 10:00 local time the fast T sensors were replaced on: 
						      t.10m.cav1 
						      t.4m.cav1 
						      t.10m.up 
	         using the sensors which had been removed prior to the storm. 
	The psyc.10m.cav1 was unplugged and replugged 
	The broken propellor on prop.6m.cav2 was replaced with prop# 8, pitch - 302 
	 
	The operations of these sensors was checked back at the trailer. 
	 

Down-load of roof 
	 
	At approx 14:00 local time the roof data logger 
	was down-loaded. Note that the extension ribbon cable was completely shredded. 
	Also the elevator was inoperative. 
	 

Prop pitch entered for prop.6m.cav2 
	 

Prop pitch entered for prop.6m.cav2 
	 
	The correct prop pitch of the new prop (302mm/rev) was 
	entered into the HC11 for prop.6m.cav2 at 4:10pm (21:10Z). 
	The old pitch was 
	 
	 
	 

Prop pitch entered for prop.6m.cav2 
	 
	The correct prop pitch of the new prop (302mm/rev) was 
	entered into the HC11 for prop.6m.cav2 at 4:10pm (21:10Z). 
	The old pitch was 298, I believe.  Since the prop was 
	replaced this morning, the HC11 has been using old pitch. 
	 

 
	morning status 
	 
	Weather:Scattered thin high clouds, light winds, well above freezing. 
	 
	Plant:Cyclone operating, CT available. 
	 
	cav1/cav2: 
	  t.4m.cav1:ok 
	  t.10m.cav1:ok 
	  psycs:ok 
	  atik.4m.cav1:ok 
	  atik.10m.cav1:ok 
	  NOx.ENSR:removed 
	  props:ok 
	  met.ENSR:ok 
	 
	far:dead 
	  t.4m.far: 
	  rain: 
	  radiometers: 
	  uw.4m.far: 
	  prop: 
	 
	upwind: 
	  t.10.up:ok 
	  h2o.10m.up:ok 
	  psycs:ok 
	  baro:ok 
	  props:ok 
	  uw.10m.up:ok 
	 
	Rooftop:downloaded yesterday 
	 

Fast T cals 
	 
	Fast T cals were done before dropping towers. 
	On cav1 the first cals were done at 13:30 (4m) and 13:24 (10m) 
	without using the insulating chamber and then the fast T's were 
	removed.  They were then re-installed 
	back onto the same height and the cal done again with 
	the chamber.  Gain values were put into the cal_files. 
	 
	t.10m.cav1	day 65 14:35:00		0.001558694 
	t.4m.cav1	day 65 14:38:10		0.001473943 
	 
	t.10m.up	day 65 13:58:30		0.00156022 
	 
	 
	 

Put zero wind tube on sonics 
	 
	 
	Archived data with the zero wind tube on the sonics 
	 
	Day 065 somewhere after 1300Z 
	 
	atik.10m.cav1, atik.4m.cav1, uw.10m.up   
	 

Fast T cals 
	 
	Fast T cals were done before dropping towers. 
	On cav1 the first cals were done at 13:30 (4m) and 13:24 (10m) 
	without using the insulating chamber and then the fast T's were 
	removed.  They were then re-installed 
	back onto the same height and the cal done again with 
	the chamber.  Gain values were put into the cal_files. 
	 
	t.10m.cav1	day 65 14:35:00Z	0.001558694 
	t.4m.cav1	day 65 14:38:10Z	0.001473943 
	 
	t.10m.up	day 65 13:58:30Z	0.00156022 
	 
	 
	 

Fast T end cals differ 
	 
	The fast T calibrations performed just before dropping the towers 
	differ somewhat from those done about a week before.  The numbers are: 
	 
			 
	t.10m.up	94 060 200500   0.001538146 
			94 065 200500   0.00156022   +1.4% 
	 
	t.10m.cav1  	94 060 164000   0.001556073 
			94 065 143500   0.001558694  +0.2% 
	 
	t.4m.cav1	94 057 144000   0.001515009 
			94 065 143800   0.001473943  -2.7% 
	 
	t.4m.far	died; no post-cal. 
	 
	I will not change the cal_files, which will cause the post-cals to be 
	ignored.  However, we should state that the gains may be in error by 
	up to 3%. 
	 

uw.10m.up day 065 zero processed 
	 
	Searching the data, guided by comment 132, the following are the times 
	for the zero chamber: 
	 
	A: 14:00:48.090-14:01:27.480 
	B: 14:01:34.530-14:02:14.870 
	C: 14:02:19.170-14:02:54.160 
	 
	Around these times, T=1.8C, rh=52%, p=1026mb from upwind sensors 
	Thus speed-of-sound was:  
	  vpres <- 0.52*fun.satvp(1.8) 
	  mixr <- (0.622*vpres)/(1026-vpres) 
	  spec.hum <- mixr/(1+mixr) 
	  Tv <- (1.8+273.15)*(1+0.61*spec.hum) 
	  cc <- 20.067*sqrt(Tv) 
	results in c = 332.97 m/s 
	Pathlength for path A is 0.1999m, therefore counts should be  
	.1999/332.97 * 4 MHz * 16 up-and-down firings/sample = 38423 counts 
	 
	files were created from archive files by (e.g.):  
	data_dump analog 14:01:34.530 < fast065131406 | grep " 206 " > uw.10m.up.065.B 
	(and manually edited to truncate to the above times) 
	 
	x <- scan("uw.10m.up.065.A",list(it="",id=0,nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	a <- x$a 
	a[a>32767] <- a[a>32767]-65536 
	mean(a[651:674]) = -628 
	mean(x$s[651:674]) = 38930, thus zero S = 38930-38423 = 507 
	 
	x <- scan("uw.10m.up.065.B",list(it="",id=0,nid=0,a=0,b=0,c=0,s=0,stat=0))  
	b <- x$b 
	b[b>32767] <- b[b>32767]-65536 
	median(b[120:610]) = 6 
	 
	x <- scan("uw.10m.up.065.C",list(it="",id=0,nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	c <- x$c 
	c[c>32767] <- c[c>32767]-65536 
	median(c[100:670]) = -63 
	 
	I don't trust the value for A since there were large fluctuations indicating 
	wind leakage.  Also, the value for S might have been off if the zero chamber  
	wasn't kept at air temperature (though Gordon (one of the people doing the  
	cal) should have known this). 
	The values for B and C are quite close to the values determined for day 035, 
	of -2 and -67, respectively. 
	 
	Unless the wind speed comparisons indicate that we should do something  
	different, I think we should not change the zeros from the day 035 values. 
	 
	 

uw.10m.up day 065 zero processed 
	 
	Searching the data, guided by comment 132, the following are the times 
	for the zero chamber: 
	 
	A: 14:00:48.090-14:01:27.480 
	B: 14:01:34.530-14:02:14.870 
	C: 14:02:19.170-14:02:54.160 
	 
	Around these times, T=1.8C, rh=52%, p=1026mb from upwind sensors 
	Thus speed-of-sound was:  
	  vpres <- 0.52*fun.satvp(1.8) 
	  mixr <- (0.622*vpres)/(1026-vpres) 
	  spec.hum <- mixr/(1+mixr) 
	  Tv <- (1.8+273.15)*(1+0.61*spec.hum) 
	  cc <- 20.067*sqrt(Tv) 
	results in c = 332.97 m/s 
	Pathlength for path A is 0.1999m, therefore counts should be  
	.1999/332.97 * 4 MHz * 16 up-and-down firings/sample = 38423 counts 
	 
	files were created from archive files by (e.g.):  
	data_dump analog 14:01:34.530 < fast065131406 | grep " 206 " > uw.10m.up.065.B 
	(and manually edited to truncate to the above times) 
	 
	x <- scan("uw.10m.up.065.A",list(it="",id=0,nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	a <- x$a 
	a[a>32767] <- a[a>32767]-65536 
	mean(a[651:674]) = -628 
	mean(x$s[651:674]) = 38930, thus zero S = 38930-38423 = 507 
	 
	x <- scan("uw.10m.up.065.B",list(it="",id=0,nid=0,a=0,b=0,c=0,s=0,stat=0))  
	b <- x$b 
	b[b>32767] <- b[b>32767]-65536 
	median(b[120:610]) = 6 
	 
	x <- scan("uw.10m.up.065.C",list(it="",id=0,nid=0,a=0,b=0,c=0,s=0,stat=0)) 
	c <- x$c 
	c[c>32767] <- c[c>32767]-65536 
	median(c[100:670]) = -63 
	 
	I don't trust the value for A since there were large fluctuations indicating 
	wind leakage.  Also, the value for S might have been off if the zero chamber  
	wasn't kept at air temperature (though Gordon (one of the people doing the  
	cal) should have known this). 
	The values for B and C are quite close to the values determined for day 035, 
	of -2 and -67, respectively. 
	 
	Unless the wind speed comparisons indicate that we should do something  
	different, I think we should not change the zeros from the day 035 values. 
	 
	P.S. I've just plotted wind speeds from uw.10m.upwind vs. prop.6m.upwind 
	for the entire DOWNWASH project, and see the expected behavior that the 
	prop is about 10% lower than the sonic (except for obvious glitches).   
	Thus, there is no evidence that the A channel really had a bias of -600 
	counts, which would be about 10 m/s.