-
Notifications
You must be signed in to change notification settings - Fork 19
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
SCM Model Failing with MAPL develop #2601
Comments
As for how to run the SCM. Build GEOSgcm and then go to
Obviously, change the account to whatever you like. Then go to
By default arm_97jul runs for 30 days, but you can change |
The issues is that somehow when that binary file vegdyn is loaded as an ESMF HConfig, ESMF is not failing for some reason as saying it could load that as a config which is weird. I can change to just say rather than assuming it is split if the HConfigCreate success to be if the yaml file has the key. But I don't like that HConfig loaded that in the first place without failing. However, this exposed what is probably another error than as been there forever since @mathomp4 nightly testing uses the release build and I was using a debug build:
|
I mean, if I had to guess, it's probably a bug somewhere in Datmodyn. Maybe something that should be 73 in size is only 72? Or vice versa? Couplers are beyond me at times. Might need @atrayano help on this. I mean, I don't even know what this code really does in MAPL! |
This issue has been automatically marked as stale because it has not had activity in the last 60 days. If there are no updates within 7 days, it will be closed. You can add the ":hourglass: Long Term" label to prevent the stale action from closing this issue. |
Closing this as, well, SCM works now. |
My nightly tests are throwing SCM run failures with MAPL
develop
(andrelease/MAPL-v3
). The first failure was:I consulted @atrayano (as this line was from #2592) and changed:
_ASSERT(num_readers < ny,'num readers must be less than NY')
to:
This gets past the first error, but now:
This is new code from #2394 by @bena-nasa . I've consulted him and he said he can take a look.
I've committed the first fix on
bugfix/mathomp4/scm-fixes
and have a draft PR open at #2602The text was updated successfully, but these errors were encountered: