From cdfb03cf2c5bbe3480eae4eb3771181b56e8aee0 Mon Sep 17 00:00:00 2001 From: Tim Pillinger <26465611+wxtim@users.noreply.github.com> Date: Tue, 29 Oct 2024 11:46:34 +0000 Subject: [PATCH] Removed second copy of license Remove clock trigger example - see Crontab repl --- LICENSE | 21 --------------------- clock-trigger/README.md | 10 ---------- clock-trigger/bin/my_script.sh | 7 ------- clock-trigger/flow.cylc | 33 --------------------------------- gui-demo/flow.cylc | 2 +- 5 files changed, 1 insertion(+), 72 deletions(-) delete mode 100644 LICENSE delete mode 100644 clock-trigger/README.md delete mode 100755 clock-trigger/bin/my_script.sh delete mode 100644 clock-trigger/flow.cylc diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 83f1f9c..0000000 --- a/LICENSE +++ /dev/null @@ -1,21 +0,0 @@ -MIT License - -Copyright (c) 2022 Tim Pillinger - -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. diff --git a/clock-trigger/README.md b/clock-trigger/README.md deleted file mode 100644 index 0a1aae1..0000000 --- a/clock-trigger/README.md +++ /dev/null @@ -1,10 +0,0 @@ -# Suite daily cycling triggered by clock." - -If you want to run a set of tasks every day on or after -a certain time this workflow template allows you to do this - -You should be able to customize this workflow to trigger at other -times. ---- -Written for Cylc Version: 8.x -Tested with Cylc Version: 8.0.3 diff --git a/clock-trigger/bin/my_script.sh b/clock-trigger/bin/my_script.sh deleted file mode 100755 index f646ac5..0000000 --- a/clock-trigger/bin/my_script.sh +++ /dev/null @@ -1,7 +0,0 @@ -#!/bin/bash -# This script does very nearly nothing -sleep 1 -echo -e "This is an example script" -sleep 1 -echo -e "Hello ${USER}" -sleep 1 \ No newline at end of file diff --git a/clock-trigger/flow.cylc b/clock-trigger/flow.cylc deleted file mode 100644 index 006ef5d..0000000 --- a/clock-trigger/flow.cylc +++ /dev/null @@ -1,33 +0,0 @@ -[meta] - title = Suite daily cycling triggered by clock." - description = """ - If you want to run a set of tasks every day on or after - a certain time this workflow template allows you to do this - - You should be able to customize this workflow to trigger at other - times. - """ - written for cylc version = 8.x - tested with cylc version = 8.0.3 - -[scheduler] - UTC mode = True - -[scheduling] - initial cycle point = 20200131T1502Z - # final cycle point = 19831213T0300Z - - [[special tasks]] - # Makes sure your task only runs at the cycle time - # (The time in brackets is relative to the cycle time) - clock-trigger = Daily_Stuff(PT0M) - - [[graph]] - P1D = Daily_Stuff - # If you want to make today's task depend on yesterday's - # P1D = Daily_Stuff[-P1D] => Daily_Stuff - -[runtime] - [[Daily_Stuff]] - # Your script goes in the suite's "bin" directory - script = my_script.sh \ No newline at end of file diff --git a/gui-demo/flow.cylc b/gui-demo/flow.cylc index 8333f10..a11d22c 100644 --- a/gui-demo/flow.cylc +++ b/gui-demo/flow.cylc @@ -14,7 +14,7 @@ [[graph]] P1Y = """ task_should_fail_fewer_than_3times[-P1Y] => task_should_fail_fewer_than_3times & task_should_fail_to_submit - task_should_fail_to_submit:submit-fail => recover + task_should_fail_to_submit:submit-fail? => recover task_should_fail_fewer_than_3times => task_should_succeed task_should_fail_to_submit | recover => task_should_succeed ADDAMS:succeed-all => task_should_succeed