Netcdf format from MOM6

[anton-seaice]

Netcdf format from MOM6

[anton-seaice]

It looks like we don't use the MOM_netcdf module I linked and its controlled by FMS. For some reason we use the "deprecated_io" option from FMS.

With "deprecated_io", I think the format is controlled by cpp macros, and so we need to turn off the "+large_file" option in spack, and then the default will be netcdf4.

Alternatively, we could try using the "fm2_io" option, (i.e. turn off "+deprecated_io") but I assume there was a good reason this option is set (@micaeljtoliveira) ?

[anton-seaice]

@micaeljtoliveira confirmed removing +deprecated_io is ok

Once we have done that, we can add

&fms2_io_nml
    netcdf_default_format = "netcdf4"
    deflate_level = 1
/

+deprecated_io is not in the access-nri om3 build , so we can wait for that and then make the config update needed.

[anton-seaice]

I think you need to remove "+large_file +deprecated_io" from https://github.com/COSIMA/spack-config/blob/7a477783782e62b0f743937c7c512b5ca42835f4/environments/access-om3-0_x_0/spack.yaml#L20 and then build. Then in the config update input.nml

[dougiesquire]

I'm moving this to priority:high because we should do this before any long runs for parameter tests. I'll do a new development release of ACCESS-OM3 using the COSIMA build infra so that we have something to test ASAP

[anton-seaice]

Closed through :

• ACCESS-NRI/access-om3-configs#91
• ACCESS-NRI/access-om3-configs#102
• ACCESS-NRI/access-om3-configs#103
• ACCESS-NRI/access-om3-wav-configs#44
• ACCESS-NRI/access-om3-wav-configs#45