Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split the asset.csv file per asset type #38

Open
datejada opened this issue Apr 29, 2024 · 2 comments
Open

Split the asset.csv file per asset type #38

datejada opened this issue Apr 29, 2024 · 2 comments
Labels
good first issue Good for newcomers

Comments

@datejada
Copy link
Member

What and Why

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

@clizbe clizbe transferred this issue from TulipaEnergy/TulipaEnergyModel.jl May 7, 2024
@clizbe
Copy link
Member

clizbe commented May 7, 2024

Moved the repo because this is a good demo case for using TIO (and should hopefully make it easier).

@clizbe
Copy link
Member

clizbe commented Jul 29, 2024

Think about what this means schema-wise and user-wise (maybe no longer applicable to user) after the refactor.

@clizbe clizbe added the good first issue Good for newcomers label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants