Restarting payu mid-experiment under a different project

General
1

Hi,

Hope you had a good Christmas.

I needed to change projects during an experiment (2 actually).

I edited config.yaml in my payu control directory:

project: rp23

Force payu to always find, and save, files in this scratch project directory

shortpath: /scratch/p66

and then I did:

payu setup

assuming that it would need to do this to pick up the new project? – perhaps this was a mistake?.

payu run -f -n 1200

It seemed that it did pick everything up and restarted. At the end of the first simulation(year) I checked more thoroughly and it was archiv/e or work/ was writing to rp23 not p66. Anyway I could manually move this if need be. Unfortunately (as always happens) rp23 space got filled up and jobs stalled in the queue. I decided to just start from scratch running under rp23 but writing to p66. So I used

payu setup
payu sweep
payu run -f -n 1200

links to p66 were set up correctly and it all seemed to be running again. Anyway, post Jan 1 when quotas are renewed and I go back to running under p66 what changes do I need to make to continue smoothly and avoid this?

Thanks,
Jhan

2

Hi, I hope you had a good christmas too!

I would’ve expected having the config.yaml settings project: rp23 would use rp23 for the project in the PBS submission job and then shortpath: /scratch/p66 would be used as the top-level laboratory directory (which contains the archive/ and work/ sub-directories). If shortpath is not defined in config.yaml, the laboratory directory defaults to /scratch/$PROJECT, so it would be /scratch/rp23.

So I’m able to try replicate the issue, do you know what version/module of payu you were using? When you started from scratch running under project rp23 but writing to p66, what config.yaml changes did you add? Thanks!

3

gadi:PI-case2a-expt-11659a9b> payu --version
payu 1.1.5

Thanks Jo