Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

ISSP-compset surfdata/fatmgrid lon/lat mismatch error

Chr

Christian Dold
New Member
All,

I am currently trying to set up an ISSP-compset with my own grid and under constant land use. I ran in several issues, and the case continues to fail with the following error message in the cesm.log:

surfdata/fatmgrid lon/lat mismatch error

I believe that it is connected to the transient co2 file. I attached the log and user_nl files.

As a side note, I had to do the following to get the case running:

1. direct to more maps:
./xmlchange LND2GLC_FMAPNAME="/clm5.0/inputdata/cpl/gridmaps/ne0np4CONUS.ne30x8/map_ne0CONUSne30x8_TO_gland4km_aave.190322.nc"
./xmlchange LND2GLC_SMAPNAME="/clm5.0/inputdata/cpl/gridmaps/ne0np4CONUS.ne30x8/map_ne0CONUSne30x8_TO_gland4km_blin.190322.nc"
./xmlchange GLC2LND_FMAPNAME="/clm5.0/inputdata/cpl/gridmaps/gland4km/map_gland4km_TO_fv0.9x1.25_aave.170429.nc"
./xmlchange GLC2LND_SMAPNAME="/clm5.0/inputdata/cpl/gridmaps/gland4km/map_gland4km_TO_fv0.9x1.25_aave.170429.nc"

2. create user_datm.streams.txt.presaero.SSP5-8.5 and change the file from aerosoldep_SSP5-8.5_monthly_1849-2101_UNSET.nc to aerosoldep_rcp8.5_monthly_1849-2104_0.9x1.25_c100208.nc


Thanks for your help.
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I don't see any log files or user_nl files attached?
But I think the error is saying that your lat/lons don't agree between your domain file (given by fatmlndfrc in lnd_in) and your surface dataset (given by fsurdat in lnd_in)?
 

Chr

Christian Dold
New Member
....here are the files.
 

Attachments

  • atm.log.3288403.txt.210120-125954.txt
    14.2 KB · Views: 3
  • cesm.log.3288403.210120-125954.txt
    157.9 KB · Views: 0
  • user_nl_clm.txt
    3.5 KB · Views: 4
  • user_nl_datm.txt
    1.2 KB · Views: 2
  • datm.streams.txt.CLMGSWP3v1.TPQW.txt
    1.3 KB · Views: 2
  • datm.streams.txt.co2tseries.SSP5-8.txt
    757 bytes · Views: 2
  • datm.streams.txt.presaero.SSP5-8.txt
    1.1 KB · Views: 1

Chr

Christian Dold
New Member
Ok, found it, yes, it was connected to the domain file. I'll give it a new run. Thanks for your help.
 

Chr

Christian Dold
New Member
Dear Keith Oleson,

I write you regarding the ISSP case. After your suggested fix, I ran into a new error message (cesm.log attached):

:
Writing to file XXX.cism.initial_hist.2020-01-01-00000.nc at time
0.000000000000000E+000
MCT::m_SparseMatrixPlus:: FATAL--length of vector y different from row count of sMat.Length of y = 8216 Number of rows in sMat = 55296
05F.MCT(MPEU)::die.: from MCT::m_SparseMatrixPlus::initDistributed_()
:
application called MPI_Abort(MPI_COMM_WORLD, 2) - process 35forrtl: error (78): process killed (SIGTERM)

Is this connected to the CISM submodel? If so, is there a way to circumvent the error or find a fix?

One idea was to use SGLC instead of CISM, because the glacier model is not of interest to my research. However, the standard ISSP compsets are all coupled with CISM.

Thanks for your help.
 

Attachments

  • cesm.log.3295094.210122-094323.txt
    75 KB · Views: 0
Top