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

Add a tutorial elecricity and sector-coupled #1107

Open
davide-f opened this issue Sep 23, 2024 · 7 comments
Open

Add a tutorial elecricity and sector-coupled #1107

davide-f opened this issue Sep 23, 2024 · 7 comments

Comments

@davide-f
Copy link
Member

Describe the feature you'd like to see

Similar to PyPSA-Eur, we should have an elec-only and sector-coupled tutorial in the documentation to give a head start to users on how to use elec-only and sector-coupled modelling

@GbotemiB
Copy link
Contributor

Hi @davide-f, I am very interested in this.

@ekatef
Copy link
Member

ekatef commented Sep 24, 2024

Hey @davide-f, hey @GbotemiB! A great idea and happy to support!

@GbotemiB
Copy link
Contributor

Hi @davide-f @ekatef,

Regarding the tutorial, I think having a dedicated folder for the tutorial in the config folder would be best. We can have the config file for the electricity and the sector-coupled in the folder.

Another suggestion will be to move the default config to the config folder. We can have all the configs there.

@GbotemiB
Copy link
Contributor

In addition, the current tutorial config doesn't allow the option to have scenario naming, which is very important to keep the files detached from each other.

@ekatef
Copy link
Member

ekatef commented Sep 26, 2024

@GbotemiB agree that the configuration files definitely requires some re-structuring.

Not sure it's a good idea to mix this task with creating the cross-sectoral tutorial, but it may be worth to keep in mind that some further improvement will be needed. Agree that configs folder may be a good place to keep the configuration files. Could it be a good idea to create there two sub-folder to keep configs for the tutorial and full-scale runs, respectively?

@GbotemiB
Copy link
Contributor

@GbotemiB agree that the configuration files definitely requires some re-structuring.

Not sure it's a good idea to mix this task with creating the cross-sectoral tutorial, but it may be worth to keep in mind that some further improvement will be needed. Agree that configs folder may be a good place to keep the configuration files. Could it be a good idea to create there two sub-folder to keep configs for the tutorial and full-scale runs, respectively?

Maybe not separate folders, we could just have a tutorial sub-folder and leave the rest as it is.

I also agree to not mix this with the cross-sectoral tutorial, but the tutorial config for the cross-sectoral tutorial will be needed.

@ekatef
Copy link
Member

ekatef commented Sep 26, 2024

@GbotemiB agree that the configuration files definitely requires some re-structuring.
Not sure it's a good idea to mix this task with creating the cross-sectoral tutorial, but it may be worth to keep in mind that some further improvement will be needed. Agree that configs folder may be a good place to keep the configuration files. Could it be a good idea to create there two sub-folder to keep configs for the tutorial and full-scale runs, respectively?

Maybe not separate folders, we could just have a tutorial sub-folder and leave the rest as it is.

I also agree to not mix this with the cross-sectoral tutorial, but the tutorial config for the cross-sectoral tutorial will be needed.

Agree, creating a sub-folder for tutorial configs sounds like a good idea and is linked with the task to create a cross-sectoral tutorial. I'd go ahead with that, unless @davide-f @hazemakhalek have any concerns on such design

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants