Describe the bug
I've just tried adding a milestone year (2040) to the simple example model. This was mostly straightforward and I just had to make sure to add demand data for 2040 (and change the agent objective year to "all" as we were previously specifying it per year).
However, I noticed that if I don't increase the end_year of the processes to 2040 (or beyond) it panics in validate_sed_commodity when trying to get flow data for that year.
To Reproduce
Add 2040 as a milestone year to the simple model
Expected behavior
Ideally we shouldn't panic and the validation should either pass of fail depending on if the model is feasible in that year (it may not be if appropriate processes aren't available for that year), giving a helpful error message if necessary
Describe the bug
I've just tried adding a milestone year (2040) to the simple example model. This was mostly straightforward and I just had to make sure to add demand data for 2040 (and change the agent objective year to "all" as we were previously specifying it per year).
However, I noticed that if I don't increase the end_year of the processes to 2040 (or beyond) it panics in
validate_sed_commoditywhen trying to get flow data for that year.To Reproduce
Add 2040 as a milestone year to the simple model
Expected behavior
Ideally we shouldn't panic and the validation should either pass of fail depending on if the model is feasible in that year (it may not be if appropriate processes aren't available for that year), giving a helpful error message if necessary