Changes to make for ESS-DIVE work

[bpbond]

From the proposal:

We will...leverage our existing lightweight and performant processing pipeline to produce a generalized ‘template’ repository for handling sensor data and generating ESS-DIVE compliant metadata

We will then fork the existing COMPASS-FME sensor data processing pipeline into a new repository. This is a desirable starting point because of its use of the Quarto document-publishing format for documentation and logging; highly-parallelized design for computational performance; and extensive, high-quality unit testing. References to COMPASS-FME will be removed throughout the code, support files, and documentation. Several features will be added to make the processing template more usable for general users, including support for data in arbitrary time zones, and extensive documentation on the inputs.

We will focus on Campbell’s default “TOA5” file format; if time and budget permit, we may extend the software to support other formats. We anticipate retaining the multiple-data-level design of our original processing pipeline, in which “Raw” data are processed to “L0” (close to Raw) and then “L1” (units converted, flags and metadata added). The details of these data levels may be modified based on the results of the initial community-consultation step described above, but we will keep this step general rather than prescriptive, given the likelihood of widely divergent opinions and experiences here.

[bpbond]

Opening this issue for planning. The text above is helpful in terms of the major steps:

• Remove COMPASS-FME references, changing to $PROJECT I assume
• Arbitrary time zone data; right now we assume EST
• More documentation - see Abstraction and documentation #262
• Fork into new template repository - either example or literally a template repository