These logs should make it easy to determine after the fact what happened with the various processing steps. For example, if fogpy notes
[INFO: 2020-06-09 16:06:46 : fogpy.filters] Filter results for LowCloudFilter
Filtering low clouds for satellite images.
Array size: 2098980
Masking: 2098980
Previous masked: 2098970
New filtered: 10
Remaining: 0
like it does when running
show-fog /media/x21308/plots_and_maps/2020/06/09/fog-20180313-1545 --abi /media/x22264/cache/fogtools/fogdb/abi/2018/03/13/15/C*/OR_ABI-L1b-RadF-M3C*_G16_s20180721545*_e201807215*_c2018072*.nc --nwcsaf /media/x22264/nwcsaf/export/CMIC/S_NWC_CMIC_GOES16_NEW-ENGLAND-NR_20180313T154542Z.nc -a new-england-1000 -i -d
then we know no fog was found. Perhaps the fog-db should warn or even raise an error on this. Maybe fogpy should shout more loudly here too; the message is quasi hidden from view.
gerritholl
commented
4 years ago
The fog database should keep logs, perhaps in the user log directory with the help of appdirs https://pypi.org/project/appdirs/
These logs should make it easy to determine after the fact what happened with the various processing steps. For example, if fogpy notes
like it does when running
then we know no fog was found. Perhaps the fog-db should warn or even raise an error on this. Maybe fogpy should shout more loudly here too; the message is quasi hidden from view.