search

TulipaEnergy / TulipaEnergyModel.jl

An energy system optimization model that is flexible, computationally efficient, and academically robust.
Apache License 2.0
18 stars 18 forks source link

Split `profile_name` in the `profiles_table` #683

Open datejada opened 1 week ago

datejada commented 1 week ago

What and Why

The idea is to have two columns with the name and type together instead of one.

Possible Drawbacks

No response

Related Issues

No response

suvayu commented 1 week ago

~split~ rename according to source or context, since the same profile maybe used in different places

greg-neustroev commented 1 week ago

We had a discussion and the conclusion was that the profiles can in principle be reused, therefore multiple profile_name and profile_type combinations can use the same profile. Thus, a profile needs an identifier of some kind, either an abstract ID, or better, a descriptive name. Please note, that this name SHOULD NOT tell how the profile is used, but rather where it came from. In the Norse pipeline example, e.g., it should not be availability-Asgard_Solar, but solar_two_seasons, and then we link the availability of solar in Asgard to this profile. solar_two_seasons indicates the data origin: it is a synthetic dataset generated so that there are two seasons.