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

Scenario Selection UI #58

Closed
p-a-s-c-a-l opened this issue Mar 18, 2019 · 5 comments
Closed

Scenario Selection UI #58

p-a-s-c-a-l opened this issue Mar 18, 2019 · 5 comments
Assignees
Labels
BB: Scenario Management Scenario Management Building Block duplicate This issue or pull request already exists enhancement New feature or request on-hold Issue is on-hold and will be addressed later SHOWSTOPPER Feature or bug, that, if not addressed, renders the CSIS essentially useless STALLED important but currently not beeing worked on

Comments

@p-a-s-c-a-l
Copy link
Member

p-a-s-c-a-l commented Mar 18, 2019

We need some selection boxes (probably in study/context or in HC-LE) to let the user choose

  • The (3?) Hazard Events used for calculation of the impact scenario (they might be pre-chosen in the data package, so user wouln't be able to change the selection)
  • The time period used for calculation of the impact scenario (currently we have only historical events in the reference data package, 3 future times periods will b made available)
  • the RCP used for the calculation of the impact scenario (for future climate we'll get 3 RCPs for each time period)

@humerh @bernhardsk
This information is then saved at the level of the GL step object and then sent as request parameters to EMIKAT REST API for calculation of RA/IA. The request parameters may include for example the unique ids of the respective HC-LE input layers for the selected time period and RCP as well as IDs of the hazard events but only if there are more than 3(?) representative pre-selected events in the HC-LE layers.

@p-a-s-c-a-l p-a-s-c-a-l added this to the D1.4 CLARITY CSIS v2 milestone Mar 18, 2019
@p-a-s-c-a-l p-a-s-c-a-l self-assigned this Mar 18, 2019
@p-a-s-c-a-l p-a-s-c-a-l added BB: Scenario Management Scenario Management Building Block enhancement New feature or request labels Apr 5, 2019
@p-a-s-c-a-l
Copy link
Member Author

@humerh @bernhardsk any opinions on this topic?

@p-a-s-c-a-l p-a-s-c-a-l added the STALLED important but currently not beeing worked on label Apr 30, 2019
@p-a-s-c-a-l
Copy link
Member Author

@humerh @bernhardsk any opinions on this topic?

@humerh
Copy link

humerh commented Jun 17, 2019

I do not know, what the UI of CSIS for selecting the Scenario will look like.
I will try to describe the functionality of selecting the Hazard Events, which are "relevant" or typically for a specific project area:

  1. Create new study and study area

  2. The "middle point" of the study area should be used for selecting the relevant events for a study. EmiKat will implement the tables for "Heat Wave Hazard Events for Europe" (see discussions in
    Produce Heat Wave Hazard Events for Europe csis#57

  3. Emikat will implement a possibility (REST-Interface) to make a query for the current "Study" with the input paramters: rcp-scenario, time-periode and the results will be 3 Hazard-Events:

  • "Frequent" (Probability = 1.0; yearly event),
  • "Occasional" (Probability = 0.2; 1 in 5 year event),
  • "Rare" (Probability = 0.05; 1 in 20 year event)

This names of Events can be used for filtering results (IMPACT, ...) from EmiKat.

@p-a-s-c-a-l
Copy link
Member Author

p-a-s-c-a-l commented Jun 18, 2019

OK, we'll allow the user to select one RCP and one time period one event from the future for comparison against the baseline scenario. This will become our basis for adaptation scenarios.

The choice should be made in the HC or HC-LE tab, depending on what we show in the HC-LE table and sent to the EMIKAT RA/IA API.

@p-a-s-c-a-l
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BB: Scenario Management Scenario Management Building Block duplicate This issue or pull request already exists enhancement New feature or request on-hold Issue is on-hold and will be addressed later SHOWSTOPPER Feature or bug, that, if not addressed, renders the CSIS essentially useless STALLED important but currently not beeing worked on
Projects
None yet
Development

No branches or pull requests

4 participants