Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

too many input landuse types

munez

New member
Hi,
I kept seeing this error of "too many input landuse types" and "MPAS core_physics abort" when running MPAS-A atmosphere_model. I tried with both 8.2.2 and 8.1.0. What might be causing this consistent issue? Attached please also find my namelist used for the running.

----------------------------------------------------------------------

ERROR:
ERROR: ------------------------------ FATAL CALLED ------------------------------
ERROR: Warning: too many input landuse types
CRITICAL ERROR: MPAS core_physics abort
Logging complete. Closing file at 2025/02/13 00:06:42
 

Attachments

  • namelist.atmosphere.txt
    1.3 KB · Views: 1
Would you please upload the following files for me to take a look:
(1) namelist.init_atmopsher, and streams.init_atmopshere
(2) namelist.atmosphere and streams.atmosphere
(3) please clarify what data you used to produce initial condition for this case?
Based on your namelist, I suppose this is a global MPAS run. Please let me know if I am wrong. Thanks.
 
Hi,
Thanks for the response!
Yes, this is a global MPAS run. A to (3), the initial condition is generated with this specific file available here, basically operational GFS 0000 forecast. Attached please find the other namelists and streams. The namelist.atmosphere can be found attached to the original thread.

Thanks again!
 

Attachments

  • namelist.init_atmosphere.IC.txt
    1.4 KB · Views: 2
  • namelist.init_atmosphere.STATIC.txt
    1.4 KB · Views: 2
  • streams.atmosphere.txt
    1.6 KB · Views: 1
  • streams.init_atmosphere.IC.txt
    947 bytes · Views: 1
  • streams.init_atmosphere.STATIC.txt
    931 bytes · Views: 1
Your namelist and stream files look fine to me.
Are you running this case in Derecho? if so, would you please point me to the path where this case is located? Thanks!
 
After some trial and errors, it turns out the reason was that I referenced the newer version of static geog data, which the static init step didn't complain about. With 3.x versions of geog, the errors were gone. Thanks again for looking into it!
 
Thank you for the update.
Would you please clarify what are the "newer version of static geog data" and the "3.x versions of geog" you used for this case? Thanks.
 
Top