irena-flextool / flextool

IRENA FlexTool is an energy and power systems model for understanding the role of variable power generation in future energy systems.
https://www.irena.org/energytransition/Energy-System-Models-and-Data/IRENA-FlexTool
Other
23 stars 5 forks source link

Allow user to decide on result tables #135

Closed nelliputkonen closed 10 months ago

nelliputkonen commented 10 months ago

(I'm not quite sure whether this is more of a Toolbox or FlexTool issue)

The issue is the balance to be handled between the output time of result processing and providing all the result tables the user wants. This has become prominent with the disappearance (optionality) of balance_t. There should be an easier way than current (https://irena-flextool.github.io/flextool/how_to/#how-to-enabledisable-outputs) to handle which tables should be shown and which are just a waste of processing time.

One option would be to add a filter selection in the workflow before Results where the user can simply select which tables to generate. There of course should be a group of recommended tables for the convenience of the user.

In my experience, there are two main use cases for result tables, one is checking everything works / debugging. This is most of model work time. The second is generating the final results / analysis. In the checking/debugging phase tables showing the unit and connector operation (flow_t) compared to inflow (balance_t) are most important. Also summary tables, capacities and penalty-related annual and time tables are used. The annualized flows, curtailments, costs etc. are of interest only in the final results/analysis phase. This could also be one idea on how to make the spit: User would decide between two options, to use the set of debugging tables or the full set of analysis tables.

jkiviluo commented 10 months ago

This is now fixed in the latest commit. https://github.com/irena-flextool/flextool/pull/138