Opened 4 years ago

Closed 3 years ago

#1647 closed help (fixed)

has NEMO3.4 been installed on the XCM?

Reported by: till Owned by: annette
Component: NEMO/CICE Keywords: xcml00, coupled
Cc: Platform: MONSooN
UM Version: 8.6


Dear CMS Team,
I am migrating my UKESM experiments from the old MONSooN to the XCM. Trial with N96 AMIP is ongoing (xltwa).
My question is: has NEMO3.4 been installed already on the XCM? If so, I could use it for my coupled N96-ORCA1 jobs (example: xllfk).
Thank you!

Change History (8)

comment:1 Changed 4 years ago by annette

  • Cc k.sivalingam@… added
  • Platform changed from Other to MONSooN

Hi Till,

Karthee has run a coupled UM 8.6 - NEMO 3.4 job on xcm. This is N96-ORCA025 but you should be able to copy the NEMO/CICE and OASIS configurations. The job id is xlsdd.

There is a bit of an issue with the UMUI for the coupled model at this version. We are working on this, but in the meantime a couple of hacks are required (see below).

Do let us know if you have any issues with this.



From Karthee (cc'ed)

Please refer to /projects/umadmin/ksival/um/xlsdd/umatmos/cfg/bld.cfg file for exact entries.

  1. The following entry is to be added to the bld.cfg file of umatmos.
    tool::fflags::UM::control::coupling                    -O2 -Ovector1 -s default64 -em -J. -hfp0 -hflex_mp=strict -I/projects/umadmin/ksival/gcom/cce/gcom4.7/xc40_cce_mpp/build/include  -INetCDFmodule  -I$(UMDIR)/grib_api/cce-8.3.4/1.13.0/include -h noomp -I/projects/umadmin/ksival/oasis/oasis3_3/20110919_para_MxSeg1500/prism/crayxc40_cce/build/lib/mpp_io -I/projects/umadmin/ksival/oasis/oasis3_3/20110919_para_MxSeg1500/prism/crayxc40_cce/build/lib/psmile.MPI1 -I/projects/umadmin/ksival/oasis/oasis3_3/20110919_para_MxSeg1500/prism/crayxc40_cce/build/lib/oasis3.MPI1
  1. the entry C98_1A=c98_1a should be modified to C98_0A=c98_0a in
    • tool::cppkeys and
    • tool::fppkeys

comment:2 Changed 4 years ago by till

Hi Annette,
thanks a lot for that, this look promising!

However the job (I copied it to XLTWB) does not compile yet I'm afraid. This is the error message in the .leave file:

ERROR: /projects/ukesm/tkuhlb/um/xltwb/umatmos/cfg/bld.cfg: LINE 50:
       tool::fflags::UM::control::coupling::oasis3_atmos_init: invalid sub-package in declaration.

The thing is this: I applied the hack from Karthee to this file, but when I resubmit the job, everything is extracted from anew and the hack is overwritten. I guess that is the problem? It would be great if you could look into this.

comment:3 Changed 4 years ago by annette

  • Cc k.sivalingam@… removed
  • Owner changed from um_support to annette
  • Status changed from new to assigned

comment:4 Changed 4 years ago by annette

Hi Till,

Edit the file again, then instead of re-submitting from the UMUI which will cause the cfg files to be ovewritten, just manually re-submit from the umui_runs directory.

  • Cd to ~/umui_runs on MONSooN.
  • Find the latest directory for this job-id through ls -alrt.
  • Cd into that directory.
  • Run qsub stage_1_submit.


comment:5 Changed 4 years ago by till

Hi Annette,
thank you for that. The compilation job now runs much longer (approx. 12 min), but eventually still fails I'm afraid. (XLTWB on the XCM.) The main reason appears to be:

ftn-855 crayftn: ERROR IOS_INIT, File = ../../../../../projects/ukesm/tkuhlb/um/xltwb/umatmos/ppsrc/UM/io_serv
ices/server/ios_init.f90, Line = 16, Column = 8 
  The compiler has detected errors in module "IOS_INIT".  No module information file will be created for this 

The .comp.leave file is here: /home/tkuhlb/output/xltwb000.xltwb.d15253.t132900.comp.leave

I admit that I had to tinker with the bld.cfg file a little more than explained above. Intially it had a few lines starting with tool::fflags::UM::control::coupling::oasis3 which I had to remove in order to make the compilation job work at all. There's still some differences to Karthee's file named above, e.g. whether this line:
tool::cflags -O2 -g -std=c99 -h omp
has omp or noomp at the end.

Thank you for your help!

comment:6 Changed 4 years ago by annette

Hi Till,

I think you may need to have OpenMP switched off - so change the -h omp to -h noomp wherever it appears. (We thought you might get away without changing this.)


comment:7 Changed 3 years ago by annette


The compile issue with the IO server code and OpenMP has been fixed (hack number 2 mentioned above). We have updated the central configuration files so this should be picked up by your jobs automatically when you submit a compile job.

I will update you about hack number 1 shortly.


comment:8 Changed 3 years ago by annette

  • Keywords xcml00, coupled added; xcml00 removed
  • Resolution set to fixed
  • Status changed from assigned to closed

I think that the OASIS paths have now been fixed properly in the config files as well. If you have any further issues, obviously do get back in touch.


Note: See TracTickets for help on using tickets.