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

Building issue in gamma version of CESM

csp

CSP
Member
Hello all,
I am trying many versions of CESM but unfortunately not been able to run a given tutorial case:
Code:
./create_newcase --case $USER/cases/b.e20.B1850.f19_g17.test --compset B1850 --res f19_g17
thus, now trying the brand new Beta version still I am unable to run this case, I am getting the following error while using the
Code:
./case.build
command:

Code:
Building case in directory /home/csp/my_cesm_sandbox_beta/cime/scripts/csp/cases/b.e20.B1850.f19_g17.test
sharedlib_only is False
model_only is False
Generating component namelists as part of build
  2022-09-26 16:41:57 atm 
Create namelist for component cam
   Calling /home/csp/my_cesm_sandbox_beta/components/cam//cime_config/buildnml
     ...calling cam buildcpp to set build time options
CAM namelist copy: file1 /home/csp/my_cesm_sandbox_beta/cime/scripts/csp/cases/b.e20.B1850.f19_g17.test/Buildconf/camconf/atm_in file2 /home/csp/OUTPUT/CESM/scratch/b.e20.B1850.f19_g17.test/run/atm_in 
  2022-09-26 16:41:58 lnd 
Create namelist for component clm
   Calling /home/csp/my_cesm_sandbox_beta/components/clm//cime_config/buildnml
  2022-09-26 16:41:58 ice 
Create namelist for component cice
   Calling /home/csp/my_cesm_sandbox_beta/components/cice//cime_config/buildnml
RUN: /home/csp/my_cesm_sandbox_beta/components/cice/bld/generate_cice_decomp.pl -ccsmroot /home/csp/my_cesm_sandbox_beta -res gx1v7 -nx 320 -ny 384 -nproc 8 -thrds 1 -output all 
FROM: /home/csp/my_cesm_sandbox_beta/cime/scripts/csp/cases/b.e20.B1850.f19_g17.test
  output: 320 384 40 48 8 sectrobin square-ice

  2022-09-26 16:41:58 ocn 
Create namelist for component pop
   Calling /home/csp/my_cesm_sandbox_beta/components/pop//cime_config/buildnml
     ... buildnml: calling pop buildcpp to set build time options
  2022-09-26 16:41:58 rof 
Create namelist for component mosart
   Calling /home/csp/my_cesm_sandbox_beta/components/mosart//cime_config/buildnml
File not found: frivinp_rtm = /home/csp/OUTPUT/CESM/cesm-inputdata/rof/mosart/MOSART_routing_Global_0.5x0.5_c170601.nc, will attempt to download in check_input_data phase
  2022-09-26 16:41:58 glc 
Create namelist for component cism
   Calling /home/csp/my_cesm_sandbox_beta/components/cism//cime_config/buildnml
File not found: cisminputfile = /home/csp/OUTPUT/CESM/cesm-inputdata/glc/cism/Greenland/greenland_4km_epsg3413_c171126.nc, will attempt to download in check_input_data phase
  2022-09-26 16:41:58 wav 
Create namelist for component ww
   Calling /home/csp/my_cesm_sandbox_beta/components/ww3//cime_config/buildnml
File not found: prestage_wind = /home/csp/OUTPUT/CESM/cesm-inputdata/wav/ww3/core2_G4_wns_30min_20000601_to_05.nc, will attempt to download in check_input_data phase
File not found: prestage_mod_def = /home/csp/OUTPUT/CESM/cesm-inputdata/wav/ww3/G4L1.mod_def.ww3.121031, will attempt to download in check_input_data phase
File not found: initfile = /home/csp/OUTPUT/CESM/cesm-inputdata/wav/ww3/restart.ww3.init.seed, will attempt to download in check_input_data phase
  2022-09-26 16:41:58 esp 
Create namelist for component sesp
   Calling /home/csp/my_cesm_sandbox_beta/cime/CIME/non_py/src/components/stub_comps_nuopc/sesp/cime_config/buildnml
  2022-09-26 16:41:58 cpl 
Create namelist for component drv
   Calling /home/csp/my_cesm_sandbox_beta/components/cmeps/cime_config/buildnml
ERROR: ESMFMKFILE not found None

Could anyone please comment/suggest anything in this regard, it will be a great help, thanks in advance.
 

katec

CSEG and Liaisons
Staff member
There's a similar thread with possible solutions in the discussion boards already. Check this one out and see if it helps:
 

csp

CSP
Member
Hi @katec
Many thanks for your reply and help, but even after including those lines in config_compilers.xml, I am still getting the errors, now my config_compilers.xml file looks like this:
Code:
<config_compilers version="2.0">
<!--  customize these fields as appropriate for your
        system. Examples are prodived for Mac OS X systems with
        homebrew and macports.  -->
        
  <environment_variables comp_interface="nuopc">
    <env name="ESMFMKFILE">/Users/sacks/ESMF/esmf8.2.0b18/lib/libO/Darwin.gfortranclang.64.mpich3.default/esmf.mk</env>
  </environment_variables>        
<compiler COMPILER="intel" MACH="csp">
<!--  homebrew  -->
<CPPDEFS>
<append>-DFORTRANUNDERSCORE -DNO_R16</append>
</CPPDEFS>
<LDFLAGS>
<append compile_threaded="TRUE"> -fopenmp</append>
</LDFLAGS>
<!--  brew install gcc without-multilib cmake mpich hdf5 enable-fortran netcdf enable-fortran  -->
<SFC> ifort </SFC>
<SCC> icc </SCC>
<SCXX> icpc </SCXX>
<MPIFC> mpiifort </MPIFC>
<MPICC> mpiicc </MPICC>
<MPICXX> mpiicpc</MPICXX>
<CXX_LINKER>FORTRAN</CXX_LINKER>
<SUPPORTS_CXX>TRUE</SUPPORTS_CXX>
<NETCDF_PATH>/usr/local/netcdf</NETCDF_PATH>
<SLIBS>
<append>$(shell $(NETCDF_PATH)/bin/nf-config --flibs)</append>
</SLIBS>
</compiler>
</config_compilers>
Any further comment would be highly appreciated, thanks in advance.
 

jedwards

CSEG and Liaisons
Staff member
Did you install esmf into a path /Users/sacks/ESMF/esmf8.2.0b18/lib/libO/Darwin.gfortranclang.64.mpich3.default/esmf.mk
or did you juse cut and paste the example?

Did you try running any tests such as scripts_regression_tests.py before you tried the tutorial example?
 
  • Like
Reactions: csp

csp

CSP
Member
Hello, @jedwards,
Many thanks for your reply, I haven't installed esmf in my system, could you please help how to find if it is installed or not, if not then would be very kind if you could please help me in installing the esmf.
Did you try running any tests such as scripts_regression_tests.py before you tried the tutorial example?
I guess this is a good idea to check these issues, where it is located? Does this need to be run after the build of the case? I assume this would *regressively* check the ability of the script to run in a system?
 
Top