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

reference table of SSP and associated scenarios #114

Open
0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q opened this issue Sep 24, 2021 · 2 comments
Open
Assignees
Labels
question Further information is requested

Comments

@0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q
Copy link
Member

I'm currently moving EDGE-Industry into mrremind, and there I need to match external "scenarios" (like low/medium/high estimates on steel stocks or assumptions on stock lifetimes) to the various SSP/SDP/not-Ariadne-but-something-else scenarios. Since this is tedious and error-prone work, I thought about having a table like

scenario steel stock estimate stock lifetime assumption
SSP1 low fast convergence
SSP2 medium normal convergence

and to reference that in my code. This way, there will be only one place for me to touch when scenarios get added/renamed.

Do EDGE-Buildings and EDGE-Transport have similar issues and should we coordinate on this?
@Loisel @MariannaR @RKrekeler

@robinhasse
Copy link
Contributor

For EDGE-B, we are working towards a very similar solution. I want want to get to one config file like in REMIND or your example above where all assumptions that distinguish scenarios from another are defined. But our plan is to make EDGE-B a separate library potentially accompanied by mredgebuildings for input data preparation. This seems like a diverging approach. Wouldn't it make sense to harmonise this (either separate libraries or integration into mrremind)? At first sight, a shared config table across sectors does not seem practical to me but I'm not sure if this is what you thought of.

0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q added a commit to 0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q/mrremind that referenced this issue Sep 28, 2021
@0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q
Copy link
Member Author

Wouldn't it make sense to harmonise this (either separate libraries or integration into mrremind)?

Depends on the scope I guess. EDGE-Transport is two packages by now. "EDGE-Industry" will just be three functions, and those will never be called outside of mrremind, so I see little point in putting them somewhere else. If EDGE-Buildings is big/complex enough it might be more reasonable to separate it.

At first sight, a shared config table across sectors does not seem practical to me but I'm not sure if this is what you thought of.

How so? You select all the switches (columns) you need, and get back the configuration for EDGE-Buildings (or Industry). The point is to have all this in one file and not spread out across the code. Or is your configuration more involved?

First draft under #116

0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q added a commit to 0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q/mrremind that referenced this issue Sep 30, 2021
0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q added a commit to 0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q/mrremind that referenced this issue Sep 30, 2021
0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q added a commit to 0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q/mrremind that referenced this issue Oct 6, 2021
0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q added a commit to 0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q/mrremind that referenced this issue Oct 8, 2021
0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q added a commit to 0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q/mrremind that referenced this issue Oct 11, 2021
0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q added a commit to 0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q/mrremind that referenced this issue Oct 18, 2021
0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q added a commit to 0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q/mrremind that referenced this issue Oct 22, 2021
0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q added a commit to 0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q/mrremind that referenced this issue Nov 16, 2021
0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q added a commit to 0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q/mrremind that referenced this issue Dec 8, 2021
0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q added a commit to 0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q/mrremind that referenced this issue Feb 11, 2022
0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q added a commit to 0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q/mrremind that referenced this issue Feb 15, 2022
0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q added a commit to 0UmfHxcvx5J7JoaOhFSs5mncnisTJJ6q/mrremind that referenced this issue Feb 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants