ADF and LDF cannot create plots with specified date ranges if tseries are available for multiple time ranges #433
Description
ADF run type
Model vs. Model
What happened?
ADF and LDF both fail when multiple timeseries files are found. This is a bit of a hidden 'gotcha' that is coming up regularly when running these diagnostics via CUPiD on recent development runs.
In these cases, tseries have been created already (say, years 1-20), and then the baseline run continues, and we want to use a larger range of timesteps. Thus, we end up creating a second set of tseries (eg, years 1-40). Then, with the ADF timeseries tool, we end up with tseries for 1-20 AND tseries for 1-40. I think this is fine, but it causes issues down the line when ADF looks for timeseries and finds both.
Is it possible to specify the years when looking for tseries files to avoid running into this issue?
ADF Hash you are using
What machine were you running the ADF on?
CISL machine
What python environment were you using?
Other (please explain below)
Extra info
conda environment: cupid-analysis