Validating river diagnostics on non-global domains #585
Replies: 3 comments 1 reply
|
Not an expert on the rivers model and definitely not familiar with what's been done to make it work for regional models but I think you'd need to keep the validation for the global model part (the else here) as that defines what's valid for a global domain and that shouldn't have changed. Whoever did the regional rivers work would need to inform what would constitute a valid regional river routing grid (it may be that the if block for horiz_grid_type != 0 just reports that its regional and continues on its merry way). |
|
Hello, |
|
Thanks both, sounds like this is reasonably simple then. |
Uh oh!
There was an error while loading. Please reload this page.
I am currently adding rivers to the Regional Climate Model (see u-dx147) and need to initialise some dump fields on grid type 23 (STASH codes 151, 152, 153). I am using a regional domain, this causes mule/validator.py to fail:
Regional rivers were added at UM13.8, so river routing diagnostics should now be valid for non-global domains (see UM ticket 7880 and JULES ticket 1555). This leaves the following elif block from line 751 of mule/validators.py defunct.
I think the solution may be to simply delete this section of code, but I'm not sure if anything needs to change elsewhere. Would anyone be able to advise?
All reactions