Skip to content

Add MOAB coupler support for Omega - #523

Open
vijaysm wants to merge 7 commits into
E3SM-Project:developfrom
vijaysm:vijaysm/omega/moab-support
Open

Add MOAB coupler support for Omega#523
vijaysm wants to merge 7 commits into
E3SM-Project:developfrom
vijaysm:vijaysm/omega/moab-support

Conversation

@vijaysm

@vijaysm vijaysm commented Aug 20, 2026

Copy link
Copy Markdown

Update interfaces to MOAB coupler by defining the Omega mesh in MOAB, and pushing/pulling data out of tags by defining and updating the data as needed by the driver. Tested only with a C-case, but I think it should work with any other case as well since the interface is uniform from the component standpoint.

Checklist

  • Documentation:

  • Linting

  • Building

    • CMake build does not produce any new warnings from changes in this PR
  • Testing

    aurora, oneapi-ifx, mpich

    • CTests Pass
    • Polaris omega_pr Pass

    chrysalis, oneapi-ifx, openmpi

    • CTests Pass
    • Polaris omega_pr Pass

    frontier, craygnu, mpich

    • CTests Pass
    • Polaris omega_pr Pass

    frontier, craygnu-mphipcc, mpich

    • CTests Pass
    • Polaris omega_pr Pass

    pm-cpu, gnu, mpich

    • CTests Pass
    • Polaris omega_pr Pass

    pm-gpu, gnugpu, mpich

    • CTests Pass
    • Polaris omega_pr Pass
  • Provide relevant details in a comment to the PR titled Testing with the following:

    • Which machines CTest unit tests
      have been run on and indicate that are all passing.
    • The Polaris omega_pr test suite
      has passed, using the Polaris e3sm_submodules/Omega baseline
    • Document machine(s), compiler(s), and the build path(s) used for -p for both the baseline (Polaris e3sm_submodules/Omega) and the PR build
    • Indicate "All tests passed" or document failing tests
    • Document testing used to verify the changes including any tests that are added/modified/impacted.
  • Performance related PRs: Please include a relevant PACE experiment link documenting performance before and after.

  • New tests:

    • CTest unit tests for new features have been added per the approved design.
    • Polaris tests for new features have been added per the approved design (and included in a test suite)
  • Stealth Features

    • If any stealth features are included in the PR, please confirm that they have been documented.

andrewdnolan and others added 7 commits August 10, 2026 12:46
Detect MOAB via OMEGA_MOAB_ROOT when COMP_INTERFACE=moab, define HAVE_MOAB,
and conditionally add/link MoabInterface.cpp. No effect when MOAB is absent.
registerApplication only registered an app. Now builds an owned-cells mesh
(vertex compaction, polygon elements, GLOBAL_ID tags), domain tags, and
x2o/o2x tag get/set. Also fixes header typos that blocked compilation.
Pass full CIME field-name lists to the C++ side, pick MOAB vs MCT layout at
compile time, and call the mesh/tag-storage functions around ocean init and
run. Drops the unused runtime layout selection it replaces.
moabInit's app id was staying local to the C++ side. The coupler-side
migration/mapping code reads seq_comm_mct's mpoid to locate the ocean mesh,
so leaving it at -1 meant it never found it, causing the crash and memory
corruption seen at runtime. Fortran now copies the id into mpoid.
component_init_areacor_moab reads area:aream:mask as one combined tag; a
missing tag fails the whole read. aream gets a -9999 placeholder, same
convention MCT uses, since the coupler fills in the real value later.
iMOAB_CreateElements expects connectivity entries to be 1-based (it computes
firstVertex + connectivity[j] - 1). Compact vertex indices were written
0-based, so every vertex reference pointed one slot too early.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants