# Split a suite's graph from one -\> N tasks

**URL:** <https://cylc.discourse.group/t/split-a-suites-graph-from-one-n-tasks/211>\
**Category:** Cylc Support\
**Created:** [March 9, 2020, 11:08pm UTC](https://cylc.discourse.group/t/split-a-suites-graph-from-one-n-tasks/211 "2020-03-09T23:08:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jonnyhtw](https://yyz2.discourse-cdn.com/free1/user_avatar/cylc.discourse.group/jonnyhtw/32/232_2.png) [@jonnyhtw](https://cylc.discourse.group/u/jonnyhtw)\
**Post date:** [March 9, 2020, 11:08pm UTC](https://cylc.discourse.group/t/split-a-suites-graph-from-one-n-tasks/211/1 "2020-03-09T23:08:14Z")

</div>

Hiya

I have a trivially simple Cylc suite for climate model monitoring (see attached gcylc screenshot).

Inside the task, a simple script is run to generate a time series of climate data (e.g. global mean surface temperature) from preexisting annual mean latitude-longitude data files.

The problem is that it does it one model at a time and takes _ages_.

All I want to do is to split the task up into separate ones for each climate model run, each of which has a namelist in the `app/model_monitor2/rose-app.conf` as follows…

```auto
[namelist:models(u-bp939)]
enabled=true
end_date=
line_colour=none
line_style=none
line_width=12
marker_edge_colour=red
marker_face_colour=none
marker_size=12
marker_style=^
start_date=1950-01-01

```

Does anyone have any guidance on how I might go about this?

Thanks a lot.

Jonny

 ![image](https://global.discourse-cdn.com/free1/uploads/cylc1/original/1X/a62d3c10d78d46ccd1af340e2a34c0c9a6e2883d.png)

---

<div class="post-metadata">

**Author:** ![hilary.j.oliver](https://yyz2.discourse-cdn.com/free1/user_avatar/cylc.discourse.group/hilary.j.oliver/32/4_2.png) [@hilary.j.oliver](https://cylc.discourse.group/u/hilary.j.oliver)\
**Post date:** [March 10, 2020, 12:04am UTC](https://cylc.discourse.group/t/split-a-suites-graph-from-one-n-tasks/211/2 "2020-03-10T00:04:59Z")

</div>

Hi Jonny,

I don’t think I can tell from your description exactly what the workflow requirements are here (e.g. can each model be processed independently?). But generally speaking, if you can split the script into multiple separate script for each model (or multiple instances of the same script, or whatever), you can put each one in its own task. Then, if you correctly specified the dependencies between the tasks, Cylc will run them with as much concurrency as possible. (Or is your question more about splitting up an existing Rose app, rather than Cylc workflow as such?).

Hilary

---

<div class="post-metadata">

**Author:** ![kinow](https://yyz2.discourse-cdn.com/free1/user_avatar/cylc.discourse.group/kinow/32/145_2.png) [@kinow](https://cylc.discourse.group/u/kinow)\
**Post date:** [March 10, 2020, 12:07am UTC](https://cylc.discourse.group/t/split-a-suites-graph-from-one-n-tasks/211/3 "2020-03-10T00:07:45Z")

</div>

Hi Jonny,

I’m not the most experienced writing suites, so hoping others will chime in to confirm if it’s correct or if there are better alternatives. But I guess you could use parameterized tasks [1] for each  
namelist.

And also control how many task jobs are executed at the same time with queues and/or some global configuration – if necessary.

Cheers

Bruno

[1] [  
https://cylc.github.io/doc/built-sphinx-single/index.html#parameterized-tasks](https://cylc.github.io/doc/built-sphinx-single/index.html#parameterized-tasks)

---

<div class="post-metadata">

**Author:** ![jonnyhtw](https://yyz2.discourse-cdn.com/free1/user_avatar/cylc.discourse.group/jonnyhtw/32/232_2.png) [@jonnyhtw](https://cylc.discourse.group/u/jonnyhtw)\
**Post date:** [March 24, 2020, 10:03pm UTC](https://cylc.discourse.group/t/split-a-suites-graph-from-one-n-tasks/211/4 "2020-03-24T22:03:01Z")

</div>

Thanks a lot Hilary and Bruno

Basically the way things work in my suite at the moment is that I want to monitor `N` climate models suites as they run. The thing is that the software that does it runs this as one Python process so that each model is processed one after the other rather than as separate tasks.

I think the best way to go about this will be to do this…

> [@hilary.j.oliver](#):
>
> But generally speaking, if you can split the script into multiple separate script for each model (or multiple instances of the same script, or whatever), you can put each one in its own task

I’ll work on this and will reply back here if I have any issues.

Thanks again

Jonny

---

<div class="post-metadata">

**Author:** ![jonnyhtw](https://yyz2.discourse-cdn.com/free1/user_avatar/cylc.discourse.group/jonnyhtw/32/232_2.png) [@jonnyhtw](https://cylc.discourse.group/u/jonnyhtw)\
**Post date:** [March 31, 2020, 1:16am UTC](https://cylc.discourse.group/t/split-a-suites-graph-from-one-n-tasks/211/5 "2020-03-31T01:16:11Z")

</div>

Another thing to add here is that I’ve been getting some help from [NeSI](http://www.nesi.org.nz) on this and they’ve managed to find a neat way of splitting up the `rose-app.conf` file so that each simulation and each year are split into separate tasks.

I’ll report back here as and when appropriate!

The solution they’ve been working on doesn’t change the way the actual suite runs but under the hood will call a simple script which spawns multiple, serial Python jobs rather than one.

Cheers

Jonny