| Files | Time [UT] | Comments | Cnt | S | Ope |
|---|
| L20030226_000 | 23:42:35 | Start of experiment | | 0 | EG |
| L20030226_000 | 23:44:48 | Taking chopper data | | 0 | EG |
| L20030226_000 | 23:52:45 | Stopped taking chopper data, going into normal data taking | | 0 | EG |
| L20030226_000 | 23:55:43 | started normal data taking | | 0 | EG |
| L20030226_000 | 00:01:13 | Converged the Rayleigh system | 600 | 0 | EG |
| L20030226_000 | 00:05:53 | Counts | 1062 | 0 | EG |
| L20030226_000 | 00:24:20 | Measured the dye laser energy and adjusted HG for max | 1058 | 0 | EG |
| L20030226_000 | 00:49:23 | Signal attenuated a bt due to a thin cirrus cloud in the beam | 978 | 0 | EG |
| L20030226_000 | 01:14:37 | Cirrus cloud no longer in the beam path. | 1002 | 0 | EG |
| L20030227_000 | 02:43:43 | Bad trigger on sodium | 1030 | 0 | EG |
| L20030227_000 | 02:44:21 | System note. Have been monitoring chopper performance | | 0 | EG |
| | looking for loss of phase lock. The infinite persistance | | | |
| | does not show any loss of phase lock. This indicates | | | |
| | that the chopper is not the cause of the false triggers. Will | | | |
| | be monitoring the output of the chopper delay unit to see | | | |
| | if that is causing spurious triggers (for the rest of the run) | | | |
| L20030227_000 | 02:48:52 | Tuned the dye laser. | 1025 | 0 | EG |
| L20030227_000 | 03:03:03 | Thin cirrus interfering again | 705 | 0 | EG |
| L20030227_000 | 03:21:25 | Clouds getting worse | 471 | 0 | EG |
| L20030227_000 | 04:19:13 | Tuned sodium system | 841 | 0 | EG |
| L20030227_000 | 04:34:47 | Cloud thickness increasing, will probably not continue with | 223 | 0 | EG |
| | a TIMED/SABER radar run as inteded, | | | |
| L20030227_001 | 05:09:38 | heavy cloud cover, shutting down | 0 | 0 | EG |
| L20030227_001 | 05:10:00 | End of experiment | 0 | 0 | EG |