Opened 11 years ago

Closed 10 years ago

#432 closed help (fixed)

Problems with STASH domain profiles

Reported by: allison Owned by: lois
Component: UM Model Keywords:
Cc: Platform:
UM Version: 4.5

Description

Hello,

I'm having a few problems with the STASH for HadCM3 on HECToR. I need to output some ocean diagnostics over a region which includes the Greenwich Meridian. I have specified in the domain profile:

Northern limit: 78,
Southern limit: 50,
Western limit: 290,
Eastern limit: 20

The output that I get from this has a strip of strange values (either very small or zero) along longitude=358.75 - this is the case for all three variables that use this domain. Do you know what might be the problem here?

An example of the output can be found in /work/n02/n02/agt/um/xezc/xezcbo.pd79c10 (the experiment, xezc, job b, was run by Andy Turner - user agt). "SOL: PEN.SOLAR*LF INTO OCEAN W/M2" in the above file is one of the diagnostics that is output over the domain specified above.

Another (similar) problem that I have is that I want to output cross-sections (longitude-depth) of total ocean v-velocity across the Atlantic at two different latitudes (26N and 50N). To do this I have made two separate diagnostics using total ocean v-velocity, with the two domain profiles given by:

For the 26N section:
Variables on full levels (1-20),
Northern limit: 27,
Southern limit: 26,
Western limit: 260,
Eastern limit: 350

For the 50N section:
Variables on full levels (1-20),
Northern limit: 51,
Southern limit: 49,
Western limit: 300,
Eastern limit: 0

The output can be found in the same file as above (/work/n02/n02/agt/um/xezc/xezcbo.pd79c10). There is just one velocity field, with the horizontal domain matching the 26N profile. It looks like the data from the 50N profile has been attached to this variable by concatenation along the depth direction - the depth dimension is repeated, so that depth goes 5, 15, .., 5192, 5, 15, .., 5192 m. Do you know what I'm doing wrong?

Any suggestions for either problem would be a great help!

Many thanks in advance,

Lesley Allison

Change History (4)

comment:1 Changed 11 years ago by lois

  • Owner changed from um_support to lois
  • Status changed from new to assigned

Hello Lesley,

We suspect that this is a known problem so we will investigate to see if we can find a fix.

More soon.

Lois

comment:2 Changed 11 years ago by simon

Hi,

I've looked at this and the meridian is a known problem at vn4.5 and there is no fix.
It is possible that there was a fix at 6.0 but it will be a considerable effort
to back port it to 4.5, and there is no guarantee that it will work at 4.5,
or even if it fixes this exact problem.
If it is essential you need the sub-region as opposed to the full field I could
investigate further.

Simon Wilson.

comment:3 Changed 11 years ago by allison

Hi Lois, Simon,

Thanks for this. It won't be necessary to port the fix back to vn4.5. Do you know if this problem is unique to ocean fields, or does it also happen when defining a sub-region in the atmosphere?

Lesley

comment:4 Changed 10 years ago by lois

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