station:

The LMA station identifier

name:

The LMA station name:


dc3_bRodenberg
dc3_cBriggsdale School
dc3_dLone Tree
dc3_eGreeley Airport
dc3_fRaymer
dc3_gFort Collins/Loveland Airport
dc3_hHereford (Derksen)
dc3_iWiggins High School
dc3_jHomestead
dc3_kPurcell
dc3_nUSDA Central Plains Experimental Range
dc3_pWeld Central High School, Keenesburg
dc3_rButte Edge
dc3_sBoyer
dc3_tFMA

status:

"up" indicates the LMA station is talking. "offline" indicates the LMA station did not report its health, so is probably down.

sdate:

The Linux system date, from the BIOS clock.

stime:

The Linux system time, from the BIOS clock.

load:

The system load. x/y/z minute load average. x = 1 minute average, y = 5 minute average, z = 15 minute average. Unless doing something major, these numbers should all be much less than unity. (The one minute one might vary a bit, but for sure, you should generally see the 15 minute average be very close to zero, or else there may be a process consuming too much of the CPU.)

uptime:

The amount of time since the last reboot, usually in days, if no days label, it's in hours or minutes.

duty time

The percentage of time the system has taken data in the past 30 days

/

The percent of full capacity for the / partition. (/ is where the core OS is located.) Should always be in the neighborhood of 80-90%. LMA data gets stored on separate partitions (see below).

/boot

The percent of full capacity for the /boot partition if there is one.

/dev/shm

The percent of full capacity for the /dev/shm filesystem.

/var/log

The percent of full capacity for the /var/log filesystem.

/data:

The percent of full capacity for the /data partition. This is the primary data partition for the USB solid-state hard-disk.

PID:

This is the process ID for the lma_DataHandler program (the program which actually collects data from the LMA board, and writes it to shared memory). If there's a number there, then it is running. If there isn't a number, there is a problem. Note, no checking is done to ensure that only one process is running, so this isn't a perfect test, but if there's a number there, and the rest of the other things below are okay, we are golden.

PIDRD:

This is the process ID of the lma_ReadData program, the daemon which reads LMA data out of shared memory and writes it to a data file.

PIDTL:

This is the process ID of the lma_TrigLog program, the daemon which reads LMA status out of shared memory and writes it to a trigger file.

PIDAT:

This is the process ID of the lma_AutoThresh program, the daemon which adjusts the threshold.

PIDDEC:

This is the process ID of the lma_Decimate program, the daemon which reads LMA data out of shared memory, decimates it, and sends it to the real-time processing computer.

Phase:

The phase count of the oscillator -- the difference between 25,000,000 and the actual number of cycles for the local data clock.

pdate:

This is the date, as reported by LMA board. This is coming straight off the GPS, so it damn well better be correct.

ptime:

This is the time, as reported by the LMA board.

temp:

This is the temperature (Celsius) of the LMA board.

gps:

The number of satellites being tracked by the GPS receiver, as reported by the LMA board.

current trigfile:

The name of the current trigger log file, for a recent second. (Trigger logs are found in the directory /home/lma/log/.)

trig ID:

The station letter, as reported in the trigger log, for a recent second.

tdate:

The date, as reported in the trigger log file, for a recent second.

ttime:

The time, are reported in the trigger log file, for a recent second.

tver:

The firmware version for the LMA board, as reported in the trigger log file, for a recent second.

tthresh:

The threshold (in dBm) of the station, as reported in the trigger log file, for a recent second.

ttrigs/s:

The current trigger rate as reported by the trigger log file, for a recent second.

tsat:

The number of satellites being tracked by the GPS receiver, as reported in the trigger log file, for a recent second.

ttemp:

The temperature (Celsius) as reported in the trigger log file, for a recent second.

files today

This is the count of number of data files collected for the current day. There should be 6 ten-minute files per hour.

files today-1

This is the count of number of data files collected for yesterday. If all is well, this should be 144 (6 files per hour times 24 hours).

files today-2

This is the count of number of data files collected for two days ago. If all is well, this should be 144 (6 files per hour times 24 hours).

current datafile:

The data file which the lma_DataHandler program is current writing to (assuming it is currently active, otherwise it would be the one last written to). The data files are in the directory /home/lma/data/YYMMDD.

pv voltage

Voltage out of solar panel

batt voltage

Voltage out of battery

load voltage

Voltage to load

bytes/month

Number of bytes transfered over PPP interface this month

decimation status

This indicates whether the decimation process has stopped working. (The decimation can stop working when the ppp connection dies -- the decimation program tries to send data to a no-longer-active ppp connection, which hangs the program.) If so, log onto the station and give the command "/root/bin/lma_restart.pl". There is a cron process which checks to make sure the decimation program is active, so this should be done automatically.