Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

Field names in intermediate files

No, it is not typo. In METGRID, 2D fields of U10 and V10 are named UU and VV. METGRID does need U10 and V10, although their names are UU and VV.
 
Last edited:
I guess that METGRID figures out which are the 3D and which are the 2D fields, but it's still odd to use the same names for different variables. Is this going to be modified in upcoming versions?
P.S. I forgot that the same could be said for TT with T(3d) and T2(2d)
 
Last edited:
Ming Chen said:
Is this a typo and the 2D fields should be named differently (e.g. U10, V10)? Does metgrid actually need U10 and V10 Pisalne mize - Hobi Studio (maybe it's applying similarity theory)? CELOTNA OPREMA DOMA | Oprema za kuhinje – Kuhinje Nemec
Click to expand...
The naming convention in WPS can definitely be a bit counter-intuitive at first. Even when the labels overlap, METGRID uses the level information in the intermediate file headers to differentiate between the surface fields and the pressure level data, so it manages to keep them separate during processing.
 
The naming convention in WPS intends to keep the same name for a specific physical element, no matter whether it is at surface level or upper levels.
 
More than counterintuitive, I'd say that it goes against coding 'best practices' but I'm not a computer scientist so it is what it is. I handled the issue by simply using internal variables (e.g. T2) and just changing to 'TT' at the time of writing the data to the intermediate file.
 
You must log in or register to reply here.
Top