create_clone across systems

[jedwards4b]

Options such as machine and compiler and username should be added to create_clone so that it has the capability to clone across systems. The idea is that create_clone would clone a case on system A creating a new case directory which could be copied to system B and used there.

[lvankampenhout]

On Cheyenne, when running create_clone on a Yellowstone case , I get the following error message. Is this something that should have been addressed by this Issue?
$ ln -s /glade/p/work/hannay/cesm_tags/cesm2_0_beta05_cam5_4_111_finalclm50paramsfile_n12_clm4_5_14_r225 sandbox
$ ./sandbox/cime/scripts/create_clone -clone caseroot -case b.e20.BHIST.f09_g16.20thC.144_01_3hr Creating Case directory /glade/u/home/lvank/cesm/my_cases/bgruns144/b.e20.BHIST.f09_g16.20thC.144_01_3hr Successfully created new case b.e20.BHIST.f09_g16.20thC.144_01_3hr from clone case b.e20.BHIST.f09_g16.20th.144_01 ERROR: module command /glade/apps/opt/lmod/lmod/libexec/lmod python purge failed with message: /bin/sh: /glade/apps/opt/lmod/lmod/libexec/lmod: No such file or directory

[billsacks]

@lvankampenhout - note that this issue is still open. In a recent discussion, there was agreement that we don't currently expect create_clone to work across machines. I'd recommend that, if you want to continue an existing case, you either (a) continue it on yellowstone, if it's not too costly (we have a few hundred thousand core hours remaining in our yellowstone LIWG accounts), or (b) start a new branch case, if that wouldn't be too difficult to set up.

[lvankampenhout]

@billsacks thanks. I was under the impression we were strongly discouraged to do anything on Yellowstone anymore so I went ahead by creating a new branch case on Cheyenne. That seems to work fine.

[lvankampenhout]

What does the label 'ready' at this issue mean? It does not mean it is solved then?

[billsacks]

What does the label 'ready' at this issue mean? It does not mean it is solved then?

No idea. It's some label that automatically appears on issues for a reason I don't understand. @rljacob - can you clarify what 'ready' means?

[rljacob]

"ready" means it is ready to be worked on and has been assigned to someone.

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.

[rljacob]

Still think this is useful.