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

Workaround for MAPL dependencies #254

Merged

Conversation

climbfuji
Copy link

There is a long discussion in the ufs-weather-model (ufs-community/ufs-weather-model#1854) and in MAPL (GEOS-ESM/MAPL#2320) on missing (implicit) dependencies for MAPL. It's been fixed in MAPL develop, but this version won't be used in the software stack for a while.

Meanwhile, we need to find the dependencies for GOCART in spack-stack-1.5.0 explicitly. Because of the QUIET attribute, this won't break other software environments where one or more of fargparse, yafyaml, pflogger are not installed.

… is merged and finds its way into the ufs-weather-model dependency tree
…/MAPL#2320 is merged and finds its way into the ufs-weather-model dependency tree
@mathomp4
Copy link
Member

Hopefully, MAPL 2.40.4 (and newer) obviate the need for this, but this lets it work with older versions. And, well, this is tested and as far as I can see, cannot hurt even when newer MAPL is tested.

@mathomp4 mathomp4 added 0 diff The changes in this pull request have verified to be zero-diff with the target branch. 0 diff trivial The changes in this pull request are trivially zero-diff (documentation, build failure, &c.) labels Sep 25, 2023
@mathomp4
Copy link
Member

@climbfuji I merged in latest develop and added a changelog entry for you.

@climbfuji
Copy link
Author

Ohhh ok, that's a problem if the ufs-weather-model is not at the top of develop at the moment ... do you have a feeling of what happens if we fast-forward the GOCART submodule pointer in the UFS?

@mathomp4
Copy link
Member

Ohhh ok, that's a problem if the ufs-weather-model is not at the top of develop at the moment ... do you have a feeling of what happens if we fast-forward the GOCART submodule pointer in the UFS?

Ohhh. Do you know what version you are using?

@climbfuji
Copy link
Author

hash 6ea78fd

@mathomp4
Copy link
Member

@climbfuji Well, it looks like that is essentially our main and now the only difference is fixes from #253 for FENGSHA that just got in:

6ea78fd...develop

So it is at most no change and if not, better, if you are running FENGSHA.

@mathomp4
Copy link
Member

If you are okay with that, I can work with @vbuchard to get your fix into develop as well (since it cannot affect our way of building GOCART at all)

@climbfuji
Copy link
Author

Should we change the target branch to main then and revert the merge from develop? Or merge this as-is into develop and then cherry-pick for another PR to main?

@bbakernoaa
Copy link

We will need the latest develop branch as there is a need from a scientific standpoint for the dust scheme. I ran a test with the latest develop and it works fine with the current version of MAPL. ufs-community/ufs-weather-model#1922

@climbfuji
Copy link
Author

That's great news, thanks @bbakernoaa. @mathomp4 How about we merge this now, and then I'll either wait for @bbakernoaa 's PR to go in first, or I update the submodule pointer in my ufs-weather-model PR?

@bbakernoaa
Copy link

@climbfuji if you want to include the submodule update in your PR that is fine with me. We just need to get this moving for the EP5 experiments.

@climbfuji
Copy link
Author

@bbakernoaa To confirm, do I need the changes in tests/parm/gocart/DU2G_instance_DU.rc from your PR?

https://github.com/ufs-community/ufs-weather-model/pull/1922/files

I am getting segfaults without them when I run the cpld_control_p8_intel test on Hera (spack-stack-1.5.0).

137: pe=00137 FAIL at line=00187    DU2G_GridCompMod.F90                     <status=41>
137: pe=00137 FAIL at line=04602    MAPL_Generic.F90                         <status=41>
137: pe=00137 FAIL at line=04789    MAPL_Generic.F90                         <status=41>
137: pe=00137 FAIL at line=01335    GOCART2G_GridCompMod.F90                 <status=41>
121: pe=00121 FAIL at line=00187    DU2G_GridCompMod.F90                     <status=41>
123: pe=00123 FAIL at line=00187    DU2G_GridCompMod.F90                     <status=41>
...

@mathomp4
Copy link
Member

@climbfuji That looks to me like the answer is yes. ESMF is complaining that it can't satisfy soil_moisture_factor since the call has no default:

       call ESMF_ConfigGetAttribute (cfg, self%f_swc,      label='soil_moisture_factor:', __RC__)

@climbfuji
Copy link
Author

@climbfuji That looks to me like the answer is yes. ESMF is complaining that it can't satisfy soil_moisture_factor since the call has no default:

       call ESMF_ConfigGetAttribute (cfg, self%f_swc,      label='soil_moisture_factor:', __RC__)

Thanks, I cherry-picked that commit in my branch so that credits go to @bbakernoaa and not me, testing now.

@bbakernoaa
Copy link

@climbfuji Yes you will need those. Otherwise the GOCART component will crash. The attributes must be present in .rc file.

Copy link
Contributor

@vbuchard vbuchard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Trusting @mathomp4 on this one. Thanks

@vbuchard vbuchard merged commit 0414229 into GEOS-ESM:develop Sep 27, 2023
4 checks passed
@climbfuji climbfuji deleted the feature/workaround_mapl_spackstack150 branch September 27, 2023 13:58
@climbfuji climbfuji restored the feature/workaround_mapl_spackstack150 branch September 27, 2023 13:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 diff trivial The changes in this pull request are trivially zero-diff (documentation, build failure, &c.) 0 diff The changes in this pull request have verified to be zero-diff with the target branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants