-
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
GCHP simulation stopped after 7 month simulation (total set time for 1 yr) #405
Comments
Let me provide additional informations: I wonder can I directly use the internal_checkpoint files that are stored in Restart directory (e.g., gcchem_internal_checkpoint.20170801_0000z.nc4), or do these files need some processing before making use of them. I presume they can be directly used, but I am failing in making direct use of them. I tested with other restart file (not the one that model generates during simulation), the model runs well, but with gcchem_internal_checkpoint.xxxx.nc4 the model is not running. I think this means the problem is on restart file. again, let me clarify: And beginning and end lines of gcchem_internal_checkpoint.xxxx.nc4 looks like: // global attributes: I hope these additional informations help more in understanding the problem. |
Thanks for writing @Hemrajbhattarai. There was a similar issue geoschem/geos-chem#318 not long ago. In that case the problem was solved by using target longitude in 0..360 coordinates when regridding a regular GCHP grid to a GCHP stretched grid. I don't know if that will solve your issue but that would be the first thing to check. |
Thanks Bob for prompt reply. My target point is around Delhi, India, so I think the lat and long on both 0 to 360 and -180 to 180 would remain the same (target lat = 28N, lon = 80E). |
Hi @Hemrajbhattarai, I think there are two separate issues. Your original post that the model ran for one month and then stopped has this error in the log file: The second issue is starting up a stretched grid run using an output restart file from the model. We have a separate report of this in issue #402 and I am looking into it. You should be able to start up a stretched grid simulation with any of the checkpoint files. There may be a bug preventing that that somehow was not reported until now. I will look into it. |
Dear @lizziel I rerun the simulation and the problem is still the same. I double-checked if I stored them in the right directory, and they seem to be ok, but the problem does exist. attached are the log files and other pieces of information. |
Thanks @Hemrajbhattarai for the update. I am going to try to reproduce the restart file issue for stretched grid. It does appear to be a bug. |
Hi @Hemrajbhattarai, this bug will be fixed in version 14.4.0. You can apply the fix manually using the update here: geoschem/MAPL#34. This does not address missing variables in the restart. Try the fix and see if it solves your problem. |
I believe any remaining issues with stretched grid are summarized in #404. If there are additional problems please create a new github issue. |
Name and Institution (Required)
Name: Hemraj Bhattarai
Institution: The Chinese University of Hong Kong
Description of your issue or question
I am running GCHP version 14.3.0
cap_restart: 20170101 000000
Run_Duration="00010000 000000"
CS_RES=48
STRETCH_GRID=ON
STRETCH_FACTOR=4.0
TARGET_LAT=28.0
TARGET_LON=80.0
The model simulation perfectly runs and gives output from 20170101 to 20170731, however, it stopped after that.
I didn't find useful information in the log file:
1514335_print_out.log.txt
1514335_error.log.txt
I also tried resubmitting the case with a new restart file that the model generates (I set Checkpoint_Freq=monthly). But the model still fails running with new error type (
1526524_error.log.txt
)
I am not sure where this problem is coming from, but I tested with a new restart file that the model generated itself, but failed to run. When I tested it, I changed cap_restart to 20170801 (since I already for 7 months), and also changed run duration to 00000500 000000.
I am looking for appropriate suggestions for debugging the issue.
Thank you.
The text was updated successfully, but these errors were encountered: