Question: how to handle overlap functions
overlap functions are provided in nc files. these are SENSOR (laser) specific. This means, if an optical module of a sensor is updated, a new overlap function needs to be applied. the correction is hence linked to the "optical module ID" (serial number of the laser).
Question: how do we pass the name of the overlap file to the STRATfinder code?
Where do we find the information on optical moduel ID?
- Recent versions of the e-profile L1 data have this information in the global attributes. Problem: hold versions of raw2L1 apparently did not include this information. So not all files that we are processing have this info.
- I included the info into the site specific config.json files. This would require manual updates when a new laser is being used. In any case, we need to have a new overlap correction created. so this would not be a big issue.
How do we locate the file?
- at the moment, I included the optical module ID into the file name of the overlap correction nc file.
- Clement only provides the path of the file location and then I locate the correct file within STRATfinder.
- Clement locates the optical module ID for a given day using either the nc global attributes or the changelog information in the configuration.json file.
@claplace what do you think? cc @marc-antoine.drouin