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

mkiau.x produces bad agcm_import_rst using latest model version in the GEOSfixture. #54

Closed
bena-nasa opened this issue Dec 2, 2020 · 8 comments

Comments

@bena-nasa
Copy link
Collaborator

bena-nasa commented Dec 2, 2020

Proactive note to remember an issue needed to be addressed as we move the model version forward from the initial 5_27_1 version.
During my testing of taking the 5_27_1 candidate of the GEOSadas fixture to use the latest version of the libraries (GEOSgcm_GridComp etc) after fixing the other setup issues (#50, #51, #52, #53) the model runs 3 hours before segfaulting in radiation. If no agcm_import_rst is specified (i.e. no increment applied) the model runs fine. Wildly speculating, perhaps related to changes I see in the GEOSagcm_GridComp.F90 version in the 5_27_1 candidate tag related to the increment handling that are not in the latest version of the GEOSgcm_GridComp repository? Just noting here for my memory.

@bena-nasa
Copy link
Collaborator Author

bena-nasa commented Dec 2, 2020

A further development. I compared the agcm_import_produced by the stock code vs my attempt to update the libraries.
In the file from the stock code I see this when examining the values

 0    13824       0 :     -9.3998   -0.029315      6.6830 : DTSDT

vs my updated library version

0    13824       0 : -1.0318e+05     -24225.      51.908 : DTSDT

That is the biggest discrepancy but lots of others are different to a degree that seems more than roundoff
That probably explains it. Will try to figure out what is happening. Since this uses mkiau_GridComp the issue could be there, could be MAPL, hard to say.

@bena-nasa bena-nasa changed the title C48 3d var test case fails in due to increment when using latest model version in the GEOSfixture. mkiau.x produces bad agcm_import_rst using latest model version in the GEOSfixture. Dec 2, 2020
@mathomp4
Copy link
Member

mathomp4 commented Dec 2, 2020

@bena-nasa These are cdo infon outputs? So the fp numbers are min/mean/max values, right?

@bena-nasa
Copy link
Collaborator Author

Yes, that was the most egregious example. Something clearly went wrong. My first guess is mkiau_GridComp.

@bena-nasa
Copy link
Collaborator Author

I'm thinking this is a case of the iau grid comp and mkiau.F90 generate nx/ny differently. I'm modifying mkiau.F90 to compute nx/ny like the grid comp now does.

@bena-nasa
Copy link
Collaborator Author

bena-nasa commented Dec 14, 2020

Yep, that was it, just an inconsistency with the IAU grid comp and mkaiu.F90 in the nx/ny used. The solution is to use MAPL_MakeDecomposition in mkiau.F90 rather than read nx/ny from the input file. You also have to compute two sets of nx/ny values. One for the lat-lon grids and one for cube grids with the reduceFactor=6 argument to MAPL_MakeDecomposition for the cube nx/ny
I will keep this issue open for now so we don't forget this when the ADAS moves to using newer versions of the IAU grid comp

@rtodling
Copy link
Collaborator

rtodling commented Nov 2, 2021

Is this still an issue? Do we have a problem running IAU that is going unnoticed. This is unclear to me! I don't see a problem running IAU!

@bena-nasa
Copy link
Collaborator Author

It appears to be fixed. If I look in the develop branch of the GEOSadas fixture and look in mkiau.F90 I see it call MAPL_MakeDecomposition as I suggested so I must have done this when we were making the git tag for the ADAS.

@bena-nasa
Copy link
Collaborator Author

I'm closing this issue as it has been fixed

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

No branches or pull requests

3 participants