Custom Query (3220 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (28 - 30 of 3220)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Ticket Resolution Summary Owner Reporter
#1324 answered Reconfiguration error: Required field is not in input dump (and yet it is!) annette luke
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

#1366 answered can we use version 9.1 on this system annette earjcti
Description

Hello, I would like to make some coding changes to the latest version of the UM and have been informed by staff at the met office that this is version 9.1. However, when I try to create a ticket (for enhancements) the latest version in the drop down box is 8.5, and here (on the help page) it is 8.6. However it does look like 9.1 is available on parts of the TRAC system (such as in the trunk code). I was therefore wondering if it is possible to do some enhancements with the 9.1 version of the model as things currently stand. Also do you know who I would contact about running the 9.1 version on MONSooN.

Thanks Julia

#1367 fixed Access to the UM repository annette dan
Description

Hi All,

Would it be possible to have access to the UM repository?

Thanks!

Cheers,

Dan

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Note: See TracQuery for help on using queries.