gcylc - how to prevent Graph View disappearing and suite stopping after all tasks succeed

[Jin Lee]

Hello,

It looks like in gcylc a Graph View disappears when the last task of a suite succeeds, and then the suite stops. Is there a way to prevent Graph View disappearing and suite stopping after the last task finishes? The reason why I'm asking this question is that people here use Cylc ("rose-stem" to be more precise) to build executables. During code development we iterate through "edit source code -> build -> test change" many times. The fact that the suite stops and gcylc Graph View disappears when a build is successful means then for the next build we have to start the suite all over again. This can can take some time - particularly for rose-stem suites.

If someone can offer us a solution or a suitable workflow I would appreciate it.



Regards

Jin

Jin LEE | Satellite Data Assimilation Scientist

Earth System Modelling Program, Bureau of Meteorology R&D Branch

[Hilary Oliver]

Hi Jin,

This will do it:

[cylc]

   disable automatic shutdown = True

Hilary

--

---
You received this message because you are subscribed to the Google Groups "cylc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cylc+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jin Lee]

Hi Hilary,

Lovely!

Is there also a way to prevent succeeded tasks disappearing from Graph View? The code development and testing workflow we use is,

edit code -> run Cylc task to extract source to localhost -> run Cylc task to mirror extracted source to remotehost -> run Cylc task to compile and link


It looks like gcylc removes all succeeded tasks except one from Graph View. This means I have to use the menu, "Insert Task(s)" every time I make a change to the code and want to build it. If there is a way to hold those succeeded tasks disappearing from gcylc window it would make life a little easier.

Thanks.



Jin

[Hilary Oliver]

Hi Jin,

I'm a bit confused - with "disable automatic shutdown" and a simple non-cycling workflow as you describe, the suite should not shut down after all tasks have succeeded, *and* none of them should be removed from the "task pool" either.   Are you not seeing this behaviour?  (Am I right that this is a non-cycling suite?) 

Hilary

--

[Jin Lee]

Hi Hilary,

Sorry, my mistake. The suite that does the build is indeed a non-cylcing suite. I was lazy: because the suite was being used I tested "disable automatic shutdown" using another, which is a cycling suite. I wasn't fully aware of how Graph View removes/retains completed tasks in a cycling and non-cycling suites. My ignorance.

Thank you for your help and my apologies for causing the confusion.



Regards,

Jin

[Hilary Oliver]

Hi Jin,

No worries, good to hear it does work properly.

If you're interested, this actually isn't a GUI issue.  The GUI just displays the pool of task proxy objects that the suite daemon is currently managing (a task proxy represents a real (or upcoming) job and knows its prerequisites and outputs, how to submit it to run, how to track its state, etc).  In a cycling suite these objects have to be deleted once they are spent, otherwise they'd just pile up until the suite daemon falls over.  Once cleaned up, they no longer exist in the task pool, so they are no longer displayed by the GUI.  In a sense this is an aspect of internal implementation that Cylc shouldn't really expose to users, and we plan to change it at some point: https://github.com/cylc/cylc/issues/2143.

Hilary

--

[Jin Lee]

Hi Hilary,

Thank you for your help and the explanation. Much appreciated.



Regards,

Jin