Hi Natalie
Sadly, we don’t have a simple fix for this and developing one is low on the list. Your idea of creating a new time coordinate in analysis code sounds like as good an idea as any.
Grenville
Hi Natalie
Sadly, we don’t have a simple fix for this and developing one is low on the list. Your idea of creating a new time coordinate in analysis code sounds like as good an idea as any.
Grenville
Thanks for looking into this for me. I had asked around in the Met Office too and they came to the same conclusion!
Natalie
Hi again,
I am now having the same problem on Monsoon3 - running mule-convpp on one of the fields files then getting the following error: skipping field validation due to irregular lbcode and just includes the first hour of the first timeseries variable. Do you know if there are any other versions of um-convpp on Monsoon3 that I can point to?
Thanks!
Natalie
PS I have tried contacting the Monsoon team but I haven’t heard back
Hi,
I know this is not a answer to your question, but it might be worth posting your issue on the Met Office GitHub discussions (in the UM or Mule channels). This will help in getting a more authoritative response regarding possible functionality in Mule, or support for timestep-timeseries output in the UM.
For information I do not believe any UM version earlier than vn13.5 is supported on Monsoon (UMDIR=/projects/metoff/umdir , for centrally installed scripts) and IIRC um-convpp was deprecated after 10.8.
Mohit
Thanks, Mohit. I have posted on the GitHub discussion board.
Let me know if you think of any way that we can do this as it is stopping progress on my project!
Best wishes,
Natalie
This problem now has a solution see: