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

cesm1

  1. A

    CESM1.2.z - For both CLM4.0 and CLM4.5, crop GDD is incorrect for the first ~20 years.

    Affected Releases - CESM1.2.zFixed in upcoming CESM1.2.2 release.(Bugzilla 1815) - Details and a fix are explained in the bugzilla report.
  2. A

    CESM1.2.z - The population density is set to 1850 for 2000_control namelist use-cases.

    Affected Releases - CESM1.2.z (Bugzilla 1838) This is true in the cesm1_2_0 release as well as the latest CLM. population density is set to 1850 for 2000_control namelist use-cases. This is due to a bad setting in the following directories... lnd/clm/bld/namelist_files/use_cases...
  3. A

    CESM1.2.z - irrigated soybean not treated same as rainfed soybean

    Affected Releases - CESM1.2.z(Bugzilla 1867) In modifying the clm to introduce tropical crop pfts, I have come across the following problem:The if-statements in biogeochem/CNAllocationMod.F90 and biogeochem/CNNDynamicsMod.F90 that check for soybean do not include the option for irrigated...
  4. A

    CESM1.1.z - The interpinic tool does not work properly for input files with multiple glacier elevation classes.

    Affected releases - CESM1.1.z (Bugzilla 1447) Currently, interpinic doesn't use any metadata about the glc_mec columns -- e.g., their topographic height. Details regarding the problem and proposed fixes are included in the bugzilla report.
  5. A

    CESM1.1.z - Problem setting a user defined initial condition file for a hybrid or branch case.

    Affected Releases - CESM1.1.zFixed in CESM1.2.z(Bugzilla 1625) We've recognized a problem in having the user override the setting of finidat when RUN_TYPE=hybrid/branch. In these cases if you set finidat in your user_nl_clm, it will contradict the value coming in from clm.buildnml.csh -- so...
  6. A

    CESM1.1.z and CESM1.2.z - Restarts can only happen on year boundaries.

    Affected Releases - CESM1.1.z and CESM1.2.z(Bugzilla 1611) Some data related to the running averages of climate variables (and maybe other data) are not written to the restart file. Thus restarts that happen mid-year do not restart properly.The workaround is to ensure that any _GLC compset runs...
  7. A

    CESM1.1.z - Limitations with different coupling frequencies for different models.

    Affected Releases - CESM1.1.zFixed in CESM1.2.1(Bugzilla 1740) CESM allows different coupling frequencies for different models. However, there are some limitations. The coupling frequencies are set via the env_run.xml variables *_NCPL. Generally, the atmosphere, land, and ice model coupling...
  8. A

    CESM1.2.z - Problem running with "too many files" for datm for over 83 years.

    Affected Releases - CESM1.2.z(Bugzilla 1339) - Problem running with "too many files" for datm for over 83 years.
  9. A

    CESM1.2.z - Driver needs a different list hardcoded in for hist_a2x3hr_flds

    Affected releases - CESM1.2.z(Bugzilla 1733) -The driver needs a different list of fields so that a case can be run and then use the resulting forcing to drive CLM. The Bugzilla report has more details.
  10. A

    CESM1.1.z - Running IAF compsets (CIAF, DIAF, GIAF) on non-NCAR machines.

    Affected Releases: CESM1.1.z The following instructions assume you will be starting from CESM1.1.zBefore you can set up and run your IAF case on a machine other than a NCAR machine, you will need to first download the forcing datasets onto your own disk location, then make modifications to the...
  11. A

    CESM1.1.z Incompatible initial conditions with BG1850CN at f09 resolution for both CLM and CISM.

    Affected Releases: CESM1.1.zBG1850CN at f09 resolution currently has initial conditions that are incompatible with the run configuration, for both CLM and CISM. Thus, this compset-resolution combination should only be used if you provide your own initial conditions for CLM and CISM.This is...
  12. A

    CESM1.1.z - Problems using compsets FSTRATMAM3 and FSTRATMAM7

    Affected releases: CESM1.1.z(Bugzilla 1645) Problem using compsets FSTRATMAM3 and FSTRATMAM7.The entry CICE_NAMELIST_OPTS in the env_run.xml file should have value cam5=.true. in cesm1_1, cesm1_1_1, and cesm1_2 beta01 through beta03. It does not. This results in an incorrect cice albedo setting...
  13. A

    CESM1.2.1 Spun-up initial conditions do not exist for new ecosystem module

    Affected Releases: CESM1.2.1(Bugzilla 1880)The POP ecosystem module used in CESM 1.2.z and later is significantly different from the module available in 1.1.z and earlier. At this time, spun-up initial conditions have not been generated so the following compsets need to be started from a...
  14. A

    Generating Mapping Files in CESM 1.2 - share librariers error (libmpich.so.3)

    Hello, I'm currently trying to utilize an interactive login on Yellowstone to run some mapping tools built into CESM 1.2.  However, I seem to be running into an error where the shared libraries aren't loading (libmpich.so.3). I run the following command to enter interactive mode: bsub -Is -q...
  15. S

    ldomain in CESM1.1

    Hi! I have a problem with the land compenent in CESM1.1. I would appreciate if I could get some insight on how to deal with this. I need to specify ldomain from an existing input nc file I have from an older case run with cesm1.0.3, which I did the following way: ./xmlchange -file env_run.xml...
  16. C

    runoff_to_ocn

    Dear CESM developers: Is there a guideline for how to compile runoff_to_ocn under cesm1_1_1/mapping/gen_mapping_files? The default set up is done for bluefire. I was wondering if I could use some helps. Any comments would be very much appreciated.
Top