Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calculate fluxes in MOAB coupler with MOAB data #6996

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

rljacob
Copy link
Member

@rljacob rljacob commented Feb 12, 2025

Calculate fluxes and ocean albedos in MOAB coupler with data in the MOAB meshes.
Prior to this change, the fluxes were calculated with MCT data and then copied to MOAB data structures.
Verified by inspection of xao fields before and after this change using Visit.

[BFB]

Add new shr_moab_mod file that will contain
usefule moab-based functions and subroutines.
First 3: mbGetnCells, mbGetTagVals, mbSetTagVals
Convert seq_flux_atmocn_mct to use MOAB data.
The local fortran arrays are sized according to number of
points locally in MOAB.  Arrays are intialized from MOAB app
and results are copied directly to a MOAB app.

MCT-based fluxes are never set.
Rename seq_flux_atmocn_mct in moab coupler to
seq_flux_atmocn_moab and remove the old moab version
Convert seq_flux_ocnalb to use MOAB data.
Create new local fortran arrays to perform calculations.
Fill from MOAB apps and copy to MOAB apps

MCT-based fluxes and albedos are not set
@rljacob rljacob requested a review from iulian787 February 14, 2025 03:23
@rljacob rljacob marked this pull request as ready for review February 14, 2025 03:24
@rljacob
Copy link
Member Author

rljacob commented Feb 15, 2025

Note: once this is merged, the MOABCOMP output will show diffs for the flux fields since the MCT versions are always 0.

@rljacob rljacob self-assigned this Feb 17, 2025
@rljacob rljacob marked this pull request as draft March 3, 2025 05:54
@rljacob
Copy link
Member Author

rljacob commented Mar 3, 2025

Converted back to draft because want to merge after #7015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant