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

using restart file from existing run

Y

yingli@atmos_colostate_edu

Member
Hi,

I have successfully built and ran a test run (CESM1.2.2 version, F_AMIP_CAM5 compset, ne120_ne120 resolution). The default is start-up run, and ran for 5 days.

I would like to use the restart files from an previous exiting run done by someone else. So I create a branch run (should that be hybrid or branch?). Here are what I did:

1) cd /glade/p/cesm/releases/cesm1_2_2/scripts
./create_newcase -case $CASEDIR -res ne120_ne120 -compset F_AMIP_CAM5 -mach yellowstone

2) cd $CASEDIR
./xmlchange RUN_TYPE=branch,RUN_REFDATE=1982-09-01,RUN_REFCASE=FAMIPC5.ne120_ne120,GET_REFCASE=FALSE
./cesm_setup

3) cd /glade/scratch/$LOGNAME/$CASENAME/run/
hsi -q "cget /home/abaker/sensitivity_tests/FAMIPC5.ne120_ne120/rest/1982-09-01-00000/*"
./$CASENAME.build

4) cd $CASEDIR
./$CASENAME.submit

------------------------

-The job was exited with exit code 255.

-The last 8 lines from cesm.log.141014-133337 is

INFO: 0031-251 task 6142 exited: rc=1
INFO: 0031-251 task 6143 exited: rc=1
INFO: 0031-251 task 6148 exited: rc=1
INFO: 0031-251 task 6144 exited: rc=1
INFO: 0031-251 task 6147 exited: rc=1
INFO: 0031-251 task 6135 exited: rc=1
INFO: 0031-251 task 6136 exited: rc=1
INFO: 0031-639 Exit status from pm_respond = 0

-I've also tried create as hybrid run, and the job was exited with exit code 255 as well.

-I've also tried changing the following configuration, and it doesn't work as well, same exit code
1) In user_nl_cam:
ncdata='path to initial condition file'

2) In user_nl_clm
finidat = 'path to clm restart file'

-here is my case directory
/glade/u/home/yingli/cesm_1_2_2/runs/f.FAMIPC5.ne120_ne120.test.002

Any help would be greatly appreciated!
Ying
 
J

jedwards

CSEG and Liaisons
Staff member
  1: pio_support::pio_die:: myrank=          -1 : ERROR: nf_mod.F90:         679 :
 1: Variable not found
 1:Abort(1) on node 1 (rank 1 in comm 1140850688): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 1


The problem isn't that it can't find the restart file it's that it can't find some variable in the restart file that it's expecting to find.   Unfortunatley it's not telling us which one.   Are you sure that the model version you are trying to restart from is compatable with the version that you are trying to use?   If you want to find out which variable is causing the code to abort I can show you a Source mod to do that.
 
J

jedwards

CSEG and Liaisons
Staff member
  1: pio_support::pio_die:: myrank=          -1 : ERROR: nf_mod.F90:         679 :
 1: Variable not found
 1:Abort(1) on node 1 (rank 1 in comm 1140850688): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 1


The problem isn't that it can't find the restart file it's that it can't find some variable in the restart file that it's expecting to find.   Unfortunatley it's not telling us which one.   Are you sure that the model version you are trying to restart from is compatable with the version that you are trying to use?   If you want to find out which variable is causing the code to abort I can show you a Source mod to do that.
 
J

jedwards

CSEG and Liaisons
Staff member
  1: pio_support::pio_die:: myrank=          -1 : ERROR: nf_mod.F90:         679 :
 1: Variable not found
 1:Abort(1) on node 1 (rank 1 in comm 1140850688): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 1


The problem isn't that it can't find the restart file it's that it can't find some variable in the restart file that it's expecting to find.   Unfortunatley it's not telling us which one.   Are you sure that the model version you are trying to restart from is compatable with the version that you are trying to use?   If you want to find out which variable is causing the code to abort I can show you a Source mod to do that.
 
J

jedwards

CSEG and Liaisons
Staff member
  1: pio_support::pio_die:: myrank=          -1 : ERROR: nf_mod.F90:         679 :
 1: Variable not found
 1:Abort(1) on node 1 (rank 1 in comm 1140850688): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 1


The problem isn't that it can't find the restart file it's that it can't find some variable in the restart file that it's expecting to find.   Unfortunatley it's not telling us which one.   Are you sure that the model version you are trying to restart from is compatable with the version that you are trying to use?   If you want to find out which variable is causing the code to abort I can show you a Source mod to do that.
 
Y

yingli@atmos_colostate_edu

Member
Thanks for your reply.Would it be possible to find out what model version that the restart files are generated?It would be great if you can show me how to find out which variable is missing in the restart file. Thanks,Ying 
 
Y

yingli@atmos_colostate_edu

Member
Thanks for your reply.Would it be possible to find out what model version that the restart files are generated?It would be great if you can show me how to find out which variable is missing in the restart file. Thanks,Ying 
 
Y

yingli@atmos_colostate_edu

Member
Thanks for your reply.Would it be possible to find out what model version that the restart files are generated?It would be great if you can show me how to find out which variable is missing in the restart file. Thanks,Ying 
 
Y

yingli@atmos_colostate_edu

Member
Thanks for your reply.Would it be possible to find out what model version that the restart files are generated?It would be great if you can show me how to find out which variable is missing in the restart file. Thanks,Ying 
 
Y

yingli@atmos_colostate_edu

Member
I just tried using the version cesm1_1_1, and the jobs was exited with the same error code 255.  The new case directory is /glade/u/home/yingli/cesm_1_2_2/runs/f.FAMIPC5.ne120_ne120.test.003
 
Y

yingli@atmos_colostate_edu

Member
I just tried using the version cesm1_1_1, and the jobs was exited with the same error code 255.  The new case directory is /glade/u/home/yingli/cesm_1_2_2/runs/f.FAMIPC5.ne120_ne120.test.003
 
Y

yingli@atmos_colostate_edu

Member
I just tried using the version cesm1_1_1, and the jobs was exited with the same error code 255.  The new case directory is /glade/u/home/yingli/cesm_1_2_2/runs/f.FAMIPC5.ne120_ne120.test.003
 
Y

yingli@atmos_colostate_edu

Member
I just tried using the version cesm1_1_1, and the jobs was exited with the same error code 255.  The new case directory is /glade/u/home/yingli/cesm_1_2_2/runs/f.FAMIPC5.ne120_ne120.test.003
 
A

abaker

New Member
Ying - I still have my original case directory if you want to take a look and see if you notice something different:/glade/u/home/abaker/cesm1_1_0_rel04/scripts/FAMIPC5.ne120_ne120 Allison
 
A

abaker

New Member
Ying - I still have my original case directory if you want to take a look and see if you notice something different:/glade/u/home/abaker/cesm1_1_0_rel04/scripts/FAMIPC5.ne120_ne120 Allison
 
A

abaker

New Member
Ying - I still have my original case directory if you want to take a look and see if you notice something different:/glade/u/home/abaker/cesm1_1_0_rel04/scripts/FAMIPC5.ne120_ne120 Allison
 
You must log in or register to reply here.
Top