During #930 , issues became apparent when data at a cycling frequency of P3M using monthly slicing in the request file caused the final time point to be removed from the cube and hence trigger a time contiguity QC error.
This has since been resolved by changes to new_varaible.py in #930. A functional test should be created to ensure that this bug does not get re introduced by future changes.
During #930 , issues became apparent when data at a cycling frequency of P3M using monthly slicing in the request file caused the final time point to be removed from the cube and hence trigger a time contiguity QC error.
This has since been resolved by changes to
new_varaible.pyin #930. A functional test should be created to ensure that this bug does not get re introduced by future changes.