Opened 12 years ago

Closed 12 years ago

#173 closed help (fixed)

Problem with job xczxi

Reported by: laurahb Owned by: willie
Component: UM Model Keywords:
Cc: Platform:
UM Version:



I'm having problems with the UM job xczxi - it runs ok (ie no errors) but the output is mostly NaNQ 's . I've worked out that the problem is in the output file xczxia_da006, which is created during the first part of the run (it's set up as an automatic resubmission every 6 hours) - some of the fields in that file, (eg. spec humidity after timestep, theta after timestep) are NaNQ's everywhere except at the boundaries. The start file xczxi.astart seems fine.
What is particularly confusing is that this job is essentially identical to the job xczxf which i ran a couple of months ago and was fine, and nothing has changed within the job or with the start dump or lat bcs file.

Any ideas why this may have happened?



(hpcx and puma username: laurahb)

Change History (4)

comment:1 Changed 12 years ago by willie

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


OK I'll have a look at this.


comment:2 Changed 12 years ago by willie

Laura, I have looked at both jobs xczxi and xczxf: they show the same fault. I have eliminated some of the check setup errors (you need to change 38 to 76 in the three tables in atmos_Science_Section_DiffFiltCoeff - you get to this by pressing HORIZ) but the others are still be ing worked on. Even with these changes the job still has the NaNQs.

I note that you have inyour directory xczxf and xczxf_orig and this makes me think that you changed something in the original job that has evoked the problem. Could you have a look at this please?


comment:3 Changed 12 years ago by willie

I now have a solution. The vertical specification is for 26 levels (atmos_Domain_vert), but the table of time weights for boundary levels only has 13 entries, each specifying two levels. The UMUI is not clever enough to understand this. The thing to do is to change the entry on this page to 26 and then re-enter the table values with start level = end level, so there will be 26 entries each specifying one level. When you do this, run check setup in the UMUI and no errors will be reported and the jobs will run properly.

The table is in Atmos > Scientific > Section by Section > Boundary layer in the UMUI.

Let me know how you get on with this.

Regards, Willie

comment:4 Changed 12 years ago by willie

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