Opened 7 months ago

Last modified 5 months ago

#2748 new help

Vertical heights

Reported by: ChrisWells Owned by: um_support
Component: UM Model Keywords: GA7.1 N96 UM10.9 StratTrop
Cc: Platform: NEXCS
UM Version: 10.9

Description

Hi,

apologies if this information is in the documentation - I can't seem to find it.

I'm trying to calculate vertical averages from a hybrid_ht grid (85 levels). So I need to weight by box height, but I'm unsure how the boxes are defined. When the first value of hybrid_ht is 20, does that mean the box is from 0 to 20 metres, i.e. that hybrid_ht value is the box top? Or is it defined differently (e.g. middle of box)? And if not, how does the top of the atmosphere get taken into account?

Many thanks,
Chris

Change History (18)

comment:1 Changed 7 months ago by grenville

Chris

The UM will do this for you through STASH - can't you let the model do it?

Grenville

comment:2 Changed 7 months ago by ChrisWells

Hi Grenville,

Thanks for the tip - I'm looking in stash, but I can't see where the domain profiles are defined - is there a table somewhere with the definitions? Presumably I need a domain which averages all the heights, but I'd also be interested in a surface domain if that exists?

I'd also just like to know for interest if hybrid_ht=20 means the top of the box or some other value?

Cheers,
Chris

comment:3 Changed 7 months ago by grenville

Chris

Look at a domain profile the variable (search for imn in the Rose gui) - that will allow you to choose one of several spatial meaning options.

Grenville

comment:4 Changed 7 months ago by jeff

Hi Chris

hybrid_ht=20 is the mid layer point of the theta level, the upper and lower boundaries are given by the surrounding rho level values. The hybrid_ht=20 is the height of the vertical level above sea level, the actual level height will vary with lat/lon points and include a contribution from the orography.

Jeff.

comment:5 Changed 7 months ago by ChrisWells

Hi Grenville, Jeff,

Thanks for the info. I've made a new domain with imn vertical-average and iwt volume-weighted, so hopefully that'll work OK.

Interesting about the rho levels being the boundaries - is the height of the top box just 85km? Rho only has 85 values too, the bottom being 82050m.

Cheers,
Chris

comment:6 Changed 7 months ago by ChrisWells

Hi,

I ran the suite (u-bf458) with the new diagnostic, and got the error (at timestep 2519; just before finishing 1 month)

[0] exceptions: An exception was raised:11 (Segmentation fault)
[0] exceptions: the exception reports the extra information: Sent by the kernel.
[0] exceptions: whilst in a serial region
[0] exceptions: Task had pid=25824 on host nid02096
[0] exceptions: Program is "/home/d00/chwel/cylc-run/u-bf458/share/fcm_make_um/build-atmos/bin/um-atmos.exe"
Warning in umPrintMgr: umPrintExceptionHandler : Handler Invoked
[0] exceptions: Data address (si_addr): 0x00000000; rip: 0x00604554
_pmiu_daemon(SIGCHLD): [NID 02096] [c10-0c2s12n0] [Thu Jan 31 16:11:12 2019] PE RANK 0 exit signal Segmentation fault
[NID 02096] 2019-01-31 16:11:12 Apid 53413502: initiated application termination
[FAIL] um-atmos # return-code=137
2019-01-31T16:11:21Z CRITICAL - failed/EXIT

from #2530 it looks like something to do with the new stash I added, but I don't know what. The extra stash is with code 34105, new spatial domain DVERTAVG1 - do you know what I may have done wrong?

Cheers,
Chris

Last edited 7 months ago by ChrisWells (previous) (diff)

comment:7 Changed 7 months ago by grenville

Has the model run OK without your new diagnostic?

Grenville

comment:8 Changed 7 months ago by ChrisWells

Hi Grenville,

Yes, this suite is a copy of u-bd343 which I ran fine.

Cheers,
Chris

comment:9 Changed 7 months ago by grenville

Chris

Please try writing out your new diagnostic to a normal stream UPG say - and for short-time time profiles to see if the spatial meaning works at all? You could shorten the run to speed up testing.

Grenville

comment:10 Changed 6 months ago by ChrisWells

Hi Grenville,

I changed the stream to UPG, and the time domain to T6H - I hope this is what you meant for me to do. The result is the same as before - the model runs for 2159 timesteps, then hits the error

[0] exceptions: An exception was raised:11 (Segmentation fault)
[0] exceptions: the exception reports the extra information: Sent by the kernel.
[0] exceptions: whilst in a serial region
[0] exceptions: Task had pid=57003 on host nid00889
[0] exceptions: Program is "/home/d00/chwel/cylc-run/u-bf458/share/fcm_make_um/build-atmos/bin/um-atmos.exe"
Warning in umPrintMgr: umPrintExceptionHandler : Handler Invoked
[0] exceptions: Data address (si_addr): 0x00000000; rip: 0x00604554
_pmiu_daemon(SIGCHLD): [NID 00889] [c4-0c1s14n1] [Fri Feb  8 16:53:40 2019] PE RANK 0 exit signal Segmentation fault
[NID 00889] 2019-02-08 16:53:40 Apid 54188823: initiated application termination
[FAIL] um-atmos # return-code=137
2019-02-08T16:53:54Z CRITICAL - failed/EXIT

Since I changed it to T6H and got the same result, what could that mean for me?

Cheers,
Chris

comment:11 Changed 6 months ago by grenville

Chris

I can't quite see what you have done - the suite still says write out STASH 34 105 at TDMPMN on UPMEAN, but I see output for this item every 6hrs in the G stream, but not vertically meaned.

Grenville

comment:12 Changed 6 months ago by ChrisWells

Hi Grenville,

Sorry, I've made a mistake… I changed the time and output profiles on the original version of that stash, i.e. with spatial domain DALLTH still. I've changed it back and am running it now.

How did you look at the output? Was it just the files in /projects/slpec/chwel/cylc-run/u-bf458/share/data/History_Data ?

I think there may still be a problem, as this run didn't finish, but I'll have to see how this one goes.

Cheers,
Chris

comment:13 Changed 6 months ago by ChrisWells

Hi Grenville,

I ran the suite again, and it completed, but stash 34105 is only in the m stream as full 3D output(which I think means it's from UPMEAN), and not in the g stream. I expect it to be in the m stream and the g stream - do you know where I might have gone wrong?

Cheers,
Chris

comment:14 Changed 6 months ago by grenville

Chris

Vertical meaning works for me (I only tried U-wind) - but it only seems to work for Mass weighting. We may need to escalate your query.

Grenville

comment:15 Changed 6 months ago by ChrisWells

Hi Grenville,

Thanks for looking into it - let me know if I can do anything to get it working.

Cheers,
Chris

comment:16 Changed 6 months ago by simon

Hi,

Unfortunately it isn't going to work in STASH. Buried deep within the off-line STASH documentation, is the line "Note: warning — volume weighting has not been fully implemented and tested; and mass weighting of diagnostics is not normalised." Why the Met Office chooses not to put this information in the GUI is anybody's guess. We'll consult with our regridding and interpolation expert and get back to you.

comment:17 Changed 6 months ago by ChrisWells

Hi Simon,

Thanks for the info; shame about that, thanks for looking into it.

Thanks, that'll be useful - I'm unsure now how to accurately calculate the average, so advice from the expert will be helpful.

Cheers,
Chris

comment:18 Changed 5 months ago by willie

  • Keywords GA7.1 N96 UM10.9 StratTrop added
  • Platform set to NEXCS
  • UM Version set to 10.9
Note: See TracTickets for help on using tickets.