For building the fog database, fogtools relies on the SAFNWC software to produce cloud microphysics (CMIC) files.
ABI operates in modes M3 and M6. Although both are supported by SAFNWC, they need a different set of configuration files. Moreover, there is a different calibration file (Gen_Info_goes16.asc) for data before 2019-04-23. I don't know if the SAFNWC software can switch dynamically between configuration files, or if this needs a software restart. Either way, if I want a fog database containing cases from both before and after 2019-04-23, fogtools needs to interact with SAFNWC in a way to swap out these files depending on what needs to run.
For building the fog database, fogtools relies on the SAFNWC software to produce cloud microphysics (CMIC) files.
ABI operates in modes M3 and M6. Although both are supported by SAFNWC, they need a different set of configuration files. Moreover, there is a different calibration file (Gen_Info_goes16.asc) for data before 2019-04-23. I don't know if the SAFNWC software can switch dynamically between configuration files, or if this needs a software restart. Either way, if I want a fog database containing cases from both before and after 2019-04-23, fogtools needs to interact with SAFNWC in a way to swap out these files depending on what needs to run.
See also https://ninjoservices.dwd.de/wiki/display/SATMET/NWC+SAF+Software