Ok, so I think I got past the cice namelist issue in my latest test case, but I’m now running into a problem with the MOM5 executable producing invalid memory reference.
[c004:1186587:0:1186587] Caught signal 11 (Segmentation fault: address not mapped to object at address (nil))
WARNING from PE 2: ocean_model_init called with an associated ocean_state_type structure. Model is already initialized.
[c004:1186585:0:1186585] Caught signal 11 (Segmentation fault: address not mapped to object at address (nil))
==== backtrace (tid:1186587) ====
0 0x000000000003e6f0 __GI___sigaction() :0
1 0x0000000001448d97 __mpp_domains_mod_MOD_mpp_get_compute_domain2d() ???:0
2 0x000000000124a1a9 __data_override_mod_MOD_data_override_init() ???:0
3 0x000000000040fd4a MAIN__() /tmp/david.hutchin6926/spack-stage/spack-stage-mom5-git.2025.08.000_access-om2-4ny34dmjy4xafgra4wpzi7pz75cx6tdb/spack-src/src/access/accessom_coupler/ocean_solo.F90:394
4 0x0000000000406ffd main() /tmp/david.hutchin6926/spack-stage/spack-stage-mom5-git.2025.08.000_access-om2-4ny34dmjy4xafgra4wpzi7pz75cx6tdb/spack-src/src/access/accessom_coupler/ocean_solo.F90:81
5 0x0000000000029590 __libc_start_call_main() ???:0
6 0x0000000000029640 __libc_start_main_alias_2() :0
7 0x0000000000407035 _start() ???:0
=================================
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Note: I ran into pretty much the same error when I tried to run a GCC-compiled version of MOM5 recently. I think it’s to do with how MOM5 specifies BOZ literals in the MPP domains module.
For example, this part of the code:
And several other BOZ examples in that module. I couldn’t easily compile those with gfortran, and when did get it to compile, I would get this same kind of invalid memory reference at run time with MOM5.
My solution in that case was to switch to intel fortran compilers which seem to handle the BOZ specification ok. Regrettably, that pathway would mean I can’t use the spack configuration that @harshula has set up on NeSI for me, and will instead seek to compile cice5 and yatm using the intel compilers that are available on NeSI (but don’t seem to play nice with spack currently).