search

FlexTRKR / PyFLEXTRKR

PyFlexTRKR
Other
72 stars 22 forks source link

Tracking did not restart as expected while tracking MCS #90

Closed jiligulu-cqs closed 3 months ago

jiligulu-cqs commented 6 months ago

Hi While tracking MCS, I find that although in Step 1 it can identify the input data has too many missing values, thus omit the time frame (no cloudid file generate as expected). But tracking did not restart as expected by the timegap: 3.1 in config file. As two figures below, the time gap is over 3.1 hours. This tracking is using demo_mcs_imerg.sh and config_imerg_mcs_tbpf_example.yml, I only change the input file and modify the start&end date. Same issue also occur when I delete some input files between start date and end date, or using sample GPM IMERG Tb+Precipitation data. 20220908_073000 20220909_023000

feng045 commented 3 months ago

This bug has been fixed in #92, specifically in this commit that fixed pyflextrkr/gettracks.py. Please pull the latest version and test it.

jiligulu-cqs commented 3 months ago

Thanks, now it works as expected.