Simplify ESDL connection to Tulipa flows, and back

suvayu commented 3 months ago

In ESDL 2 assets are connected via a transport asset, whereas Tulipa prefers direct connection between assets due to efficiency reasons. We need to find:

[x] #4
[x] #6
[x] ~vice versa, i.e. going from a Tulipa flow to a connection in ESDL using transport asset.~ (deal with this later)

clizbe commented 2 months ago

I think the first step is determining what data Tulipa needs for the connection and where that data can be entered in the MapEditor.

suvayu commented 2 months ago

For now I implemented what @datejada suggested here: https://github.com/TulipaEnergy/esdl4tulipa/issues/1#issuecomment-2205181967

Code wise, it's this: https://github.com/TulipaEnergy/esdl4tulipa/blob/8bb50212b6a9d76e51113ce2fdcc1421ae9d20a4/src/esdl4tulipa/mapping.py#L67-L71 https://github.com/TulipaEnergy/esdl4tulipa/blob/8bb50212b6a9d76e51113ce2fdcc1421ae9d20a4/src/esdl4tulipa/mapping.py#L135-L140

The attributes you see above are the Tulipa names, and the ESDL names are recorded in the esdl_key method (click the links aobve). Essentially I skipped anything for which we haven't associated an ESDL attribute in the table in #1

TulipaEnergy / esdl4tulipa

Simplify ESDL connection to Tulipa flows, and back #2