The road to regional coupled modelling (rCM3)

Hi all.

For rCM3 development I’d like to build a NUOPCY executable that can run inside a debugger.

I need some advice as to the best way to achieve this:

Currently, the CM3 config (latest branch is https://github.com/ACCESS-NRI/access-cm3-configs/tree/cm3-O100km-vn13.8) does the following (I think?)

  1. Uses UM sources from https://github.com/ACCESS-NRI/UM/tree/vn13.8_nuopc (which contains the required files in src/control/top_level)

  2. Pulls a pre-build SPACK MOM6 executable (access-om3/pr79-12 according to https://github.com/ACCESS-NRI/access-cm3-configs/blob/cm3-O100km-vn13.8/rose-suite.conf)

  3. Build the NUOPCY executable locally

So, in order the build the NUOPCY executable with debug symbols, I should

a) Create a new om3 pull request to compile with debug symbols, similar to Claire’s pr120? MOM6 symmetric with updated MOM6 version by claireyung · Pull Request #120 · ACCESS-NRI/ACCESS-OM3 · GitHub (which was built with -gflags on branch cy-pananopt according to ACCESS-OM3/spack.yaml at cy-pananopt · ACCESS-NRI/ACCESS-OM3 · GitHub )

b) Change the value of OM3_MODULEin the rose-suite.conf

Then compile the NUOPCY executable locally (including compiling the UM locally w/debug options).

Any thoughts @cbull, @kieranricardo, @harshula ?

Note - last time I tried to load access-om3/pr120-19 into Linaro it couldn’t find the debug symbols, see this thread :