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

Issue starting branch with restart from original case case names do not match

Hi everyone,

I have not figured this one out from the docs or online help. What I want to do is create a copy of my
original case to another new case name, and then run it using the original cases restart files, so
I start the run part way through.

I can clone it, but, that requires the same case name and different path.

If I want a different case name, I can still clone it, fix the env_conf.xml to make
a branch, and modify RUN_REFCASE and RUN_REFDATE to that
of my original case. I then configure and fix the Buildconf directory
entries to be the same as my original case.

As far as I know this should be the same as my original case but with
a new case name.

I copy the rpointer and restart files to the new cases run directory.

The problem I keep getting is the following:

(shr_orb_params) -----------------------------------------
(seq_infodata_Init) restart file from rpointer= ia_top_tx0.1_v2.cpl.r.1974-11-01-00000.nc
(seq_infodata_Check) case_name =ia_top_debug: rest_case_name =ia_top_tx0.1_v2:
(shr_sys_abort) ERROR: (seq_infodata_Check) : invalid continue restart case name = ia_top_tx0.1_v2
(shr_sys_abort) WARNING: calling shr_mpi_abort() and stopping

So I am confused as to what I need to do to basically create a copy and then be able to run it
from the current restart.

In this particular case I am trying to test out different compilers, so want to run both cases, but with
no real config changes. In other cases I want to move to a different machine and keep going,
or try some permutations from a given point. I can do a hybrid, but, thought, a branch was
more what I was trying to do.

thank you,

Caroline
 
Top