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

Scenarios page #145

Closed
ElectricMountains opened this issue Mar 3, 2025 · 4 comments
Closed

Scenarios page #145

ElectricMountains opened this issue Mar 3, 2025 · 4 comments

Comments

@ElectricMountains
Copy link
Contributor

The scenario page should simply present a list of scenarios that have been calculated.

@drifter089
Copy link
Collaborator

Scenarions/ Learn More

walktrough or the energy modelling scenario that was presented

  • who are we
  • what is energy modelling
  • input data for our scenario
  • how pypsa-earth/pypsa-eur (PyPSA) does its magic
  • what the results look like (link to jis to get results and run to produce data for this page)

this should help user understand how energy modelling works and how we calculated the data for this app

@ekatef
Copy link

ekatef commented Mar 4, 2025

@ElectricMountains @drifter089 Super! Totally agree that we need a page which provides also the technical details for the simulations.

According to the previous discussions, I have a feeling that we must address the needs the audience groups with different levels of involvement into modeling stuff. So, absolutely agree that we need both basic definitions and links to more in-depth materials.

What I'm not sure about is how to balance interests of those two groups of users: what should go first, basics of details? I mean if we'll put definitions of the basics on top of the page won't it be a problem for people loking for more details? Do you have any ideas or sketches for the layout?

I also have a feeling that it could be best to keep the descriptions short on this particular page and provide links to the sources [while we'll need to make sure that the descriptions in the sources are detailed enough and up-to-the-date! 😄]. Is it consistent with your understanding?

@ElectricMountains
Copy link
Contributor Author

Just noting this issue is similar in nature to #86

@ElectricMountains
Copy link
Contributor Author

ElectricMountains commented Mar 17, 2025

#167 (Not planned for v1.0)

@ElectricMountains ElectricMountains closed this as not planned Won't fix, can't repro, duplicate, stale Mar 17, 2025
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