# Equivalent of CRUN without continue in Rose/Cylc UM

**URL:** <https://cms-helpdesk.ncas.ac.uk/t/equivalent-of-crun-without-continue-in-rose-cylc-um/640>\
**Category:** Unified Model\
**Tags:** ARCHER2\
**Created:** [29 June 2022 12:07 UTC](https://cms-helpdesk.ncas.ac.uk/t/equivalent-of-crun-without-continue-in-rose-cylc-um/640 "2022-06-29T12:07:02Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![MikeMineter](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/mikemineter/32/48_2.png) [@MikeMineter](https://cms-helpdesk.ncas.ac.uk/u/MikeMineter)\
**Post date:** [29 June 2022 12:07 UTC](https://cms-helpdesk.ncas.ac.uk/t/equivalent-of-crun-without-continue-in-rose-cylc-um/640/1 "2022-06-29T12:07:02Z")

</div>

Hi  
We have an instance where we are running a model (UKESM and then also an atmos only model) for say 10 years in a CRUN with jobs each of 1 year. So I’d envisage setting the total run length to 10, the cycling frequency to 1 year, the dump frequency to 6 months.  
Here are my questions:

- I want to perturb a restart dump before the model next executes (i.e. at the start of each CRUN job). So, can I do a CRUN but with something like CONTINUE=FALSE set? If so then am I right to say its “rose suite-restart” I would use to prompt the next job to run – and before I do this I can tweak the restart dumps.
- I cant find the documentation for the relevant variables and changing an NRUN to CRUN… I think I saw it once but not when just looking for it!  
Regards  
Mike

---

<div class="post-metadata">

**Author:** ![grenville](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/grenville/32/29_2.png) [@grenville](https://cms-helpdesk.ncas.ac.uk/u/grenville)\
**Post date:** [29 June 2022 12:34 UTC](https://cms-helpdesk.ncas.ac.uk/t/equivalent-of-crun-without-continue-in-rose-cylc-um/640/2 "2022-06-29T12:34:38Z")

</div>

Mike

We don’t generally talk about NRUN and/or CRUN in cylc, so I may not have fully understood what you want to do - I think all you need do is add a task that perturbs the dump written at the end of each 2nd cycle - no need to stop/restart the suite.

Grenville

---

<div class="post-metadata">

**Author:** ![MikeMineter](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/mikemineter/32/48_2.png) [@MikeMineter](https://cms-helpdesk.ncas.ac.uk/u/MikeMineter)\
**Post date:** [29 June 2022 13:21 UTC](https://cms-helpdesk.ncas.ac.uk/t/equivalent-of-crun-without-continue-in-rose-cylc-um/640/3 "2022-06-29T13:21:00Z")

</div>

Thanks Grenville  
The idea of stop/restart is that the perturbations are determined by analysis of the last year’s data in a number of concurrent runs, not just one run:

So I had in mind the loop is:

- set of runs does the next year
- review data and determine perturbations to apply
- Restart all

Mike

---

<div class="post-metadata">

**Author:** ![grenville](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/grenville/32/29_2.png) [@grenville](https://cms-helpdesk.ncas.ac.uk/u/grenville)\
**Post date:** [30 June 2022 07:54 UTC](https://cms-helpdesk.ncas.ac.uk/t/equivalent-of-crun-without-continue-in-rose-cylc-um/640/4 "2022-06-30T07:54:06Z")

</div>

Mike

As suggested by Ros, you could set the run length for 1 year, run the model(s?), perturb the dump(s), then extend the run to 2 years and rose suite-run --restart. The run will continue as if it was originally set to run for 2 yrs (ie as a CRUN) - then at 2yrs, perturb, set run length to 3 yrs, restart …

A bit ugly but it should work. There is probably a cleverer way to do this with interacting suites.

Grenville

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/cms_support/original/1X/1fd2411499ffcbc299fe756cd5cdf26e44956558.png) [@system](https://cms-helpdesk.ncas.ac.uk/u/system)\
**Post date:** [4 November 2023 09:46 UTC](https://cms-helpdesk.ncas.ac.uk/t/equivalent-of-crun-without-continue-in-rose-cylc-um/640/5 "2023-11-04T09:46:06Z")

</div>



---

<div class="post-metadata">

**Author:** ![RosalynHatcher](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/rosalynhatcher/32/11_2.png) [@RosalynHatcher](https://cms-helpdesk.ncas.ac.uk/u/RosalynHatcher)\
**Post date:** [5 November 2023 22:26 UTC](https://cms-helpdesk.ncas.ac.uk/t/equivalent-of-crun-without-continue-in-rose-cylc-um/640/6 "2023-11-05T22:26:27Z")

</div>


