- 108: Base, Site base, Fri 04-Jan-2002 16:17:35 MST, Swapped Base Disk Drive
01/04/2002 16:10
Removed disk 'ISFF backup #2'
Installed disk 'ISFF backup #1'
Reboot of aster worked perfectly.
- 96: Base, Site all stns, Wed 19-Dec-2001 10:54:00 MST, archive size and disk capacity
Archive file sizes (Kbyte = 1024 byte) per day:
marigold: 209396
cosmos: 177885
s2: 36642
s3: 36987
aster: 185
total: 461095
The /data disk is: 11442156 Kbytes, so we can store 24 days on /data.
Backup disk #2 is 16547932 Kbytes, which holds 35 days.
Backup disk #1 is slightly larger than #2, something like 18 Gbytes.
Note that these sizes don't include any photos.
- 87: Base, Site base, Mon 10-Dec-2001 18:24:44 MST, aster rebooted several times
I just rebooted aster several times because I swapped /backup before remembering
to put $ASTER/projects/FLOSS on it (with all the photos that I promised to
various visitors today (The Star reporter and the Walden science teachers.)
I think everything is back to the way it should be now.
We're leaving this lovely place.
Bye bye...
- 84: Base, Site base, Mon 10-Dec-2001 11:01:16 MST, restarting serial_ingest
To effect a new sio_converter for the pam data on stn2 you only
needed to send a HUP signal to the stn2 ingest process:
------------- Ingest tasks -------------
host user pid start exectime process
aster aster 1216 Dec09 ? 00:00:12 stn2 4 /dev/usb/ttyUSB0
kill -HUP 1216
serial_ingest then restarts another ingest on that serial port
immediately.
- 82: Base, Site all stns, Sun 09-Dec-2001 18:26:41 MST, rebooted aster
The reason why Xlevel and Ylevel have been bad is that channel config had too
few values for the logger at the bare site (cr10_13, rather than cr10_18).
Since I don't know how to restart ingest for the PAM sites (I tried
ingest_control -r stn2, but this didn't work) and I couldn't reach Gordon,
I simply restarted aster. This appears to have worked (though I still had
to start cockpit stn2 manually).
Now Xlevel and Ylevel.bare appear to be okay.
The biggest problem with the way we were collecting data is that we dropped
all the Qsoilraw.bare values. Thus, it will be extra work to revise the
calibrations for the Qsoil.bare data taken to date.
- 13: Base, Site base, Thu 29-Nov-2001 14:28:14 MST, hourly.csh, daily.csh, and SSH
Crontab executes these scripts on $ASTER/projects/FLOSS01/scripts:
hourly.csh: executed at XX:15 every hour from 06:00 to 22:00.
daily.csh: executed every morning at 06:20 MST
Add commands to these scripts do periodic tasks.
One script that is executed from hourly is update_ip_addr:
update_ip_addr: does an ssh to maclean@linus and copies the current
IP address to /net/aster/projects/FLOSS01/floss_ip_addr
- 2: Base, Site base, Fri 09-Nov-2001 08:15:22 MST, Archive size and scheme
With the 3 sonics on the adams at 60hz the archive sizes are
marigold 67 Mbyte/8 hr = 201 Mbyte/day
cosmos 40 Mbyte/8 hr = 120 Mbyte /day
(no thermocouples on cosmos, and prop vanes at 1 Hz)
SteveO says the thermocouples will run at about 5 Hz and would like
to increase the prop vanes to 5 Hz.
12 thermocouples at 5 hz would be additional 23 Mbyte/day.
The additional prop data is about 25 Mbyte/day.
Eve, one campbell at 20 hz (no krypton/heater yet):
stn2 8.8 Mbyte/ 7.3 hr = 30 Mbyte/day
So the archive will be about 400 Mbyte/day.
This does not include camera images or more than 12 thermocouples.
We will have about 11 Gbyte available on the base system HD,
and 18 Gbyte on the removable HD.
11 Gbyte gives us about 20-25 days archive. So we can keep a second
copy of the files on the removeable HD, and about every 2-3 weeks
someone could swap in another removeable HD, and bring the
other back to Boulder. Hopefully we wouldn't delete any files
on the base until they have been copied to the mass store.
To do this we will need to buy an another 18 Gb HD and its
plastic holder for the Dell latitude module bay.