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

Case SMS.f10_f10_mg37.X fails #396

Closed
jedwards4b opened this issue Jul 28, 2023 · 3 comments · Fixed by #397
Closed

Case SMS.f10_f10_mg37.X fails #396

jedwards4b opened this issue Jul 28, 2023 · 3 comments · Fixed by #397
Assignees
Labels
bug Something isn't working

Comments

@jedwards4b
Copy link
Collaborator

20230728 083532.319 ERROR            PET000  Map type consd, destcomp ocn,  mapnorm one set; cannot set mapnorm to none  Forr_rofi
20230728 083532.320 INFO             PET000 Finalizing ESMF
20230728 083532.320 ERROR            PET000 /glade/derecho/scratch/csgteam/temp/spack/derecho/23.06/builds/spack-stage-esmf-8.5.0-wadvsguui6ysezcdnhhnrdqkh7zigbvm/spack-src/src/Infrastructure/Trace/src/ESMCI_Trace.C:1816 ESMCI::TraceEventRegionExit() Wrong argument specified  - Trace regions not properly nested exiting from region: [ESMF] Expected exit from: [MED] IPDv03p7
20230728 083532.320 ERROR            PET000 /glade/derecho/scratch/csgteam/temp/spack/derecho/23.06/builds/spack-stage-esmf-8.5.0-wadvsguui6ysezcdnhhnrdqkh7zigbvm/spack-src/src/Infrastructure/Trace/src/ESMCI_Trace.C:1258 ESMCI::TraceClose() Wrong argument specified  - Internal subroutine call returned Error
@jedwards4b jedwards4b self-assigned this Jul 28, 2023
@jedwards4b jedwards4b added the bug Something isn't working label Jul 28, 2023
@jedwards4b
Copy link
Collaborator Author

If I comment out the call at med.F90: 1832 the X case will run to completion - is this an adequate solution?

@jedwards4b
Copy link
Collaborator Author

Opening a PR with a more exact solution.

@mvertens
Copy link
Collaborator

@jedwards4b - this solution is too restrictive and its not clear what the impact is on other compsets. We don't want the mediator to really be aware of what type of compsets of components we are using on the other side. We need to come up with another solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants