Opened 5 months ago

Closed 5 months ago

#2466 closed help (fixed)

NDdiag: "orography not of the right size"

Reported by: ambrogio Owned by: willie
Priority: high Component: NDdiag
Keywords: Cc:
Platform: Other UM Version:

Description

Dear CMS Helpdesk,

I am trying to run NDdiag starting from a pp file which does not contain orography. So, I included an orography file that I previously regridded in order to have the same grid as the input pp file (see command below)

NDdiag /group_workspaces/jasmin2/incompass/users/ambrogio/20160611_NDdiag_input_fields.pp nddiag.control.analysis test.pp /group_workspaces/jasmin2/incompass/users/ambrogio/regridded_orog.pp

The output given is this:

Input file: /group_workspaces/jasmin2/incompass/users/ambrogio/20160611_NDdiag_input_fields.pp

Diagnostics File: nddiag.control.analysis
Output File: test.pp
Orography File: /group_workspaces/jasmin2/incompass/users/ambrogio/regridded_orog.pp

Date: 2018/05/14 Time: 17:18

Input grid ……

N(theta), N(rho) : 80 80
(NX,NY) p-grid : 1250 750
(NUX,NUY) v-grid : 1250 750

Output grid (NX,NY) : 1250 750
DATE : 2016/ 6/11 0: 0
Orography file /group_workspaces/jasmin2/incompass/users/ambrogio/regridded_orog.pp

does not contain an orography of the right size.

Please specify an orography.

Why do you think is still giving an error about the size of the orography? See attached xconv screenshots of the input and the orography files.

Many thanks for your attention,

Best wishes
Ambrogio

Attachments (2)

xconv_screenshot.png (240.2 KB) - added by ambrogio 5 months ago.
xconv screenshot
xconv_screenshot_2.png (174.7 KB) - added by ambrogio 5 months ago.

Download all attachments as: .zip

Change History (9)

Changed 5 months ago by ambrogio

xconv screenshot

comment:1 Changed 5 months ago by willie

  • Platform set to Other

Hi Ambrogio,

The STASH code for the orography is 33, but that doesn't appear in your regridded orography file. You should re-create this with the correct STASH code.

Regards
Willie

comment:2 Changed 5 months ago by ambrogio

Dear Willie,

Many thanks for this reply. I have now generated a new orography file with the correct stash, which seems to be correctly read by NDdiag. Unfortunately I am still getting an error while running NDdiag, see below:

####

Input file: /home/users/ambrogio/NDdiag_files/20160611_input_NDdiag_fields.ppb
Diagnostics File: nddiag.control.analysis
Output File: test.pp
Orography File: /home/users/ambrogio/NDdiag_files/orography.ppb

Date: 2018/05/17 Time: 14:38

Input grid ……

N(theta), N(rho) : 80 80
(NX,NY) p-grid : 1250 750
(NUX,NUY) v-grid : 1250 750

Output grid (NX,NY) : 1250 750
DATE : 2016/ 6/11 0: 0
Missing v
Missing q
Missing T
Missing w
Missing rho pressure
Missing theta pressure

STOP We need the ALL following fields: orography,u,v,w,T,q,p_rho,p_theta

#####

From the error message it looks like NDdiag is, for some reason, not able to read beyond the first field (u) in the input file, which has been generated by taking relevant fields from different um files and saving them in a single pp file (whose endianness has then been swapped to make it NDdiag-compatible).
Do you have any suggestions on how to solve this problem?
The input and orography files are in Jasmin in /home/users/ambrogio/NDdiag_files/ and the NDdiag control file is in /home/users/ambrogio/programs/NDdiag_2.2.3/
An xconv screenshot of orography and input files is attached.

Many thanks again,
Ambrogio

Changed 5 months ago by ambrogio

comment:3 Changed 5 months ago by willie

Hi Ambrogio,

I've had a look at your input file and it is not in the right format for NDdiag. The UM produces files in time step by time step manner and NDdiag expects the same. All the required fields must be present at time step 1, then all the fields again at time step 2 and so on. There must be no return to time step 1. Your file however has all 13 time steps for U followed by all 13 times steps for V and so on. This makes NDdiag think many of the required fields are missing.

I don't think your input file came directly from the UM. It looks to me like some data base format such as netCDF, where the time dimension is just another variable, has been converted to create the input file.

So the solution is to re-create the input file in the required time step order.

Regards
Willie

comment:4 Changed 5 months ago by willie

  • Owner changed from um_support to willie
  • Status changed from new to accepted

comment:5 Changed 5 months ago by willie

Hi Ambrogio,

I've just realised I've already written pp_merge which merges a set on PP files in time order - you can down load it at http://cms.ncas.ac.uk/wiki/ToolsAndUtilities/PpFileTools. So you need to find the UM files with the required fields, convert them to PP format and then use pp_merge

Regards
Willie

comment:6 Changed 5 months ago by ambrogio

Dear Willie,

Many thanks for this. Everything works fine now.

Best wishes
Ambrogio

Last edited 5 months ago by ambrogio (previous) (diff)

comment:7 Changed 5 months ago by willie

  • Resolution set to fixed
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.