Opened 3 years ago

Closed 3 years ago

#1324 closed help (answered)

Reconfiguration error: Required field is not in input dump (and yet it is!)

Reported by: luke Owned by: annette
Priority: normal Component: UM Model
Keywords: reconfiguration Cc:
Platform: MONSooN UM Version: 8.4

Description

When turning reconfiguration on for job xkawr I get the following error:

????????????????????????????????????????????????????????????????????????????????
???!!!???!!!???!!!???!!!???!!!???!!! ERROR ???!!!???!!!???!!!???!!!???!!!???!!!?
? Error in routine: Rcf_Set_Data_Source
? Error Code:    30
? Error Message: Section  34 Item   163 : Required field is not in input dump!
? Error generated from processor:     0
? This run generated *** warnings
????????????????????????????????????????????????????????????????????????????????

However, s34i163 is in the dump (/projects/ukca/nlabra/ANCILS_N96L85/xjcina.da20151201_00). Viewing the file in Xconv/convsh shows that it is variable 281:

 281  : 192   145   85    1     Stash code = 34163

(which has the correct timestamp of 2015/12/01:00.00, the entry at variable 535 has a timestamp of 2015/11/26:00.00 so I guess is associated with the UPMEAN stream)

I can extract variable 281 and make an ancillary file from it and use this instead - see job xkawq which is able to reconfigure properly.

I'm not sure why the model cannot see this field in the file - it can see all the others. Comparing the entry for this field from STASHmaster_A and the user STASHmaster file (~mdalvi/umui_jobs/prestash/vn8.2/UKCA_Prog_151_163.prestash) gives

1|    1 |   34 |  163 |CLOUD DROPLET NO CONC^(-1/3) (m)    |  | 1|    1 |   34 |  163 |<CLOUD DROPLET NO CONC^(-1/3)> (m)  |
2|    0 |    0 |    1 |    1 |    2 |   10 |   11 |    0 |    | 2|    2 |    0 |    1 |    1 |    2 |   10 |   11 |    0 |   
3| 000000000000000000000000000000 | 00000000000000000001 |      3| 000000000000000000000000000000 | 00000000000000000001 |   
4|    1 |    0 | -99  -99  -99  -99  -99  -99  -99  -99  -99    4|    1 |    0 | -99  -99  -99  -99  -99  -99  -99  -99  -99 
5|    0 | 1862 |    0 |   65 |    0 |    0 |    0 |    0 |      5|    0 | 1862 |    0 |   65 |    0 |    0 |    0 |    0 |   

i.e. other than the name, only the SPACE code is changed from 0 (diagnostic field for which space is required only when the diagnostic is requested) to 2 (Section 0, 33 or 34 items only: primary field available to STASH). The same change has been made for e.g. s34i162, and there isn't a problem with this field.

Any and all advice as to how to get Reconfiguration to recognise that this variable exists would be greatly appreciated.

Many thanks,
Luke

Change History (3)

comment:1 Changed 3 years ago by grenville

Luke

Did you try changing the space code to 0?

Grenville

comment:2 Changed 3 years ago by annette

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

Luke,

Did you make any progress on this issue?

As well as creating an ancillary you can also just force the field to be read in from the dump as in #1169 (as I'm sure you know).

#1169 looks to me like the same sort of problem where the field is in the dump but the recon can't find it. It may be that this is a bug/feature of the UM. The next step I think might be to look at the recon code but as there is a work around it might not be high priority.

Annette

comment:3 Changed 3 years ago by annette

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