number of relevant VNP02IMG.v2 scenes for DOWNLOADER and PRE_SE_ROOT is different

[Bich Tran]

It’s not really a bug but I noticed that when downloader is interrupted (due to server error, corrupted files, etc.), I re-run pywapor script and the number of relevant VNP02IMG.v2 scenes is different.

It turned out that the DOWNLOADER module found a different number of relevant scenes than PRE_SE_ROOT module.

I would not expect different number because the period and area is the same.

Attached is log.text, python script, config file, and zipped VIIRS cache folder

[bert.coerver]

This is resolved in https://bitbucket.org/cioapps/pywapor/commits/21fe1427f317cfe9fd17b686daa8ad8c5939d4d4 and will be included in next release.

The number of scenes returned by pre_se_root was the "correct" number. Because other variables than "lst" and "bt" are temporally interpolated to the overpass times of those two variables, the period for which the other variables are downloaded is buffered with 3 days on both ends (i.e. to avoid extrapolation). The .download_data() method was incorrectly also buffering the “lst” and “bt” variables.