Hi All,
I encountered a few issues regarding CTSM spinup with FATES. I use CTSM5.1.dev118 and configure my model with I2000Clm51FatesRs to run single-point simulations at high latitudes/Arctic (ranging 57-67 N). Some of the case setup information is attached and I briefly describe it below:
a) RUN_TYPE = startup and configured with -bgc fates -no-megan option;
b) data atm, active lnd with FATES, stub for all other components;
c) spinup with repeated 1991-2010 GSWP3 forcing and prescribed 2000 aerosol, ozone, and nitrogen deposition states;
d) cold start without accelerated spinup.
My first issue is that I am conducting simulations at high-latitude/arctic sites, and it took 15,000+ years to reach equilibrium due to the slow turnover time for total soil organic carbon content. Because of the file naming limitation, I ran 9,900 years and then used the hybrid mode to finish the remaining 6,000+ years. Is it reasonable to use this mode for such a long spinup run in my case? Or should I modify the file naming codes?
The second issue is utilizing the spinup results to initialize the historical transient run. I encountered an issue with unmatched current year and initial condition file, which was posted previously by another member. However, I am still unsure how to fix it for my case. The failed log (lnd.log.3460629) shows "ERROR: Current model year does not match year on initial conditions file (finidat) ... This match is a requirement when both: (a) The current run is a transient run, and (b) The initial conditions file was generated from a transient run." I suppose my spinup runs, which provide the initial conditions for my historical simulations, are not transient. I then tried to force the model bypassing this error with "check_finidat_year_consistency = .false." added in user_nl_clm. The model ran but used default cold start initial conditions rather than my spinup outputs (lnd.log.3460685). It would be very much appreciated if any comment or solution could help solve this issue.
Thank you,
Cheng-En
I encountered a few issues regarding CTSM spinup with FATES. I use CTSM5.1.dev118 and configure my model with I2000Clm51FatesRs to run single-point simulations at high latitudes/Arctic (ranging 57-67 N). Some of the case setup information is attached and I briefly describe it below:
a) RUN_TYPE = startup and configured with -bgc fates -no-megan option;
b) data atm, active lnd with FATES, stub for all other components;
c) spinup with repeated 1991-2010 GSWP3 forcing and prescribed 2000 aerosol, ozone, and nitrogen deposition states;
d) cold start without accelerated spinup.
My first issue is that I am conducting simulations at high-latitude/arctic sites, and it took 15,000+ years to reach equilibrium due to the slow turnover time for total soil organic carbon content. Because of the file naming limitation, I ran 9,900 years and then used the hybrid mode to finish the remaining 6,000+ years. Is it reasonable to use this mode for such a long spinup run in my case? Or should I modify the file naming codes?
The second issue is utilizing the spinup results to initialize the historical transient run. I encountered an issue with unmatched current year and initial condition file, which was posted previously by another member. However, I am still unsure how to fix it for my case. The failed log (lnd.log.3460629) shows "ERROR: Current model year does not match year on initial conditions file (finidat) ... This match is a requirement when both: (a) The current run is a transient run, and (b) The initial conditions file was generated from a transient run." I suppose my spinup runs, which provide the initial conditions for my historical simulations, are not transient. I then tried to force the model bypassing this error with "check_finidat_year_consistency = .false." added in user_nl_clm. The model ran but used default cold start initial conditions rather than my spinup outputs (lnd.log.3460685). It would be very much appreciated if any comment or solution could help solve this issue.
Thank you,
Cheng-En
