Opened 2 years ago

Closed 2 years ago

#313 closed (fixed)

CICE compiler

Reported by: rb4844 Owned by: Martin Dix
Priority: major Component: ACCESS-CM2
Keywords: CICE, configuration Cc:

Description (last modified by Martin Dix)

The CICE build configuration in our current test suites is on the Raijin side, not from the accessdev suite. Can this be changed so that CICE can be configured from rose edit?

Attachments (1)

rose-edit-ocean-decomposition.png (81.0 KB) - added by Martin Dix 2 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 Changed 2 years ago by rb4844

Component: ACCESS modelACCESS-CM2

The CICE compiler in our current test suites is on Raijin side, not accessdev side. Can this be changed so that CICE can be configured from rose edit?

Last edited 2 years ago by rb4844 (previous) (diff)

comment:2 Changed 2 years ago by Martin Dix

In the extracted CICE directory the compiler module is loaded in compile/environs.raijin-185 which is included in the build script comp_access-cm360-185. These files are left-overs from the build outside the suite and now aren't used.

In the coupled model suite (e.g. u-am527), app/make2_cice/rose-app.conf has

[command]
default=comp_access-cm-rose-185

Despite the misleading 185 in the name, this doesn't load any modules itself or include environs.raijin-185, so just uses the ones loaded in the suite.

The compiler version used is written in bytes 37-40 of module files (name.mod) but not object files.

My suite u-am567 uses an unmodified environs.raijin-185 but CICE is still built with v17

E.g.

% od --skip-bytes=36 --read-bytes=4 -c  ~mrd599/cylc-run/u-am567/share/cice/compile_360x300/build_MPI1_16p-mct-185/ice_history_write.mod        
0000044   1   7   .   0

C.f. a file built with the v15 compiler

% od --skip-bytes=36 --read-bytes=4 -c  /g/data/access/cylc-run/vn10.7_prebuilds/fcm_make_nci_um_safe_omp/build-atmos/include/timestep_mod.mod 
0000044   1   5   .   0

Apart from the confusing name of the build command I don't think there's a problem.

comment:3 Changed 2 years ago by Martin Dix

Owner: set to Martin Dix
Status: newaccepted

comment:4 Changed 2 years ago by Martin Dix

Description: modified (diff)

comment:5 Changed 2 years ago by rb4844

Martin,

I maybe need to explain/clarify a bit more. I am referring to, for example, /home/599/rb4844/cylc-run/u-am379/share/cice/compile, the file comp_access-cm360-185 - its part of the build process, not actually the compiler - sorry, not sure of what to call the different bits.

comp_access-cm360-185 is the problem - this contains the information about the CICE decomposition, and it sits on the Raijin side.

To change the cpus for CICE you have to do it in this script - otherwise nothing changes. The settings on the accessdev side are only partially taken up - so if you set cpus to 28 for example with rose edit or in rose_suite.conf, the run command expects 28 cpus to be used, a model for 28 cpus gets built, but comp_access-cm360-185 does not get changed, and then the job crashes as the default here is 16 cpus. The script drops through to this point:

echo
#24 : 12x2
setenv BLCKX 30
setenv BLCKY 150
#16 : 8x2
setenv BLCKX 45
setenv BLCKY 150

allocating blocks for 16 cpus, which doesn't match up.

Changed 2 years ago by Martin Dix

comment:6 Changed 2 years ago by Martin Dix

In Met Office GC3.1 suites (e.g. u-an062) the NEMO and CICE builds use fcm.

rose-suite.conf has

CICE_BLKX=40
CICE_BLKY=42
CICE_COL=360
CICE_MAXBK=1
CICE_ROW=330

and app/fcm_make_ocean/rose-app.conf has

keys_cice_app=coupled ncdf CICE_IN_NEMO NEMO_XIOS key_oasis3mct key_nemocice_decomp gather_scatter_barrier ORCA_GRID NICECAT=5 NICELYR=4 NSNWLYR=1 TRAGE=1 TRLVL=0 TRPND=1 TRFY=0 NTRAERO=0 NBGCLYR=0 TRBGCS=0 TRBRI=0 NUMIN=150 NUMAX=249 REPRODUCIBLE key_iomput NXGLOB=$CICE_COL NYGLOB=$CICE_ROW BLCKX=$CICE_BLKX BLCKY=$CICE_BLKY MXBLCKS=$CICE_MAXBK

This appears in rose-edit as


An early version of our coupled suite also used fcm for the CICE build (though not for MOM) so it should be possible to restore this.

comment:7 Changed 2 years ago by Martin Dix

Resolution: fixed
Status: acceptedclosed

Suite u-ao219 demonstrates setting the CICE build environment from the suite.

Note: See TracTickets for help on using tickets.