| Files | Time [UT] | Comments | Cnt | S | Ope |
|---|
| L20030225_000 | 02:51:45 | Start of experiment | 987 | 0 | EG |
| L20030225_001 | 05:50:40 | Sdoium system tuned | 963 | 0 | EG |
| L20030225_001 | 05:50:51 | Rayeleigh HG tweeked for the hell of it | 963 | 0 | EG |
| L20030225_001 | 05:51:53 | Counts | 1132 | 0 | EG |
| L20030225_001 | 05:54:36 | very thin cirrus at 10km starting to be visible in the beam | 939 | 0 | EG |
| L20030225_001 | 06:06:42 | Radar started at 05:58UT | 706 | 0 | EG |
| L20030225_001 | 06:35:21 | Bad trigger | | 0 | EG |
| L20030225_001 | 06:35:28 | I set the scope up to aquire timing jitter and it appears as | 1068 | 0 | EG |
| | if the ARCLITE program unit is emitting triggers out of | | | |
| | timing as I could see after this bad trigger that program unit | | | |
| | supplyed a bad trigger . Next step to see if this is also the | | | |
| | case from the chopper circuit. Looks like this method will | | | |
| | do the trick in isolating the source of the bad triggers. | | | |
| L20030225_001 | 06:46:19 | Cirrus gone for the moment | 1157 | 0 | EG |
| L20030225_002 | 08:23:25 | Pausing data aq for chopper characterization setup | | 0 | EG |
| L20030225_002 | 08:29:14 | Starting chopper function acqusition | 167 | 0 | EG |
| L20030225_002 | 08:41:23 | Ending chopper function acq. | | 0 | EG |
| L20030225_002 | 08:41:43 | End of experiment | | 0 | EG |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |