Replies: 4 comments 11 replies
-
In particular the TC class is still very useful as demonstrator (in e.g. the CCUR lecture) as it visualizes well how a probabilistic event set is generated, which helps understanding the concept quickly. I think some learning would be lost if we instead just download a hazard set from the API, so for some "Climada introduction"-classes, one would probably also need to install petals in the future. |
Beta Was this translation helpful? Give feedback.
-
I support this decision. |
Beta Was this translation helpful? Give feedback.
-
I think this is a good idea in general. |
Beta Was this translation helpful? Give feedback.
-
If you'll indulge me for a bit, let me take this opportunity to bring up a fundamental question once more: I'm still a little bit unsure about the separation of petals and core in the first place. I appreciate that it makes sense to have the core maintained professionally and to a higher standard, but the divergence between the two repos can ache a little. I know this might be unorthodox, but what if the petals module was moved back to this repo? That would ease the decision to move less-used components into the petals, while making it easier to have core and petals in tune. For beginners, the I agree that my train of thought isn't fully formed yet, but if this sets someone thinking, that's already something :) |
Beta Was this translation helpful? Give feedback.
-
Today, the CLIMADA devs decided to move more
Hazard
-derived classes from the core repository into CLIMADA Petals. The goal is to reduce development overhead in the core. Also, differentHazard
types originally served as "demonstrators" in the core. But this purpose has been diminished by more and more hazard data being available from the data API. Therefore, this decision is in line with the original intend of Petals, namely to house hazard (and other) specialization modules.In a first step, we want to move all TC-related modules:
In a second step, we also want to move the winter storm module:
Users of these modules will have to do the following when they upgrade to a new Climada version:
climada.hazard.MODULE
toclimada_petals.hazard.MODULE
At this point, it is still unclear when the move will happen. We want to keep the user experience as nice as possible, with appropriate warnings and/or errors being raised that tell users exactly what to do.
Please note and comment/criticize/suggest..! @ThomasRoosli @mmyrte @tovogt @bguillod @ChrisFairless
Beta Was this translation helpful? Give feedback.
All reactions