Skip to content

Potential make_coupler_mosaic bug when using --land_mosaic #366

@JosephMouallem

Description

@JosephMouallem

A strange behavior was encountered when using make_coupler_mosaic for a coarse C48 atmosphere and 1 degree ocean configuration. Some fields on the coupler level are not populated correctly with null values in certain locations leading to a model crash.
The issue occurs when adding --land_mosaic to the call. It works fine without --land_mosaic.
This behavior was observed on C6 using both serial and parallel versions of make_coupler_mosaic of fre-nctools-parallel/2024.04.

Below is an example:

  1. Fails (with --land_mosaic)
    srun --ntasks=$npes make_coupler_mosaic_parallel --atmos_mosaic atmos_mosaic.nc --land_mosaic land_mosaic.nc --ocean_mosaic ocean_mosaic.nc --ocean_topog topog.nc --mosaic_name grid_spec --area_ratio_thresh 0.0001 --check --print_memory --verbose

data location: /gpfs/f6/bil-coastal-gfdl/proj-shared/Joseph.Mouallem/shiemom_pdata/GLOBAL/C48_1deg_mask_issue

  1. Works (without --land_mosaic):
    srun --ntasks=$npes make_coupler_mosaic_parallel --atmos_mosaic atmos_mosaic.nc --ocean_mosaic ocean_mosaic.nc --ocean_topog topog.nc --mosaic_name grid_spec --area_ratio_thresh 0.0001 --check --print_memory --verbose

data location: /gpfs/f6/bil-coastal-gfdl/proj-shared/Joseph.Mouallem/shiemom_pdata/GLOBAL/C48_1deg_ok

For more info check this slide deck.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions