Opened 3 months ago

Last modified 3 months ago

#3125 new help


Reported by: pmcguire Owned by: um_support
Component: UM Model Keywords: UM, WRITHEAD
Cc: mtodt Platform: ARCHER
UM Version:


Hello CMS helpdesk:
I have been able to get my UM AMIP suite (u-bq290) working on Archer with UM11.0 (I have also done this for UM11.5). It ran fine to the Wallclock limit of 15 minutes in the short queue. I tried to increase the Wallclock limit to 300 minutes in the standard queue, but I get this error message now:

???!!!???!!!???!!!???!!!???!!!       ERROR        ???!!!???!!!???!!!???!!!???!!!
?  Error code: 24
?  Error from routine: WRITHEAD
?  Error message: WRITHEAD: Addressing conflict
?  Error from processor: 52
?  Error number: 99

I am sure I am doing something silly wrong, but I don't immediately know or see what it is.
Can you point me in the right direction?

Change History (5)

comment:1 Changed 3 months ago by dcase

If you've only changed the queue settings and the thing submits and starts to run, then I'd just do the basic things first, i.e. check your disk quota and rerun the task. Possibly there was a temporary disk problem???

I'll look at it later if the trivial things above don't fix it, but it's probably worth re-triggering just in case they help.

comment:2 Changed 3 months ago by grenville


Please allow group read permission on your ARCHER /home and /work spaces


comment:3 Changed 3 months ago by pmcguire

Thanks, Dave & Grenville
I just did a restart of the u-bq290 suite.
The u-bq296 suite had similar problems, if you want to look at things for that suite instead. (The restart might have erased some files from u-bq290).
I changed the group read permissions for my ARCHER /home and /work spaces.

comment:4 Changed 3 months ago by pmcguire

Hi Grenville & Dave

I have done a 'rose suite-run' without the '—restart', and I have reduced the dump frequency from 10 days to 10 time steps. It's the u-bq290 suite. I still get the same WRITHEAD errors. The WRITHEAD error messages seem to have multiple possible causes.
See: puma:/home/pmcguire/um/vn11.0/src/control/dump_io/writhead.F90.

I guess one possible next step is to disambiguate these 'WRITHEAD: Addressing conflict' error messages in this routine with better print statements. I can try to do that.

Or maybe there are other possible next steps?

comment:5 Changed 3 months ago by grenville


I think the simplest thing will be to take a standard 11.5 job and add easyaerosol etc to that. I can't imagine the problem is with writhead.F90 - you may end up be going down an endless rabbit hole chasing this.


Note: See TracTickets for help on using tickets.