Closed philipjyoon closed 4 months ago
This was implemented into CSLC download code but wasn't absolutely necessary because historical batch processing does the counter side of this: reduce m before submitting queries jobs. Either way, this ticket is completed.
Checked for duplicates
Yes - I've already checked
Describe the bug
The value of m starts from 1 at the very beginning of the sensing time series for any particular frame and then ramps up to the actual m value. In the early stages of historical processing, there will not be enough sensing times in the database (and dataset) to satisfy the entire m compressed CSLC files. m needs to be reduced in these cases accordingly.
What did you expect?
n/t
Reproducible steps
Environment