The rlmod and tccon-rlmod subcommands assume that you can provide a single path where all the GEOS met data can be found for the given runlog (and likewise a single --chem-path if needed). For TCCON, this is not true if a runlog crosses 1 Apr 2024, when we switched from GEOS FP-IT to IT.
To support runlogs that similarly cross changes in met products, we could add either an option to these subcommands or additional subcommands that accept a path to a JSON/TOML/etc. file that specifies met paths for different date ranges, e.g.:
[[paths]]
start_date = "2000-01-01"
end_date = "2024-04-01"
met_path = "/data/met/geosfp-it"
chem_path = "/data/chm/geosfp-it"
[[paths]]
start_date = "2024-04-01"
met_path = "/data/met/geos-it"
chem_path = "/data/chm/geos-it"
The
rlmodandtccon-rlmodsubcommands assume that you can provide a single path where all the GEOS met data can be found for the given runlog (and likewise a single--chem-pathif needed). For TCCON, this is not true if a runlog crosses 1 Apr 2024, when we switched from GEOS FP-IT to IT.To support runlogs that similarly cross changes in met products, we could add either an option to these subcommands or additional subcommands that accept a path to a JSON/TOML/etc. file that specifies met paths for different date ranges, e.g.: