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

ERROR in /home01/g151a06/CESM2.1.3/components/clm/src/main/ncdio_pio.F90.in at line 368

Status
Not open for further replies.
Previously, I ran a transient simulation from 2000 to 2150 with changing CO2 emissions datasets (compset:

2000_CAM60_CLM50%BGC-CROP-CMIP6DECK_CICE%CMIP6_POP2%ECO%ABIO-DIC_MOSART_CISM2%NOEVOLVE_WW3_BGC%BPRP)

I want to run new experiment with changing the landunit suddenly in 2025.
I ran the experiment with branch run with the restart file of 2025 from previous run. I just changed the landunit in fsurdata. (set use_init_interp = .true.)

However, I got the following error.

check_dim ERROR: mismatch of input dimension 50887 with expected value
50923 for variable landunit
ERROR in /home01/g151a06/CESM2.1.3/components/clm/src/main/ncdio_pio.F90.in at line 368
Did you mean to set use_init_interp = .true. in user_nl_clm?
(Setting use_init_interp = .true. is needed when doing a
transient run using an initial conditions file from a non-transient run,
or a non-transient run using an initial conditions file from a transient run,
or when running a resolution or configuration that differs from the initial conditions
.)

I have attached the lnd log file below.
Is this because the information regarding landunit in the restart file and fsurdata don't match?
I would be grateful if you could help me on how to solve it.
 

Attachments

  • lnd.log.13737765.pbs.231026-141500.txt
    141.6 KB · Views: 2
If so, would it be okay to just replace the land restart file after running the model for a just 1 month with hybrid run?
Also, if possible, which variables should I replace?

Thank you in advance.
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
Right, you can't do a branch run if you change fsurdat. I think a hybrid would work.
 
Right, you can't do a branch run if you change fsurdat. I think a hybrid would work.
Thanks for your answer.

Instead of running hybrid run for the entire remaining period, would it be okay to just replace the lnd restart file obtained through hybrid run and run a branch again?
I am asking this question because I am concerned that if the experiment continues with hybrid run, there will be a difference in the experiment in addition to the effect caused by the changes in landunit since it is a fully coupled experiment.
 

slevis

Moderator
Staff member
You could try that. It may work.

If not, just make sure that the hybrid case is as similar to the branch as you can make it, pointing to restart files for all the components. If you do that, then any difference introduced to the experiment should be negligible.
 
You could try that. It may work.

If not, just make sure that the hybrid case is as similar to the branch as you can make it, pointing to restart files for all the components. If you do that, then any difference introduced to the experiment should be negligible.
Thank you for your comment.
I ran a hybrid run with the original restart file for one day, and then did an experiment by replacing only clm2 restart files from hybrid run.
Even though I did a fully-coupled run, offline run was performed making only output file from land component.

Could you give me some advices?
I have attached the atm, cesm and lnd log files below.
Thank you in advance.
 

Attachments

  • log.zip
    603.8 KB · Views: 1

oleson

Keith Oleson
CSEG and Liaisons
Staff member
There is a traceback in the cesm log indicating the line numbers of the modules where the model crashed. You could try printing out the values of variables used in those lines. But there seem to be multiple places where the model crashed and it may be difficult/time-consuming to find the problem that way.
So you might try a different method of starting your experiment, e.g., a hybrid run with use_init_interp=.true.
 
There is a traceback in the cesm log indicating the line numbers of the modules where the model crashed. You could try printing out the values of variables used in those lines. But there seem to be multiple places where the model crashed and it may be difficult/time-consuming to find the problem that way.
So you might try a different method of starting your experiment, e.g., a hybrid run with use_init_interp=.true.
Thank you for your reply. I will try a hybrid run!
 
Status
Not open for further replies.
Top