search

NCAR / ucomp-pipeline

Data processing pipeline for UCoMP
Other
6 stars 3 forks source link

L0 filename #4

Closed mgalloy closed 2 years ago

mgalloy commented 5 years ago

The raw filename should be YYYYMMDD.HHMMSS.ucomp.l0.fts where the date is specified in UT.

Might change l0 to l0mean or l0ave at some point.

bberkeyU commented 5 years ago

Right now the code supports different number of sums/avgs/means/integrations for each extended header. So there is no obvious mean value to plunk into the file names.

mgalloy commented 4 years ago

Example file given on November 14, 2019 is named 20191009.152516.70565.ucomp.FTS. Is there a reason for the 5 decimal place accuracy of the seconds? Will there ever be any files written in the same second? Also, there should be an l0 after comp. and the FTS extension should be lowercase, i.e., the filename should be: 20191009.152516.ucomp.l0.fts unless there is a need for the sub-second resolution in the time.

bberkeyU commented 4 years ago

The system can (and has) taken data at a rate of more than once a second. The 5 decimal places was just a too big to fail number it can be reduced.

Can you remind me what 10 means? Is this something related to wavelengths?