Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#352 closed help (fixed)

Additional PC2 diagnostics

Reported by: kipling Owned by: willie
Component: Diagnostics Keywords:
Cc: Platform:
UM Version: 7.1


In the PC2 documentation (annexe to UMDP29, s5.3) it is mentioned that the increments to prognostic cloud variables from certain sections of code (erosion, pressure forcing, initiation and bounds checking) are not ordinarily available, but are provided as diagnostics via a modset and user-STASHmaster file. Are these already available on PUMA, or will I need to request them from the Met Office?

Attachments (2)

STASHMASTER_pc2_incr_7p1 (30.0 KB) - added by willie 11 years ago.
files.tar.gz (104.9 KB) - added by willie 11 years ago.

Download all attachments as: .zip

Change History (6)

Changed 11 years ago by willie

Changed 11 years ago by willie

comment:1 Changed 11 years ago by willie

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

Hi Zak,

I have asked the Met Office and they have provided the attached user STASHmaster and fortran files.

There will be updates version of 4 files, a new subroutine and a
stashmaster file. These were taken from a VN7.4 branch (but there is no
reason why they shouldn't also work at 7.1)

If they don't work immediately then do a diff between the files below
and your pristine 7.1 versions and just apply those changes.

atmos_physics1.F90 (modified) (5 diffs)
diagnostics_pc2checks.F90 (added)
diagnostics_conv.F90 (modified) (2 diffs)
st_diag2.F90 (modified) (3 diffs)
atm_step.F90 (modified) (1 diff)

(The STASHmaster is also contained in the compressed tar file.)



comment:2 Changed 11 years ago by kipling

Thanks for that; I've imported these changes into FCM:

fcm:um_br/dev/kipling/VN7.1_pc2_incr (

and am now testing them.

comment:3 Changed 11 years ago by willie

  • Resolution set to fixed
  • Status changed from assigned to closed

comment:4 Changed 11 years ago by kipling

Mohit has pointed out to me that this patch left the ST_DIAG2 call in INITDIAG out of sync with the definition, although so far as I can tell this hasn't caused any problems.

In any case, code for these diagnostics has since appeared on the trunk, as, if anyone else needs it.

Note: See TracTickets for help on using tickets.