Stash difficulties SET_LEVELS_LIST

[jmw240]

Hi,

I've been having difficulty adding some seemingly standard stash requests to a suite (u-bw943). I originally added quite a large amount of stash and the model ran fine but adding a further 6 deposition diagnostics crashes the model in atmos main. I've experimented by adding some of these and not others and the error messages have differed which has made diagnosing the problem tricky. The last attempt I tried had just one of these stash added (50032 - HONO2 dry deposition) and failed with the error message below. I can see reference to the section and item but have been unable to work how to proceed.

? Error code: 1
? Error from routine: SET_LEVELS_LIST
? Error message: Bad control data: stlist(10/11)/section/item 1001295032
? Error from processor: 173
? Error number: 199

I am aware there are errors in stash requests but these are for unselected species and I believe were present before I added any of the new stash (they arise due to switching to a new chemical mechanism).

Any help would be greatly appreciated.

Many thanks,

James

[luke]

Hi James,

I believe that this problem is fixed now - correct?

The issue is that a diagnostic (defined in STASHmaster_A) uses a 2D level structure but was requested to be output on theta levels (i.e. 3D) in the Rose STASH panel.

e.g. from the header information in the STASHmaster

#|Model |Sectn | Item |Name                                |
#|Space |Point | Time | Grid |LevelT|LevelF|LevelL|PseudT|PseudF|PseudL|LevCom|
#| Option Codes                   | Version Mask         | Halo |
#|DataT |DumpP | PC1  PC2  PC3  PC4  PC5  PC6  PC7  PC8  PC9  PCA |
#|Rotate| PPF  | USER | LBVC | BLEV | TLEV |RBLEVV| CFLL | CFFF |

and then compare to the following 2 (example) diagnostics:

1|    1 |   50 |   81 |LIGHTNING NOx EMISSIONS 3D          |
2|    0 |    0 |    1 |    1 |    2 |   10 |   11 |    0 |    0 |    0 |    0 |
3| 000000000000000000000000000000 | 00000000000000000001 |    3 |
4|    1 |    0 | -99  -99  -99  -99  -99  -99  -99  -99  -99  -99 |
5|    0 | 1871 |    0 |   65 |    0 |    0 |    0 |    0 |    0 |
#
1|    1 |   50 |   82 |LIGHTNING DIAGNOSTIC: TOT FLASHES 2D|
2|    0 |    0 |    1 |    1 |    5 |   -1 |   -1 |    0 |    0 |    0 |    0 |
3| 000000000000000000000000000000 | 00000000000000000001 |    3 |
4|    1 |    0 | -99  -99  -99  -99  -99  -99  -99  -99  -99  -99 |
5|    0 |    0 |    0 |  129 |    0 |    0 |    0 |    0 |    0 |

the values for LevelT, LevelF, LevelL (line 2), and LBVC (line 5) are different.

We can see from UMDP C04 (​https://code.metoffice.gov.uk/doc/um/latest/papers/umdp_C04.pdf)

that these values correspond to:

• LevelT: The level type code. Specifies the type of levels on which a field is defined.
  • 2 Data on atmosphere theta levels.
  • 5 Single level data.
• LevelF and LevelL: The first and last level codes. Specify the first and last levels on which a field is defined.
  • 10 First tracer level.
  • 11 Last tracer level (= Top atmospheric level).
• LBVC: PP vertical coordinate type. Defined and documented in UMDP F03, this is the field code defining the vertical coordinate of an output field to (older) PP graphics applications, i.e. such that there is a common value for each horizontal field. LBVC is used to specify the PP header item (26=lbvc) on output, but is also required within STASH to generate other PP header output items, such as (52=blev) in the correct format. Example lbvc codes:
  • 65 hybrid height (as atmosphere model levels)
  • 129 surface level

The fix here is either to correct the STASHmaster_A entry (if the diagnostics should be 3D) or change the levels requested in Rose (if the diagnostic should be 2D). It is a confusing error message - I believe that from the 1001295032 number, the 129 corresponds to LBVC (i.e. a surface level)), the 50 is the section (i.e. UKCA diagnostics section) and 32 corresponds to item number 32 (which is not helpful being only 2 digits rather than specifying 3). So this is telling us that diagnostic s50i032 is defined as a surface level in its STASHmaster_A entry.

I will mark this ticket as closed. Please let me know if us know if you need further assistance.

Many thanks and best wishes,
Luke.