This includes the following changes (details in commit messages):
Creation of a generic config_template.yaml that includes the structure for SATELLITE_USING_PRESSURE_EDGES and SATELLITE_USING_PRESSURE_CENTERS
Update to the standard config file to include OCO2_v11.1 (preprocessed) and to add the QUALITY_FLAG to TROPOMI for the sake of consistency
Addition of a read_satellite_file generic function to parsers.py. This will need to be edited once we figure out how these parsers are called in the actual operator script.
Additionally, I encountered a few other hiccups.
First, we need to know which files to read when so that we are able to match up the satellite and model observation times. A few options here:
We could add a preprocessing step in which we iterate through all the provided satellite files and resave them with "TIMEMIN_TIMEMAX" appended to the end of the file names so that we can match it to the daily or monthly GEOS-Chem files.
We could require that the user provides the satellite file name structures (this actually makes some sense regardless) with some YYYYMMDD key.
Second, we need to know the temporal resolution at which to apply the operator. Should we do this for daily observations? Monthly? Or up to some number of observations? This could also be provided as an option in the config file.
As we begin to figure these things out, we should also make some sort of create_model_columns.py file that actually applies the functions in order (much like your example for Sarah).
This includes the following changes (details in commit messages):
Additionally, I encountered a few other hiccups.
First, we need to know which files to read when so that we are able to match up the satellite and model observation times. A few options here:
Second, we need to know the temporal resolution at which to apply the operator. Should we do this for daily observations? Monthly? Or up to some number of observations? This could also be provided as an option in the config file.
As we begin to figure these things out, we should also make some sort of create_model_columns.py file that actually applies the functions in order (much like your example for Sarah).