Opened 6 months ago

Closed 3 months ago

#3206 closed error (answered)

check_iostat/RUN_UKCA namelist issue

Reported by: SarahShallcross Owned by: um_support
Component: UM Model Keywords: iostat, RUN_UKCA
Cc: Platform: ARCHER
UM Version: 8.4

Description

Hello,

I've tried to look for previous tickets on this, but have only found one that had to do with a namelist http://cms.ncas.ac.uk/ticket/1969.

I have been trying to rerun a previous run (xojgc) just with a different dump file (xolmc), but keep coming across an error with "check_iostat" (below).
I double checked that a run that was working last week was working now and have come across the same error (xotnj).

????????????????????????????????????????????????????????????????????????????????
???!!!???!!!???!!!???!!!???!!!???!!! ERROR ???!!!???!!!???!!!???!!!???!!!???!!!?
? Error in routine: check_iostat
? Error Code: 4324
? Error Message: Error reading namelist RUN_UKCA. Please check input list against code.
? Error generated from processor: 0
? This run generated 3 warnings
????????????????????????????????????????????????????????????????????????????????

ATP Stack walkback for Rank 0 starting:

_start@…:113
libc_start_main@…:242
main@…:48
um_shell_@…:1661
readlsta_@…:1884
check_iostat$check_iostat_mod_@…:51
ereport64$ereport_mod_@…:107
gc_abort_@…:137
mpl_abort_@…:46
MPI_ABORT@0x17e8e0c
PMPI_Abort@0x180789c
MPID_Abort@0x1830b71
abort@…:92
raise@…:42

ATP Stack walkback for Rank 0 done
Process died with signal 6: 'Aborted'
Forcing core dump of rank 0
View application merged backtrace tree with: stat-view atpMergedBT.dot
You may need to: module load stat

These errors can be found in the .leave file in:
/home/n02/n02/sarahs93/output/xolmc000.xolmc.d20060.t185700.leave

Hopefully that makes sense and I haven't missed something obvious!
Let me know if you need more detail.

Thank you,
Sarah

Change History (6)

comment:1 Changed 5 months ago by grenville

Sarah

I'm a bit confused:

xojgc and xolmc are different jobs - the list of branches included is different between the two.

Does xojgc work at all, where does xolmc come from?

Grenville

comment:2 Changed 5 months ago by SarahShallcross

Hi Grenville,

Sorry, xojgc was initially run by Graham using a different dump file.
The xolm experiment was me trying to run that same job with a different dump file and changing the lat/lons for the 16 lidar sites that output to the .pg files.

I first tried running xolmb, which is a copy of xojgc but with some STASH changes and a different dump file - this also errored for the iostat/RUN_UKCA reason above.
xolmc was me testing whether I could make the necessary changes (the lat/lon changes) in a model run that had run successfully a week before (xotna).

After this I checked a different model run that had also run successfully the week before (with no changes, just to check whether it would run) and got the same error.

Apologies, it's a little convoluted - but basically I have tried about 5 different model runs, 2 of which had successfully run the week before and got the same iostat/RUN_UKCA error for them all.

Thanks,
Sarah

comment:3 Changed 5 months ago by grenville

Sarah

What should I try to run when ARCHER comes back?

Grenville

comment:4 Changed 5 months ago by SarahShallcross

Hi Grenville,

xolmc please!

Sarah

comment:5 Changed 5 months ago by grenville

Hi Sarah

The code expects a RUN_UKCA namelist with ~100 entries - but your job has ~120. The code does not expect things like:

AEROS_BL_NUC=1.00,
AEROS_FT_NUC=1.00,
AEROS_AGEING=3.00,
AEROS_Accumulation_Width=1.50,
AEROS_Aitken_Width=1.50,
AEROS_CLOUDPH=1.26E-06,
AEROS_FF_EMS=1.00,
AEROS_BB_EMS=1.80,
AEROS_BF_EMS=1.40,
AEROS_FF_Diameter=58.0,
….

It looks like there is a branch missing - I can't help much with that.

Grenville

comment:6 Changed 3 months ago by grenville

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

closed through inactivity

Note: See TracTickets for help on using tickets.