Error message when using GIAF_JRA compset

ynkuo

Yan-Ning Kuo
New Member
Hi all,

I'm running the GIAF_JRA compset. However, it alsways turns out to be stopped no more than 2 minutes after I submitted it and the cesm.log file shows the error message as follows:

MCT::m_AttrVectComms::GSM_scatter_: myID = 0. Invalid input, GSMap%gsize = 1036800, lsize(iV) = 64800
shr_mct_sMatReaddnc: Error on scatter of areasrc0
000.MCT(MPEU)::die.: from shr_mct_sMatReaddnc()

Is anyone encountering similar problems and how did you fix it? Thanks!

Best,
Yan-Ning
 
Hi kuo,

Thanks for your advice.
I used f09_g17 resolution and it failed.
I changed it to TL319_g17 as your advice and it runs successfully.

I appreciate your response.

Best,
Won-Il
 

ucas_qs

qiushi Zhang
Member
Hi kuo,

Thanks for your advice.
I used f09_g17 resolution and it failed.
I changed it to TL319_g17 as your advice and it runs successfully.

I appreciate your response.

Best,
Won-Il
Hi Lim,

Yes I figured this out.

I found a ppt (http://www.cesm.ucar.edu/events/workshops/ws.2018/presentations/omwg/kim.pdf) and saw they run GIAF_JRA with the code as follows:
./create_newcase --case $CASENAME --compset GIAF_JRA --res TL319_g17 --run-unsupported

I used T62_g16 before and failed. After I changes my resolution to TL319_g17, it ran successfully. Hope this discovery also help you.

Best,
Yan-Ning
Hello kuo and Lim,
I want to run the compset GIAF_JRA (the res is TL319_g17), but I find it takes a lot of computing resources and time to run it from the default initial field due to spin-up. Do you have restart fields for this case, so that I can run it in "hybrid" or "branch" type to avoid having to spin up for a long time?

Best,
Qiushi
 
Back
Top