Open daniellevie opened 3 years ago
On the ReEDS branch can now plot multiple years. To address this issue we will need to replace the year part of the timestamp to be equal across all years. This can be a config setting and set in the get_data method.
This should only be allowed to happen if each individual scenario only contains a single unique year, else we will have duplicate timestamps
1) Date inputs (e.g. start date, end date) for multi-scenario, date-based plots (e.g.
Stacked_Gen_Facet_Grid_Range
) inMarmot_plot_select.csv
require a year, which prohibits making time-based plots from PLEXOS runs with different years. For example, I may want to plot dispatch for a select 1 across scenarios from 2024 and 2050. If you attempt to plot two scenarios with different ranges, Marmot will say that there is no generation in the range and not create a plot. Adding this feature would make several plotting methods more flexible for users. Possible solutions might be changing the date inputs to require only day/month and then having the plotting function intuit the year from the run (not sure if anyone is out there doing multi-year runs).2) Timeseries based plots don't plot well with scenarios that span multiple years; for example, below is the output for
Unserved_Energy_Timeseries
with two runs from 2024 and 2050. Solution may be something similar to above where only time/day/month are used to match. Not sure if including year in these should be an option to toggle in config.