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

supported X case mesh resolutions #3788

Open
worleyph opened this issue Aug 21, 2020 · 0 comments
Open

supported X case mesh resolutions #3788

worleyph opened this issue Aug 21, 2020 · 0 comments

Comments

@worleyph
Copy link
Contributor

worleyph commented Aug 21, 2020

  1. This is probably a feature rather than a bug, but I was trying to find a small mesh resolution to use with an X case. @amametjanov advised that I use

    --res f19_g16 --compset X

which worked. I tried to find something smaller, trying

  --res f45_g37 --compset X
  --res ne4_oQU480 --compset X
  --res ne4_oQU240 --compset X

All three of these failed with

 (shr_mct_sMatPInitnc) Initializing SparseMatrixPlus
 (shr_mct_sMatPInitnc) SmatP mapname idmap_ignore
 (shr_mct_sMatPInitnc) SmatP maptype X
 (shr_mct_sMatReaddnc) reading mapping matrix data decomposed...
 (shr_mct_sMatReaddnc) * file name                  : idmap_ignore
  ERROR: (shr_mct_sMatReaddnc)No such file or directory

for the same shr_mct_sMatPInitnc call (7th one, whichever one it was). Is this expected? Is f19_g16 the smallest? This is not critical, but it would have been useful for a debugging exercise that I am going through at the moment.

  1. Also, the diagnostic output for shr_mct_sMatPInitnc and shr_mct_sMatReaddnc ended up int wav.log file, which looks like a bug to me. Should be ??? cpl.log, ??? e3sm.log, but probably not wav.log .
rljacob pushed a commit that referenced this issue Apr 12, 2021
…ogging"

This reverts commit 9c64b5ac2c3f33f1dfa4a070ec7d5d509647d9eb, reversing
changes made to 5cef5558c4e7bebfc8ec8f3b507e7e583e6a669c.
rljacob pushed a commit that referenced this issue Apr 21, 2021
…ogging"

This reverts commit 1922e71c1a1b71b44025b5b7b28207c3ee85a978, reversing
changes made to 92e12945e38ce8caba171d16e78df2e5b802cd93.
rljacob pushed a commit that referenced this issue Apr 21, 2021
Revert "Merge pull request #3788 from ESMCI/azamat/driver/mem-usage-logging"

This reverts commit 1922e71, reversing
changes made to 92e1294.

[ Description of the changes in this Pull Request. It should be enough
information for someone not following this development to understand.
Lines should be wrapped at about 72 characters. Please also update
the CIME documentation, if necessary, in doc/source/rst and indicate
below if you need to have the gh-pages html regenerated.]

Test suite:
Test baseline:
Test namelist changes:
Test status: [bit for bit, roundoff, climate changing]

Fixes [CIME Github issue #]

User interface changes?:

Update gh-pages html (Y/N)?:

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

No branches or pull requests

3 participants