include "technical data anchored in the model"

[akleinau]

Description of the issue

This comes from the model factsheets. Include "technical data anchored in the model", described as if and which technical data is embedded/ hard coded in the model and not part of the scenario

Ideas of solution

Workflow checklist

• [ ] I discussed the issue with someone else than me before working on a solution
• [ ] I already read the latest version of the workflow for this repository
• [ ] The goal of this ontology is clear to me

I am aware that

• [ ] every entry in the ontology should have a definition
• [ ] classes should arise from concepts rather than from words

[stap-m]

related to #482. Maybe it should be discussed/solved together.

[akleinau]

"technical endogeneous data is endogeneous data hard coded in the model and about technical parts of the model"?

[stap-m]

I'd rather classify it as exogenous data because its determined by the modeller and a kind of (steady) input to the model. It's not calculated by the model itself. @l-emele @Vera-IER @han-f What do you think?

[Vera-IER]

I'd rather classify it as exogenous data because its determined by the modeller and a kind of (steady) input to the model.

Yes I agree to that. The technical data is like a database which is fed into the model as input data. It's not hard coded. (The hard coded parts of my model are the equations like for example mass balances etc.)

[akleinau]

than someone should change that helptext in the factsheets so we don't disagree with them (model factsheets on the OEP website), @stap-m do you know who is responsible for that? We should reach common ground about this with the people involved in the factsheet first

[stap-m]

I opened an issue in the oeplatform for this.

[christian-rli]

I can change the help text in the issue created by @stap-m , but I don't think I'm the best person to discuss what precisely the help text should say. Once a text is agreed upon, I will implement it.

[han-f]

Have we possibly solved this by #520 ? In the sense that it is (hard coded) exogenous data?

[akleinau]

then just make "technical data" a synonym of "exogenous data"?

[stap-m]

We could distinguish between "model specific input data" and "scenario specific input data" - the first one doesn't usually change ("anchored in the model"), while the latter depends on the scenario?

[akleinau]

That sounds good! Scenario/Model specific input data: "Input data that is used by the scenario/model."?

[christian-rli]

So if I understand correctly, I should a) rename what is now called "Technical data anchored in the model" to "Model specific input data" with a mouseover that reads "Input data that is used by the model."? and b) Create another field with the same structure but for scenarios? I'm not sure I can just create new fields without breaking sth (@meisam-booshehri + @MGlauer ?) Would I add this new field in the scenario factsheets or in the model factsheet? Or am I misunderstanding?

[l-emele]

Do I understand correctly that this issue is now more a question of what should be presented on the OEO than a question what do we need in the OEO? If so, I suggest moving this issue to the OEP repo.

[sfluegel05]

The way I read it, there are two parts to this issue:

• changing the mouseover text on the website (-> https://github.com/OpenEnergyPlatform/oeplatform/issues/616)
• distinguishing between input data that is model specific or scenario specific

For the latter we have this suggestion:

Scenario/Model specific input data: "Input data that is used by the scenario/model."?

[l-emele]

Okay, in #482 we decided to go with the term exogenous data, so I propose the following two definitions:

• Exogenous model data is exogenous data that is used by a model.
• Exogenous scenario data is exogenous data that is used by a scenario.

[sfluegel05]

I agree with the labels. Maybe we can add model / scenario input data as alternative terms, similar to what we did with exogenous data.

I'm not quite sure if the definitions work. As I understand it, a scenario can be based on a model, thus the exogenous model data would automatically be used by a scenario and would become an instance of exogenous scenario data as well. I suggest Exogenous model / scenario data is exogenous data that is specific to a certain model / scenario.

[l-emele]

In the SIROP meeting in September 2021 we decided that we won't touch the model factsheets. Therefore I removed the milestone and added a new label "model factsheet".