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

FGEOS_C5SMAM_L40CN compilation error

Y

yaoxian_huang@yale_edu

New Member
Hi, I would like to run a compset FGEOS_C5SMAM_L40CN using CESM 1.2.2 CAM5.3-Chem. There is no problem for me to configure, setup and compile this compset at a resolution of f19_f19, however, when I changed the resolution to f09_f09, compilation errors occured during the cesm_setup. Is it because the input data,e.g. GEOS5 and other dataset, has not been uploaded to the CESM server? Or other settings that I need to revise? Thank you for providing a hint. I am attaching the compilation error messages as follows.
Creating Macros file for bulldog/lustre/home/client/apps/geo/Sources/Applications/CESM/1.2.2/scripts/ccsm_utils/Machines/config_compilers.xml intel bulldogSetting MPI_PATH from EnvironmentCreating batch script CAM_CRL.run Locking file env_mach_pes.xml Creating user_nl_xxx files for components and cplRunning preview_namelist script  infile is /home/geo/unger/yh463/CAM_CRL/Buildconf/cplconf/cesm_namelist CAM build-namelist - ERROR: No default value found for ncdatauser defined attributes:key=ic_md  val=20050101Died at /lustre/home/client/apps/geo/Sources/Applications/CESM/1.2.2/models/atm/cam/bld/build-namelist line 3384.ERROR: cam.buildnml.csh failedERROR: /lustre/home/client/geo/unger/yh463/CAM_CRL/preview_namelists failed: 25344
 
Y

yaoxian_huang@yale_edu

New Member
Update from this post: I found a way to solve this problem by adding the ncdata path in user_nl_cam as &cam_inparmncdata = "FILE LOCATION/FILENAME"/Then use ./preview_namelists to inform the ncdata routine. By doing this, ./cesm_setup can be executed without errors. 
 
Y

yaoxian_huang@yale_edu

New Member
Update from this post: I found a way to solve this problem by adding the ncdata path in user_nl_cam as &cam_inparmncdata = "FILE LOCATION/FILENAME"/Then use ./preview_namelists to inform the ncdata routine. By doing this, ./cesm_setup can be executed without errors. 
 
K

krc139@marine_rutgers_edu

New Member
Hi,I am running into a similar problem/same compile error with compset F1850C5. I compiled resolution T31_g37 no problem but I can't compile a higher resolution T85_g16. I don't follow how you set ncdata (i.e. where exactly was that file located?). Can you please explain how you found this to set in user_nl_cam?Thanks,Kyle
 
K

krc139@marine_rutgers_edu

New Member
Hi,I am running into a similar problem/same compile error with compset F1850C5. I compiled resolution T31_g37 no problem but I can't compile a higher resolution T85_g16. I don't follow how you set ncdata (i.e. where exactly was that file located?). Can you please explain how you found this to set in user_nl_cam?Thanks,Kyle
 
J

jedwards

CSEG and Liaisons
Staff member
Unless you have a compeling reason to use the Eulerian dycore you should try f19_f19 or f09_f09 instead of T85.
 
J

jedwards

CSEG and Liaisons
Staff member
Unless you have a compeling reason to use the Eulerian dycore you should try f19_f19 or f09_f09 instead of T85.
 
K

krc139@marine_rutgers_edu

New Member
Thank you for this helpful suggestion. The f19_f19 resolution is exactly what I want for the atmosphere/land grid. However, I am encountering a run problem for f19_f19, I am attaching the cesm.log for a run with 64 processors/cores. I have two questions if you could please help: 1) for the ocean, what is the difference between f19 and e.g. g16? I am running F compsets, and I am only interested in modifying the prescribed SSTs-could g16 work instead of f19 (i.e. f19_g16)? I did not encounter problems running T31_g37, so I am wondering if, for my purposes, I could just run f19_g16 to increase the atmosphere/land grid resolution and maybe this will avoid my current problems. 2) for the f19_f19, could my errors be related to the number of processors? I tried first with 28 processors and the log contained no information, I then tried with 64 processors and the model seemed to make it further but still crashed. Is there a minimum number or a divisible/combination number needed for an f19_f19 run?Thank you for your help,Kyle
 
K

krc139@marine_rutgers_edu

New Member
Thank you for this helpful suggestion. The f19_f19 resolution is exactly what I want for the atmosphere/land grid. However, I am encountering a run problem for f19_f19, I am attaching the cesm.log for a run with 64 processors/cores. I have two questions if you could please help: 1) for the ocean, what is the difference between f19 and e.g. g16? I am running F compsets, and I am only interested in modifying the prescribed SSTs-could g16 work instead of f19 (i.e. f19_g16)? I did not encounter problems running T31_g37, so I am wondering if, for my purposes, I could just run f19_g16 to increase the atmosphere/land grid resolution and maybe this will avoid my current problems. 2) for the f19_f19, could my errors be related to the number of processors? I tried first with 28 processors and the log contained no information, I then tried with 64 processors and the model seemed to make it further but still crashed. Is there a minimum number or a divisible/combination number needed for an f19_f19 run?Thank you for your help,Kyle
 
J

jedwards

CSEG and Liaisons
Staff member
You didn't attach any logs.  The model at f19_f19 should run fine on 64 processors and probably aslo on 28 processors. The difference between f19_f19 and f19_g16 for an F compset is just when the data is interpolated from g16 to f19.  The f19_f19 case is a little more effiecient and should be fine for your case. 
 
J

jedwards

CSEG and Liaisons
Staff member
You didn't attach any logs.  The model at f19_f19 should run fine on 64 processors and probably aslo on 28 processors. The difference between f19_f19 and f19_g16 for an F compset is just when the data is interpolated from g16 to f19.  The f19_f19 case is a little more effiecient and should be fine for your case. 
 
J

jedwards

CSEG and Liaisons
Staff member
Here is the error:
FLDLST: DTH in fexcl( 34 ) not found

Do you have a user_nl_cam with an fexcl variable? If so remove that variable and try again.
 
J

jedwards

CSEG and Liaisons
Staff member
Here is the error:
FLDLST: DTH in fexcl( 34 ) not found

Do you have a user_nl_cam with an fexcl variable? If so remove that variable and try again.
 
K

krc139@marine_rutgers_edu

New Member
Brilliant! I did have many fexcl variables named in the user_nl_cam. I removed those, and it runs-but ONLY on 64 processors. I previously tried a run with no fexcl variables but with 28 processors and it crashed immediately so I did not realize the fexcl was the issue. Any idea on how to find out what the minimum number of processors required is, or better yet, how to set the number of processors? Looks like this may be done in the run script, but I'm not sure...Thanks,Kyle
 
K

krc139@marine_rutgers_edu

New Member
Brilliant! I did have many fexcl variables named in the user_nl_cam. I removed those, and it runs-but ONLY on 64 processors. I previously tried a run with no fexcl variables but with 28 processors and it crashed immediately so I did not realize the fexcl was the issue. Any idea on how to find out what the minimum number of processors required is, or better yet, how to set the number of processors? Looks like this may be done in the run script, but I'm not sure...Thanks,Kyle
 
You must log in or register to reply here.
Top