Opened 7 years ago

Closed 6 years ago

#1354 closed help (fixed)

Nudging on UM vn.8.4

Reported by: webber24 Owned by: um_support
Component: UM Model Keywords: Nudging vn.8.4
Cc: Platform: ARCHER
UM Version: 8.4


Am running the UM on ARCHER and attempting to nudge my model run. I am unsure how to do this as I receive an error when I follow (some of) the guidelines set out on the following UKCA wiki for vn 7.3 ( I have not attempted to add other branches or hand edits, but have altered the following:

  • Deselected the 360 day calendar
  • Turned on nudging (and the nudging macro) under > Model Selection>Atmosphere>Scientific Parameters and Sections> Section by section choices> Section 39
  • Altered the page > Model Selection>Atmosphere>Control>Post processing, Dumping and Meaning> Dumping and Meaning as in the wiki page above (bullet point 5 under Get Working at Vn7.3)
  • Have finally turned on Automatic Post-processing along with the Delete Superseeded restart dumps option.

The Error message I get in my output (.comp.leave file):

INTEGER, INTENT(IN) :: tropopause_level( &

ftn-352 crayftn: ERROR NUDGING_NUDGING_CONTROL, File = ../../../../../../../../home2/n02/n02/webber24/um/xkctx/umatmos/ppsrc/UM/atmosphere/nudging/nudging_nudging_control.f90, Line = 163, Column = 30

"TROPOPAUSE_LEVEL" has the INTENT attribute, therefore it must be a dummy argument.

I hope I have been thorough enough,

Many Thanks,


Change History (5)

comment:1 Changed 7 years ago by luke

Dear Chris,

You will need to remove the INTENT(IN) on the declaration of tropopause_level in the files src/atmosphere/nudging/nudging_nudging_control.F90, which should solve this problem.

Please also see ticket

I'm just finishing up getting the ARCHER vn8.4 release ready (currently a problem with climate meaning) but when that is ready I would advise moving to that. This bug has already been fixed in that job.


comment:2 Changed 7 years ago by webber24

Dear Luke,

Thank you for the above advice, this has worked. A new issue has arisen regarding "Wrong Calendar set in Ancillary Files". I have attached the branches (and hand edit) you advised in ticket #1312, which should enable all ancillaries to be compatible with the Gregorian calendar, but to no avail.

Is this a bug within the model, or have I missed something?

The job id is xkctx.

Many Thanks,


comment:3 Changed 6 years ago by annette

Hi Chris,

Is this still an issue, or can we close the ticket?

Best wishes,

comment:4 Changed 6 years ago by webber24

This is fine to close, thanks Annette

comment:5 Changed 6 years ago by annette

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