Opened 14 months ago

Closed 14 months ago

Last modified 14 months ago

#2579 closed help (fixed)

replanca: pp headers do not match

Reported by: shakka Owned by: um_support
Component: UM Model Keywords: ancilliaries, orography, recon
Cc: Platform: Monsoon2
UM Version: 11.1

Description

Hi helpdesk,

I have been trying to get a version of the nested suite at v11.1 running using my own lsm/orog ancillaries, but am getting the following error on the recon stage:

IO: Open: /home/d04/elgil/cylc-run/u-ba217/share/data/ancils/Peninsula/km1p5/qrparm.orog on unit 13
replanca_rcf_replanca: UPDATE REQUIRED FOR FIELD 34 : STANDARD DEVIATION OF OROGRAPHY
c_io ( 13):c_io_unix: in: 4194304 bytes were requested, but only 2605056 were transfered - we have reached end-of-file : fd=58
replanca_rcf_replanca: UPDATE REQUIRED FOR FIELD 35 : OROGRAPHIC GRADIENT XX COMPONENT
I1,ancil_requests(irec) % stashcode 34 35 4
Error in replanca_rcf_replanca
CMESSAGE replanca_rcf_replanca: PP HEADERS ON ANCILLARY FILE DO NOT MATCH
ErrorStatus? 235

????????????????????????????????????????????????????????????????????????????????
???!!!???!!!???!!!???!!!???!!! ERROR ???!!!???!!!???!!!???!!!???!!!
? Error code: 235
? Error from routine: RCF_ANCIL_ATMOS
? Error message: replanca_rcf_replanca: PP HEADERS ON ANCILLARY FILE DO NOT MATCH
? Error from processor: 0
? Error number: 6
????????????????????????????????????????????????????????????????????????????????

The orography ancils I'm using don't contain orographic roughness or gradient components, which has previously worked fine (in version 10.4 runs at least). Is there a way to get the recon to skip over this so it doesn't request the non-existent fields from the ancil file?

Thanks,
Ella

Change History (5)

comment:1 Changed 14 months ago by shakka

Oops - sorry - should also have said that the suite id is u-ba217.

comment:2 Changed 14 months ago by willie

Hi Ella,

u-ba217 seems to have completed successfully. Is this still a problem?

Regards,
Willie

comment:3 Changed 14 months ago by shakka

Hi Willie,

I had to run it with default ancils instead, so yes - it is still a problem. However, I have now started using the latest version of the CASIM nesting suite at vn 11.1, so the suite ID is now u-ba502 (it has got past the UM_recon stage though, so it might be fine).

Ella

Last edited 14 months ago by shakka (previous) (diff)

comment:4 Changed 14 months ago by willie

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

Hi Ella,

Ok, if u-ba502 fails, raise a new ticket. I'll close this one now.

Regards
Willie

comment:5 Changed 14 months ago by shakka

OK, thanks Willie.

Note: See TracTickets for help on using tickets.