Jonathan, Dave:

we were reminded this week of a second trend NDS1 issue if the user asks for data which spans a DAQ restart. NDS1 has an optimization turned on which reads the channel list from the first second trend frame file in the time sequence and applies it to all subsequent files. It looks for a missing file as an indicator the DAQ was restarted and the channel list needs to be re-read. This worked when second trend frame files were one minute in length, but does not work when they were extended to ten minutes in length.

The temporary solution is that I will rename the partial second trend frame file by pre-pending a dot (ditto with its associated md5 file) after I have ascertained that LDAS has archived the file.

The attached dataviewer one hour second trend plots of the EX building outside temperature spanning yesterday's DAQ restart show a before and after this fix was applied. Before the fix the temperature went from 99F to +/-400F, after the fix the correct temperature is shown with a 10 minute data gap.

The long term fix is to use the run-number in the frame header as a channel configuration index.