LIS run freezes without any known problem #1780
Unanswered
jinwoongyoo
asked this question in
Q&A
Replies: 1 comment 1 reply
|
Hi @jinwoongyoo Sorry you are having this trouble. We don't usually see this. If you point me to your job script on Discover, I'd be glad to take a look. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I often encountered LIS run stops right after being allocated on Discover.
I have to resubmit the job often multiple times to make the LIS run get over the spot.
If it passes the point, then LIS runs fine.
Below is the lislog section that the LIS run stops.
[INFO] Reading mask from lis_input.d01.nc
[INFO] Saving global land mask...
[INFO] Reading landcover map from lis_input.d01.nc
[INFO] Reading surfacetype map from lis_input.d01.nc
[INFO] Reading mask from lis_input.d02.nc
[INFO] Saving global land mask...
[INFO] Reading landcover map from lis_input.d02.nc
[INFO] Reading surfacetype map from lis_input.d02.nc
[INFO] Finished reading landmask and landcover data
[INFO] Reading elevation map from lis_input.d01.nc
[INFO] Reading slope map from lis_input.d01.nc
[INFO] Reading aspect map from lis_input.d01.nc
[INFO] Reading elevation map from lis_input.d02.nc
[INFO] Reading slope map from lis_input.d02.nc
[INFO] Reading aspect map from lis_input.d02.nc
[INFO] Reading soiltexture map from lis_input.d01.nc
[INFO] Reading soiltexture map from lis_input.d02.nc
[INFO] Landmask LAND points = 0
[INFO] Total number of surface tiles 0
[INFO] Total number of tiles for LSM 0
[INFO] Total number of grid points 0
I wonder if the LIS team is aware of the issue by any chance?
Since I can make a LIS run going after several times of push, it is not a serious issue but I hope someone can figure out the issue and make it better.
Thank you.
Jinwoong
All reactions