-
Notifications
You must be signed in to change notification settings - Fork 170
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
Nested simulation "Do_Mixing" error #1889
Comments
@jimmielin Thank you, Haipeng! |
@laura-hyesung-yang @jimmielin: I am now testing the fix in PR #1895, this could possibly fix your issue. |
@jimmielin @yantosca #1895 seems to fix this issue. I no longer get the "Do_Mixing" error after implementing the code change in #1895. Thanks, Haipeng and Bob! |
The issue actually persists with the #1895 fix. |
This issue has been automatically marked as stale because it has not had recent activity. If there are no updates within 7 days it will be closed. You can add the "never stale" tag to prevent the Stale bot from closing this issue. |
Bumping this error to prevent it from going stale. It might not be isolated to nested-grid full-chemistry simulations as we have observed this in nested-grid aerosol-only and WRF-GC simulations as well near domain edges. There might be something that has changed in the chemistry in the past few versions to introduce this instability. |
Tagged this issue with "never stale" to preserve it |
Name: Laura Yang
Institution: Harvard University
GEOS-Chem version: v13.3.4
I'm running a 0.25 nested simulation. When I change the input.geos file to use the TURBDAY mixing scheme (Set use non-local PBL to True), I get the following error in my GC.log file:
I have boundary conditions and a 1-month spin-up file using non-local PBL mixing. I'm wondering if I should regenerate the BC and 1-month spin-up file using a full mixing scheme as well to avoid this error. When I use the non-local PBL mixing scheme in my 0.25 nested simulation, I don't encounter this error. Thank you!
The text was updated successfully, but these errors were encountered: