-
Notifications
You must be signed in to change notification settings - Fork 27
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
Stretched Grid Runs Failing with "Error calling DO_WETDEP" #402
Comments
Thanks for writing @anasali1999. We were recently informed about a bug in GCPy cubed-sphere regridding. We will bring this into the development branch shortly but in the meantime you may want to apply the fix in geoschem/gcpy#311 and then create a new stretched-grid restart file. |
HI @anasali1999, thanks for reaching out. Have you validated that your run using a stretch factor of 2.0 compares well with a uniform global run? If yes, I think we can rule out problems with generation of the restart file. I wonder if there is an instability running at higher grid resolution at the particular region of interest. Here are a few things to try:
|
Hello everyone, thank you for the suggestions. Sorry I seem to have closed this issue earlier by accident. @lizziel I reduced all the time steps in setCommonRunSettings.sh by half, this lead to the same DO_WETDEP error. I then returned the time steps to normal and turned off wet deposition; this time the run failed with "Error calling DO_CONVECTION". Here are all the files for the turned-off wet dep run: wet dep off files.zip I have yet to inspect the restart files, but I will report back once I compare the working unstretched, working 2.0 factor stretched, and the failing stretched files. @yantosca This fix looks easy enough for me to try, I will report back once I try it. |
Hello @yantosca I applied the changes to GCPy and generated a new restart file, but the run failed again with the same DO_WETDEP error. |
Hi @anasali1999, have you looked through the GEOS-Chem debugging guide? It has a specific section on the issue you are encountering in DO_WETDEP. See if there are any suggestions on that page (found here) that you have not yet tried. |
Hello, I have seen that section of the guide but I've been following some other leads in the meantime. I'll try the debugging strategy shown in the guide |
Hello, I am closing this issue, my GCHP setup overall was incorrect. |
Name and Institution (Required)
Name: S. M. Anas Ali (preferred name Anas)
Institution: University of Toronto, Department of Physics
Confirm you have reviewed the following documentation
Description of your issue or question
Please provide as much detail as possible. Always include the GCHP version number and any relevant configuration and log files.
I am working with GCHP 14.1.1 to perform stretched-grid runs. I am regridding a C48 cube-sphere restart-file to stretched-grid restart-files with different stretch factors. I was able to regrid the file with a stretch factor of 2.0 and successfully run the model, but all other model runs have failed within 6-11 minutes.
The failed runs all have "Error calling DO_WETDEP" in the end of their slurm outputs. I have no idea why my stretch factor of 2.0 worked, but the other runs did not, as I used the same regridding commands and the same original restart-file. Looking at the files with
ncdump -h filename
shows the target lat, target lon, and stretch factor correctly for all the regridded restart-files. I even used the original restart-file to perform a regular run, with no errors.Here are the relevant files:
do_wetdep_error.zip
Here is an example of my regridding commands:
Additional note: when re-compiling (with "make -j" in my build directory), I saw the following output with MECH as fullchem and USE_REAL8 as the only ON setting:
Below are some of the relevant portions of the slurm output, log files, and setCommonRunSettings. Full files are attached as well. Some typical slurm output for a failed run:
Some gchp.log.new output:
Relevant sections of my setCommonRunSettings.sh
While I wait for support, I will try recompiling and running the model in a fresh run directory. Thank you everyone!
The text was updated successfully, but these errors were encountered: