FLATLAND96: Site none Messages, 32 Entries..

initial log file /net/aster/projects/FLATLAND96/logbook/tklog.log created by tklog

The telephone number of the Champaign Radisson Suites is 
217-398-3400

101 Trade Center Drive
Champaign, IL 61820

It is on the south side of Champaign on Neil St, US-45.


For reservations contact Jeff Edwards @ Radisson.

The ASTER startup script in /etc/rc3.d
now has the SLIP connection to the ADAM (using FreeWave Radio)
commented out until the radio/adam is available and needed.


The file now looks like:.....

#
# Start ASTER processes
#

user=aster

case "$1" in
'start')
     
#     echo " Starting slip on cua/b at 34800 baud"
#     echo "/etc/slattach cua/b 128.117.87.29 128.117.87.30 38400"
#     /etc/slattach cua/b 128.117.87.29 128.117.87.30 38400

#     echo "Adding route to goldenrod"
#     route add host 128.117.87.2 128.117.87.30 1

     echo " Logging in as $user to start ASTER processes..." >/dev/console
     su - $user -c "Aster_Start" >/dev/console 2>&1
     echo " Aster processes started" >/dev/console
    ;;
'stop')
     ;;
esac

Calibration of Q7's previous to 95, as evidenced by serial
numbers prefixed by 94xxx, are off.

Need to adjust the calibration factors we have by:
	positive multiplier	1.159
	negative multiplier	 .9065

This is an issue for SCMS / MARS95 / MicroFronts also.
Very Nice Fellas....

Because we need to move the radiation stand further away from the
ETI / Campbell than what our cables are, Kurt discovered that for

Licor LI200SA:
A BNC extension having less than 75-ohms or so is OK, and 
that equates to a couple hundred feet of RG.

REBs Q7:
Additional cable of tens of meters is OK, provided the
WIRE INSULATION is NOT PVC

In order to place the radiation sensorsso that they would not be shaded
by the PAM mast, I determined the length of the shadow from curves that
John had prepared showing solar elevation vs azimuth for various dates.
I used the data for Aug 21 (longest shadows for locations north of the
PAM mast), latitude 40 deg N.

Length of shadow, r, for object of height h and solar elevation phi

r = h/atan(phi)

	azimuth	elevation	r/h
	------- ---------	---
	360	63 deg		0.51
	345/15	60		0.58
	330/30	57		0.65
	315/45	53		0.75
	300/60	45		1.00
	285/75	34		1.5
	270/90	19		2.9

We originally numbered the PAM stations, from north to south, 1,3,2.
This has been somewhat confusing, so this morning we swapped stations
2 and 3 so that they are now numbered 1,2,3 from north to south.

I changed entry numbers 7-10 and 13 to reflect this change.

The 4 available serial ports will be assigned to:

Aster:	/dev/cua/a	U.S. Robotics DP/PPP to Net66 Internet access
	/dev/cua/b	Freewave Radio SLIP connection to ADAM
			[Not installed as of 6/x/96]

Cocklebur:
	/dev/cua/a	Freewave Radio "eve_rf" to PAMs, 19200-bps
	/dev/cua/b	GPS Time Code Receiver, 4800-bps


EVE_RF:
can be run on cocklebur using the system startup script:
	/etc/rc3.d/S80pam start
or can be terminated using 'stop' instead
It simply runs the polling program with the correct pass parameters,
and writes the log file to /pam/log/eve_rf.log.


GPS:
The GPS program is run every hour on Cocklebur using root cron:

    # Run time_code to get time from GPS receiver. Use -s option to set clock
    #
    0 * * * *       /home/aster/bin/sparcsunos5/time_code -L -s -d /dev/cua/b >> /home/aster/log/time_code.log 2>&1

And on ASTER root cron, 5 minutes later:
    #
    5 * * * *       rdate cocklebur > /dev/null 2>&1

The Startup script for the Internet Connection PAM GOES reader
is in:	/etc/rc3.d/S80pam	for ASTER startup

and a duplicate copy in:	/pam/bin/...

It creates log files in: /pam/log

The program can be initiated using: /etc/rc3.d/S80pam start
and terminated using 'stop'

PPF Data files are put in /data/incoming/ppf/FLATLAND/tcp_ppf

The Startup script for the EVE_RF Polling Program
is in:	/etc/rc3.d/S80pam	for COCKLEBUR startup

It creates log files in: /pam/log/eve_rf.log

The EVE_RF program can be initiated using: /etc/rc3.d/S80pam start
and terminated using 'stop'

PPF Data files are put in /data/incoming/ppf/FLATLAND/eve_rf
These will be processed into netCDF by 'run_pam_file_translators'
and put into /data/ppf/FLATLAND96/eve_rf

I loaded the 'June 12th' version of Burghart's
pam2netCDF translator program.
The old version was renamed to ".old"
The new version allows fields to be generated for even if there is no data.

Soil Moisture 'Shake-n-Bake' Tests:

Date/Time	A	B	C	D	Notes
---------	-----	-----	-----	-----	-----
96/06/15,   wet	33.06	30.23	33.50	30.70	Several dry days since last rain
  ~18:30Z   dry	28.72	26.33	28.98	26.73	(~5).  Before that there were
  Sta-1    diff	 4.34	 3.90	 4.52	 3.97	heavy rains, and in general it's
     (%h2o/Dry)	15.11%	14.81%	15.60%	14.85%	been a very wet year here, up
						until now.
						2 samples taken and mixed: 1
						between rows, 1 closer to corn.
	Campbell Reading, PAM1 18:30Z ~= 31%	See Note on Soil Moisture/temp.

96/06/17,  wet	42.77	52.23	49.75	46.90	Lots of rain last night...a
  ~16:30Z  dry	30.77	37.25	35.31	33.55	really gooey mess.
  Sta-3	  diff	12.00	14.98	14.44	13.35

96/06/19,  wet	34.35	30.29	32.96	35.89	No rain for 2 days
  ~17:30Z  dry	28.63	25.18	27.44	29.96
  Sta-2	  diff	 5.72	 5.11    5.52	 5.93	



96/06/23,  wet	25.86	26.03	30.97	31.07	Rain storm last night in the
  ~17:30Z  dry	21.54	21.65	25.75	25.92	area.  ground somewhat moist
  Sta-2	  diff   4.32	 4.38	 5.22	 5.15	but not a lot


96/06/25,  wet	31.60	27.25	31.18	28.15	No rain since last storm.
  ~17:00Z  dry	26.76	23.04	26.41	23.83	conditions may be about the
  Sta-1	  diff   4.84    4.21    4.77    4.32	same as 6/15 except the corn 
						is taller.

96/07/02   wet  31.51   30.18   30.90   -----   no rain for days. 8cm sample
    ?      dry  29.34   28.04   28.77   -----   taken.
  Sta-1   diff   2.17    2.14    2.13   -----

96/07/02   wet  30.59   30.77   30.20   -----   refer to above
    ?      dry  26.93   27.09   26.59   -----
  Sta-2   diff   3.66    3.68    3.61   -----

96/07/02   wet  30.86   31.05   29.59   -----   refer to above
    ?      dry  26.74   26.79   25.53   -----
  Sta-3   diff   4.12    4.26    4.06   -----

96/07/07   wet  34.10   33.51   36.80   -----   dry conditions
  15:45Z   dry  32.48	31.83	34.96   -----
  Sta 1   diff   1.62    1.68    1.84   -----

96/07/07   wet  27.59	29.37	29.60	-----	dry conditions
  17:00Z   dry	24.96	26.45	26.68   -----
  Sta 2   diff   2.63    2.92    2.92   -----

96/07/07   wet	38.58	32.38	34.28	-----	dry conditions
  17:30Z   dry  35.05	29.47	31.19   -----
  Sta 3   diff   3.53    2.91    3.09   -----


96/07/12   wet	35.76	33.17	30.55	31.52
  18:00Z   dry	34.08	31.73	29.20	30.13
  Sta 1   diff	 1.68	 1.44	 1.35	 1.39

96/07/12   wet	25.64	28.08	29.27	34.60
  17:30Z   dry	23.75	26.05	27.12	32.01
  Sta 2	  diff	 1.89	 2.03	 2.15	 2.59

96/07/12   wet	37.00	33.63	34.77	33.61
  17:00Z   dry	35.06	31.91	32.95	31.86
  Sta 3   diff	 1.94	 1.72	 1.82	 1.75

96/07/15   wet  28.64   26.93   27.15   24.71   special sample just after rain
 ~18:00Z   dry  25.15   23.61   23.79   21.68
  Sta 1   diff   3.49    3.32    3.36    3.03

96/07/15   wet  25.98   22.35   30.92   27.90
 ~18:00Z   dry  22.12   18.91   26.32   23.58
  Sta 2   diff   3.86    3.44    4.60    4.32

96/07/15   wet  29.01   27.79   27.33   27.94
 ~18:00Z   dry  24.88   23.80   23.40   23.90
  Sta 3   diff   4.13    3.99    3.93    4.04

96/07/17   wet  26.04   26.15   25.69   28.48
  17:00Z   dry  22.71   22.84   22.44   24.87
  Sta 1   diff   3.33    3.31    3.25    3.61

96/07/17   wet  24.02   27.38   30.03   28.47
  17:00Z   dry  20.78   23.67   26.12   24.58
  Sta 2   diff   3.24    3.71    3.91    3.89

96/07/17   wet  29.25   31.47   30.79   30.29   This looked the driest.
  17:00Z   dry  25.78   27.73   27.16   26.71   Also, it was the smallest
  Sta 3   diff   3.47    3.74    3.63    3.58   volume (though supposedly same)

96/07/22   wet  25.06   26.41   27.89   28.73   
  17:00Z   dry  20.31   21.38   22.55   23.28
  Sta 1   diff   4.75    5.03    5.34    5.45

96/07/23   wet  27.83   24.61   24.30   32.29
  17:00Z   dry  23.20   20.36   20.15   26.64
  Sta 2   diff   4.63    4.25    4.15    5.65

96/07/23   wet  30.67   27.84   27.06   29.93
  17:00Z   dry  24.52   22.03   21.61   24.01
  Sta 3   diff   6.15    5.81    5.45    5.92

96/07/27   wet  22.97   30.09   26.38   27.25  This looked the wettest.
  17:00Z   dry  18.88   24.62   21.72   22.46
  Sta 1   diff   4.09    5.47    4.66    4.79

96/07/27   wet  31.58   30.84   26.80   34.90
  17:00Z   dry  27.19   26.42   23.05   29.95
  Sta 2   diff   4.39    4.42    3.75    4.95

96/07/27   wet  35.00   30.29   27.51   32.23
  17:00Z   dry  29.90   25.91   23.53   27.54
  Sta 3   diff   5.10    4.38    3.98    4.69

96/08/01   wet  19.17   22.01   21.58   21.90  
  16:00Z   dry  16.32   18.75   18.43   18.70
  Sta 1   diff   2.85    3.26    3.15    3.20

96/08/01   wet  24.95   24.23   28.41   26.89
  16:00Z   dry  22.13   21.49   25.11   23.78
  Sta 2   diff   2.82    2.74    3.30    3.11

96/08/01   wet  20.63   24.73   22.49   26.25
  16:00Z   dry  17.42   20.82   18.98   22.07
  Sta 3   diff   3.21    3.91    3.51    4.18

96/08/06   wet  20.74   22.66   20.92   26.23
  16:00Z   dry  18.08   19.77   18.25   22.87
  Sta 1   diff   2.66    2.89    2.67    3.36

96/08/06   wet  21.97   26.01   19.69   22.56
  16:00Z   dry  20.08   23.70   17.93   20.58
  Sta 2   diff   1.89    2.31    1.76    1.98

96/08/06   wet  23.54   22.56   21.04   27.82
  16:00Z   dry  20.53   19.64   18.33   24.22
  Sta 3   diff   3.01    2.92    2.71    3.60

96/08/12   wet  32.96   36.46   45.86   33.38
  17:00Z   dry  29.31   32.34   40.82   29.74
  Sta 1   diff   3.65    4.12    5.04    3.64

96/08/12   wet  37.36   32.77   30.52   31.46
  17:00Z   dry  33.41   29.53   27.42   28.19
  Sta 2   diff   3.95    3.24    3.10    3.27

96/08/12   wet  30.58   33.36   27.57   33.99
  17:00Z   dry  27.31   29.71   24.52   30.40
  Sta 3   diff   3.27    3.65    3.05    3.59

96/08/20   wet  42.93   48.67   45.03   41.35
  17:30Z   dry  33.84   38.23   35.41   32.50
  Sta 1   diff   9.09   10.44   9.62     8.85

96/08/20   wet  35.03   24.42   32.45   33.66
  16:30    dry  28.42   19.58   26.31   27.17
  Sta 2   diff   6.61    4.84    6.14    6.49

96/08/20   wet  41.20   41.58   43.67   46.04
  17:00    dry  32.48   32.83   34.56   36.28
  Sta 3   diff   8.72    8.75    9.11    9.76

Campbell Soil Moisture Probes
all appear to have a significant temperature dependence that
causes about a 3-5% diurnal change when the soil temperature
varies about 10-20 degrees.

I don't know the specifics of the sensor enough to say whether
this is a real problem or not (need to R.T.F.M.!), but that does
appear to be the case.
....
YES, the Campbell manual does include a reference and a description
of a temperature correction equation.  That has not been put into 
the Campbell software program, or in EVE yet.

I finally got around to copying down Matt's new version of TKLOG which
is designed to work with his Paradox file import stuff on the PC for
grabbing station visit reports generated on the Compaq.

old version saved in: /home/aster/apps/tklog/tklog.save.working

Removed Message Types PAM1,PAM2,PAM3 because we're now using the site number for
that.  Matt's stuff will recognize that convention.

Daily Status JD168

Weather:	Mostly overcast.  Hot.
		Strong T-storms in afternoon, ~5pm through 7,
		rain continued off and on until 2am local 

Data System:	Up
    Tcp_ppf:	Poor Phone line after rain, mostly down through mid-JD169
    Eve_rf:	Up, fully recording data.
    Softw:	Uploading of metppf translation
		Found problem with pam2netCDF translation because packet length 
		was 1 byte off because of the CR on the DOS file terminator.

Sensors:
	Under-reporting problem with ETI


PAM Stations:
	All Up.

Site Visits:
	3	Tsfc sensor put online
		Checked ATI ground
		ETI test: 
		Download of metppf data

Wayne Angevine noticed interference on the 915 UHF profiler
from the Freewave radios.  This amounted to raising his noise
floor from about 12db to as much as 24.

A series of tests were performed to try to reduce or eliminate
the problem.
	- Reduced signal power to about 5 then 3: no luck,
	still had interference, but that was where i lost comms.
	- Lowered the antenna.  It had probably been 'seeing'
	the profiler.  This helped, but not enough.
	- Rotated the lowered antenna and put power level at 4.
	This produced the best results, reducing the noise floor
	to 13-15, except for one axis: west, which remained up 
	at about 18 (possibly from atmospheric reflects, the
	antenna was shooting to the west of the profiler, or else
	reflection from a nearby Rohn tower).

Results:
	- The interference is configuration dependent.  Some attempts 
	improved one of the beams, but degraded others.   There's no
	doubt interaction with the distance, pointing angle and surrounding
	structures.

	- No configuration is acceptable to Wayne with the old
	Freewave radios.
	this is because he already has marginal signal levels, esp.
	at the middle height range gates.  

	- Wayne may be willing to allow us to have comms, except
	Between the hours:	9am - 5pm local.
	Those are his peak periods of interest.


New Radios Test:
	The new models of Freewave radios scan from 921-928.
	These are the ones we plan to use for aster.

	No Problem with these!
	We tried running the new radios in the 'worst' configuration
	from before (full power, raised yaggi pointing over the profiler)
	and Wayne didn't see any interference.

In case the programmed setting is lost on the Fluke Scopemeter, the
settings required for looking at the sonic received pulses are:

Channel A: 2V DC w/ 10:1 probe
Channel B: 5V DC w/ 10:1 probe
Time sweep: 20 microsec/div
Trigger: B; positive slope; level=3V

Gordon has revised the method for inputing time to the dailyplot
routines, enabling an arbitrary starting time and length.  The new
method for passing time to the routines is via the function dpar(),
which is like par():

Prior to making the first dailyplot within an S session you must 
execute dpar, e.g.

dpar(year=1996, mon=6, day=15, hour=12, lenhr=24)

Then fun.xxxx.plot will produce a 24 hour plot beginning at 12:00 gmt on
June 15.  Subsequently dpar(day=20) will produce the same plot for June
20 or dpar(lenhr=96) will produce a plot of 4 days of data.

dpar.next() and dpar.prev() will increment dpar()$hour by + or -
dpar()$lenhr.  

dpar.now() gives a plot ending at the present time and is also a handy
way to initialize dpar at the beginning of a session.  dpar.now() is
currently executed by $ASTER/.Data/.First()

Try dplot() to get a graphical interface to the dailyplots in the
daily_S_plots script.  Provide comments and feedback to Gordon.

Measure and record the crop heights at each station on a regular
basis.  Most stations are at intersections of different plantings, so
the crop height will be different in different directions.  These are
recorded in a logbook entry dated June 17.  Station photos should be made
on perhaps a weekly or bi-weekly basis to record the changes in the
crops.  Take some regular photos also of the crop under the net
radiometer, over the soil sensors, and under the Everest.

Don't trample the crops under the net radiometer, over the soil sensors
or under the Everest IRT.  The Everest footprint extends along a line
to the NW of the station and between 7m and 13 m from the station.  The
footprint width (in the SW/NE direction) is about 3m.

Keep the sonics at a height between 3 and 4 meters above the top of the
crop canopy to the SW of the station.  Don't forget to relevel the
sonic after you move it.  The sonic height (above the ground) can be
determined by measuring along the lowered mast to the hinge point and
then measuring from the hinge point to the surface.  The sonic heights
are recorded in a logbook entry dated June 25.

There are no filters on the bandpass hygrometer 50Ys.  Steve Semmer will
determine a maintenance procedure for cleaning these.

Take soil samples and make gravimetric soil moisture measurements as
often as possible.

ETI Checks today:

Jerry Price could reproduce the dropped coef. only by 'sparking' the
input power, these tests were to check out the possibility of 'dirty'
power causing our problem.

Station 3, s/n51
----------------
When i arrived and checked the eeprom cal coefficients, they were OK.
This station has definitely been power cycled since they were loaded.


Station 1, s/n57
----------------
This is the A/C powered station.  The power system was stabilized yesterday
with the addition of a battery box, in between the DC supply and PAM.
The voltage is around 12.5-13 and is rock (granite, not pumice that is) solid. 

Coef. were dumped when i arrived.
Programmed them in, and cycled power hoping that they'd stay programmed..
....foolish me. 
Test for unusual power up glitching.
The scopemeter was setup to trigger/record the positive slope.  Coef. were 
loaded and verified and power was cycled.  The waveform rose from 0 to 
10V within 250microSec, 12 within 600microSec, and stabilized at 12.5 within
1.2mS: no glitches, signal was very clean.  The Coefficients however, suffered
greatly.
Test for unusual power down glitching.
After confirming the power up looks good, i decided to look at the power down.
It dropped from 12.5 to 4 within 200microSec.  It did take
3mS to drop from 4 to 2Volts, and the scope memory trace didn't have enough
to show the wave all the way to 0, but it was a very clean signal.  However,
the reprogrammed coefficients suffered greatly.

I tried these tests both with and without the PC attached.
It may well be that ETI s/n #57 and #58 are the only ones having this problem,
because #51 did retain it's coefficients after i programmed them in several
days ago.

Jerry Price had recommended to put a small 12V battery in the gauges just to
keep them up until returning to Boulder.  We may do that because frankly this
isn't important enough for this project to continue right now.

 The Boulder connection went down sometime this morning.
ISS was also down so I would assume it had something to
do with the local netrwork link. System was back up at
13:55 GMT.

Moved the crontab entries to run the netcdf file translators from
militzer to aster acount.

  I created this log for the purpose of monitoring
the status of the systems and sensors. It is not a
comprehensive check of everything. The purpose is to
help decide what needs immediate attention.

  I added some code to allow for direction
changes in sonic booms as they are moved up the
mast. This was done because station 2 sonic was
moved yesterday.

  It appears GOES is down in Boulder. The last available
data from Boulder was ~12:30 GMT. Will send a message to
Boulder.

  I modified daily_S_plots to included the temperature
and relative humidity data, from cosmos, in the temperature
and humidity daily plots. This confirmed EVE and cosmos have
the same coefficients for the sensor.

When Tom requested an upload of 'eve_rf' data to cover the GOES outage
a few days ago, I put together on steam:
	/rdss/pam/bin/rcp_flatland_data

It is being run under my crontab at 1:15 every day to automatically copy
'yesterday's ppf file.   That file is subsequently converted to netCDF by
Matt's crontab initiation of the 'run_pam_file_translators'
It can be run for any day by using:
	rcp_flatland_data 1-jul-96
(or)	rcp_flatland_data 960701
etc.
It first checks to see if the file is there, and thus that the net is up also.
If the net's down, it waits 5-minutes and trys again.  You can change the
default limit (12) on the number of these retry attempts by using:
	rcp_flatland_data -r 3

Rain restarted here about an hour ago (another rainband is coming through).
This was enough to make all the sonics die (wind and temperature).  Hopefully,
they'll come back as the rain diminishes.

Greg has given us other documents relevant to ozone operations which I've
put in $ASTER/projects/FLATLAND/doc:

close.dwn - packing instructions for the sensor
spares.lst - list of spare parts kept on site

Since Greg would like us to look at ozone spectra, I thought it would be 
useful to review here how to obtain values for white noise levels.
Since white noise, by definition, has the same amplitude at all frequencies,
its total variance is simply the average amplitude of the spectra where
noise is observed (usually the high frequencies) times the bandwidth of the
data.  The bandwidth of the data is from 1/averaging period, which is usually
small so we call it 0, to the Nyquist frequency.  However, the Nyquist 
frequency also is the highest frequency plotted on power spectral plots.

THEREFORE, the variance due to white noise is simply the amplitude of the
power spectra at the highest frequency (usually 5 or 10 Hz) when plotted as 
frequency * spectra (which is the default in fun.plot.prep).  The standard 
deviation is the square root of this variance.

For example, the attached spectral plot from an hour ago shows white noise
on conc.O3 with a variance of 0.002 V^2, which gives a standard deviation
of 0.04 V (or 0.8ppb with Greg's nominal gain of 20).  This is the same value
that we saw a few days ago when Greg installed this instrument. 
h2o.csi has no white noise (yeah!).  
Both w.atik and tc.atik appear to have noise at 0.025 (m/s)^2 = 0.16 m/s 
and 0.007 C^2 = 0.03 C respectively, but this is an artifact of combining
10 sample/sec and 20 sample/sec data.

We had light rain about 04Z at the Radisson last night, but none of the
stations saw it.