| Files | Time [UT] | Comments | Cnt | S | Ope |
|---|
| L20051204_000 | 18:25:16 | Start of experiment | 679 | 0 | EG |
| L20051204_000 | 18:37:31 | Nice and clear skies, Dye needs changing. | | 0 | EG |
| L20051204_000 | 18:37:48 | tuning | | 0 | EG |
| L20051204_000 | 18:40:32 | Done tuning sodium to 589.158nm | 604 | 0 | EG |
| L20051204_000 | 18:42:17 | Interesting! The sodium densitiy has fallen. Looks like the | | 0 | EG |
| | reelignment of the wavemeter has shift the best reading. | | | |
| | Tuning back to establish the setting yeilding the highsest | | | |
| | sodium counts. | | | |
| L20051204_000 | 18:51:27 | NO change observed when tuning from 589.159nm to | | 0 | EG |
| | 589.160nm. Looks like the optimum wavelengths as seen on | | | |
| | the wavemeter when sodium returns from lidar are the highest | | | |
| | is at 159.159nm. This is a wavelength reading shift of 1pm | 603 | | |
| L20051204_000 | 18:53:34 | Note on PC crashes. Found a runaway process on PC belonging | | 0 | EG |
| | the the norton realtime scan engine. ARCLITE starved of | | | |
| | CPU cycles. Removed the offending application and installed | | | |
| | a more recent version of the program. Looks ok now. | | | |
| L20051204_000 | 19:51:56 | Sodium HG adjusted. Warmup time not sufficient hence | 557 | 0 | EG |
| | HG drift during the first hour. Tweeked HG back to max energy | | | |
| L20051204_001 | 22:10:38 | Converged Sodiumn | | 0 | EG |
| L20051204_001 | 22:34:14 | Sodium HG tweeked to max | 638 | 0 | EG |
| L20051204_001 | 22:36:53 | Restarted Data collection software, Raleyigh frozen | 638 | 0 | EG |
| | looks like I still have a problem with the service threads! | | | |
| L20051204_002 | 23:17:34 | counts | 738 | 0 | EG |
| L20051204_002 | 23:19:19 | End of experiment | 730 | 0 | EG |