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
Instead of having one file, asset.csv, we should have one file per asset type:
consumer_assets.csv
producer_assets.csv
conversion_assets.csv
storage_assets.csv
hub_assets.csv
The main driver for this change is to have the parameters you need for each asset in each file so the user understands which data needs to be updated depending on the assets.
Some things to consider I can think of:
The asset structure in TulipaEnergyModel remains the same. Reading and storing the input data is what changes, and then all goes to the current asset structure.
Add defaults to the parameters so the missing data gets a value.
Check with TulipaIO.jl changes and modifications that we might need there too.
Possible Drawbacks
More files, but easier for users using the file to run the model
Related Issues
No response
The text was updated successfully, but these errors were encountered:
What and Why
Instead of having one file,
asset.csv
, we should have one file per asset type:The main driver for this change is to have the parameters you need for each asset in each file so the user understands which data needs to be updated depending on the assets.
Some things to consider I can think of:
Possible Drawbacks
More files, but easier for users using the file to run the model
Related Issues
No response
The text was updated successfully, but these errors were encountered: