Do not add bounds to plev (plev19) in era interim cmorizer#2328
Conversation
|
cheers @zklaus - can we wait to merge until @remi-kazeroni has had a look too, please? I reckon a data regeneration would be in store too 🍺 |
Good point @valeriupredoi 👍 I'll have a look into this tomorrow at the latest |
|
take your time, man! The isenes3 plenary is not helping 😁 |
|
Well, I completely understand the constraints and limitations, but this has implications for the core, which is supposed to be frozen today, so if possible, looking at it sooner rather than later would be great. |
|
@zklaus - indeed, but given we don't need to change anything in Core perse, we should be fine. Good luck chairing the upcoming session at the plenary you two, I be there 🍺 |
remi-kazeroni
left a comment
There was a problem hiding this comment.
I tested it and this generates data without plev bounds as expected. But we have more than 300 GB of ERA-Interim data on Mistral, a large fraction of which has plev coordinates. So I'd rather be sure with need to regenerate the data before doing so.
|
If we are unsure about this, or just need something that is effective more quickly, we might consider adding a fix for ERA-Interim that simply removes the bounds in the preprocessor. |
|
@remi-kazeroni whoa! Yeah, prob best to be 100% sure about that - we'd kill Thor knows how many polar bears with that massive data movement 😁 I unfortunately don't now about the validity of not guessing bounds on ERA from a scientific point, up to you guys to know this 👍 |
remi-kazeroni
left a comment
There was a problem hiding this comment.
Fine for me, thanks. If that is fine, I will merge this myself once the new data are in place at Mistral and Jasmin
Description
Before you get started
Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.
New or updated data reformatting script
To help with the number of pull requests: