Giters

clarity-h2020 / csis

Management Project for coordinating the Climate Service co-creation process of the CLARTIY CSIS. High-level tasks (issues) are defined in this repository and then broken down into concrete implementable issues in different sub repositories.

Home Page:https://csis.myclimateservice.eu/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Calculation can't be triggered on test instance of CSIS

DenoBeno opened this issue · comments

commented

I suppose this is meant as a feature, but now I can't test the updated screening workflow because I can't trigger the calculation. How is this supposed to work?

commented

I have entered one EMIKAT ID from an existing study and now I can see how the new study looks like, I just can't trigger anything new.

commented

I suppose this is meant as a feature

Exactly, it's a safety precaution. It's not possible to trigger Emikat from the DEV instance, so that it doesn't interfere with the "real version" of the Study on PROD.
E.g. someone mistakenly edits the Study on DEV (changes Area or Adaptation option or whatever) and runs the calculation again. PROD would then only seemingly show Emikat results for the selected settings on PROD, when in reality it was using the settings configured on DEV.