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

Point-scale simulation with CTSM5.3

johanna_teresa

Johanna Malle
New Member
Dear all,

I am currently trying to start using the new CLM version, my code version is ctsm5.3.021 which I have recently ported to our HPC. I am trying to re-create point-scale and regional simulations which have been successful with a previous version, as I would like to use the hillslope hydrology configuration in the future.

I have updated my surface datasets to match the new requirements, and I understand that the previously required domain files are not necessary anymore. I am using the user_nl_datm_streams to define my forcing data. As suggested here, I have set CLM_USRDAT.UNSET:meshfile = none and not specified mesh files in env_run.xml.

The model builds successfully, but then I get this error: "ERROR: (dshr_mod:dshr_mesh_init) ERROR: model_meshfile UNSET does not exist.", which I guessed had to do with the fact that I left ATM_DOMAIN_MESH at UNSET. I tried using ./mesh_maker to create a mesh, but there I get the notification that this is not required for a single-point case.

Any help with this would be much appreciated. I have attached my user_nl_datm_streams file, as well as the log files and my env_run.xml file.

Thanks a lot and best wishes,
Johanna

./create_newcase --case "${CASEDIR}" --compiler intel --compset I1PtClm50SpRs --res CLM_USRDAT --mach eiger --driver nuopc --mpilib mpich --pecount 128 --run-unsupported
./xmlchange COMP_INTERFACE=nuopc
./case.setup
./xmlchange ATM_NCPL=24
./xmlchange RUN_STARTDATE=2013-01-01
./xmlchange STOP_OPTION=nyears
./xmlchange STOP_N=6
./xmlchange DATM_YR_ALIGN=2015
./xmlchange DATM_YR_START=2015
./xmlchange DATM_YR_END=2019
./case.build
./case.submit
 

Attachments

  • ctsm_5_3_mesh_problem.zip
    40.2 KB · Views: 2

johanna_teresa

Johanna Malle
New Member
Dear Keith,

Thanks a lot for getting back to me.

I tried setting PTS_LAT and PTS_LON, but I couldn't properly see if this solved my initial issue because it revealed a different problem: I had previously set --pecount to 128, but as soon as I set PTS_LAT and PTS_LON this was not accepted anymore. After setting pe count to 1, (either via setting --pecount during the ./case.create step or ./xmlchange NTASK=1) the model would still bild, but fail upon submitting the case. I get 128 PET*.ESMF_LogFiles in my run directory, which I have never seen when running gridded simulations. I copied one of them below. Do you happen to know what the cause for this could be?

Thanks again,
Johanna


Output from PET001.ESMF_LogFile:
20250217 182412.371 ERROR PET001 ESMF_VM.F90:5391 ESMF_VMGetDefault() Value cannot be a NULL pointer - Not a valid pointer to VM
20250217 182412.372 ERROR PET001 esm.F90:1281 Value cannot be a NULL pointer - Passing error in return code
20250217 182412.372 ERROR PET001 esm.F90:706 Value cannot be a NULL pointer - Passing error in return code
20250217 182412.372 ERROR PET001 esm.F90:1139 Value cannot be a NULL pointer - Passing error in return code
20250217 182412.372 ERROR PET001 esm.F90:203 Value cannot be a NULL pointer - Passing error in return code
20250217 182412.372 ERROR PET001 ESM0001:src/addon/NUOPC/src/NUOPC_Driver.F90:797 Value cannot be a NULL pointer - Passing error in return code
20250217 182412.372 ERROR PET001 ensemble:src/addon/NUOPC/src/NUOPC_Driver.F90:2918 Value cannot be a NULL pointer - Phase 'IPDv02p1' Initialize for modelComp 1: ESM0001 did not return ESMF_SUCCESS
20250217 182412.372 ERROR PET001 ensemble:src/addon/NUOPC/src/NUOPC_Driver.F90:1345 Value cannot be a NULL pointer - Passing error in return code
20250217 182412.372 ERROR PET001 ensemble:src/addon/NUOPC/src/NUOPC_Driver.F90:486 Value cannot be a NULL pointer - Passing error in return code
20250217 182412.372 ERROR PET001 esmApp.F90:134 Value cannot be a NULL pointer - Passing error in return code
20250217 182412.372 INFO PET001 Finalizing ESMF with endflag==ESMF_END_ABORT


Output from cesm.log:
(t_initf) Read in prof_inparm namelist from: drv_in
(t_initf) Using profile_disable= F
(t_initf) profile_timer= 4
(t_initf) profile_depth_limit= 4
(t_initf) profile_detail_limit= 2
(t_initf) profile_barrier= F
(t_initf) profile_outpe_num= 1
(t_initf) profile_outpe_stride= 0
(t_initf) profile_single_file= F
(t_initf) profile_global_stats= T
(t_initf) profile_ovhd_measurement= F
(t_initf) profile_add_detail= F
(t_initf) profile_papi_enable= F
 
Vote Upvote 0 Downvote

johanna_teresa

Johanna Malle
New Member
This resulted in the following problem during the ./case.build step:
'ERROR: /users/jmalle/CTSM/libraries/mpi-serial/missing: line 81: aclocal-1.16: command not found'.

I am guessing this is because we only have Automake 1.15 rather than 1.16 on our system. I will look into updating it and let you know if it's successful. In the meantime I will also try and generate a mesh for the single point location following a suggestion from Sean Swenson.

Thanks a lot!
 
Vote Upvote 0 Downvote
Top