You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PeriodPartition, introduced in TimeStruct 0.9.12, creates a bug when used together with EMGUI. Running the GUI on the introduced tests of this PR illustrates this with the error
Type TimeStruct.OperationalPeriod{TimeStruct.SimplePeriod{Float64}} can not be used as index for a PartitionProfile{Float64}
Ideally, a solution to this should be first implemented in EMGUI before this PR can be merged.
The problem is within the processing of EnergyModelsGUI which does not fully support the new time profile types and subdivisions. The reason for that is that partition_duration can be different for different type of nodes. As a consequence, it cannot be directly incorporated within the TimePeriod as it is the case for all other potential time structures. Subsequently, a PartitionProfile cannot be indexed by a TimePeriod as the information of the partition is not accessible as this level, despite being theoretically able to use them as indices.
That being said, it requires a rework of the plotting functionality to work properly for all nodes that have variables or parameters that require PeriodPartition. As I do not consider it in this case prudent to wait for the implementation in EMGUI (which may take a bit of work), I say that we instead still merge PR 12 in EnergyModelsFlex and provide a warning in the README.md and the documentation instead.
This problem also leads to not being able to load saved data that is indexed over a partition period. To this end, you must exclude the result files for these variables from the folder you load..
Activity
JulStraus commentedon Jun 27, 2026
The problem is within the processing of
EnergyModelsGUIwhich does not fully support the new time profile types and subdivisions. The reason for that is thatpartition_durationcan be different for different type of nodes. As a consequence, it cannot be directly incorporated within theTimePeriodas it is the case for all other potential time structures. Subsequently, aPartitionProfilecannot be indexed by aTimePeriodas the information of the partition is not accessible as this level, despite being theoretically able to use them as indices.That being said, it requires a rework of the plotting functionality to work properly for all nodes that have variables or parameters that require
PeriodPartition. As I do not consider it in this case prudent to wait for the implementation inEMGUI(which may take a bit of work), I say that we instead still merge PR 12 inEnergyModelsFlexand provide a warning in theREADME.mdand the documentation instead.JulStraus commentedon Sep 17, 2026
This problem also leads to not being able to load saved data that is indexed over a partition period. To this end, you must exclude the result files for these variables from the folder you load..