-
Notifications
You must be signed in to change notification settings - Fork 63
Tropical storm case studies #2260
Copy link
Copy link
Open
Labels
evalanything related to the model evaluation pipelineanything related to the model evaluation pipelineinitiativeLarge piece of work covering multiple sprintLarge piece of work covering multiple sprint
Metadata
Metadata
Assignees
Labels
evalanything related to the model evaluation pipelineanything related to the model evaluation pipelineinitiativeLarge piece of work covering multiple sprintLarge piece of work covering multiple sprint
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
No status
Describe the task. Describe the task. It can be a feature, a set of experiments, documentation, etc.
We have seen that the model can produce realistic-looking tropical cyclones, for example Typhoon Koinu here:
We would probably like to look at the model performance for one or a few selected storms in a way that is repeatable and ideally quantitative. This could take the form of an extra package within the fast evaluation, that might read some exported netcdf files and then look at a pre-selected region and time-span known to contain an interesting storm.
How exactly this should be realized technically and how such case-studies should be selected is up for debate.
example output
As a proof-of-concept, I have implemented a simple cyclone detector, that would allow us to look at track positions and quantities like wind-speed and core pressure along the track:
In this example, the model is almost perfect for Koinu, and even follows the intensification (but not the track) of storm Bolaven which was initiated around step 30. Note that other examples during the same period were not as good though.
Hedgedoc URL, if you are keeping notes, plots, logs in hedgedoc.
No response
URL to the design document
No response
Area