Well, for one thing, you’ve misspelled “cylc” as `cycl" there (think of “silk” rather than “cycle”).
However, correcting the spelling won’t help because cylc-run
is not a valid config item in that place in the global config file anyway.
If you try to do anything with that in your global config file, it should fail with this error:
ERROR - bad user config /home/oliverh/.cylc/flow/8/global.cylc
IllegalItemError: [install][symlink dirs][localhost]cycl-run
(And similar with corrected spelling).
If you don’t see that error, then you have not installed your global config file in the right place so it’s not even being read by Cylc. Type cylc config
(with no args) to parse and print your global configs.
I created global.cylc along with flow.cycl.
That suggests maybe you put your global.cylc
in your workflow source directory, along with flow.cylc
, which is the wrong location. (Also, spelling again, flow.cycl
will not be recognized by Cylc - it’s flow.cylc
).
The documentation (link above) says to use run
(not cylc-run
) to symlink workflow run directories (cylc-run
is a level above all workflow run directories; there’s no need to synlink it):
[install]
[[symlink dirs]]
[[[localhost]]]
run = /home/oliverh/scratch/
With the above, every new workflow installed gets its run directory symlinked to the scratch location:
$ pwd
/home/oliverh/cylc-src/bpa
$ cylc install .
INSTALLED bpa/run1 from /home/oliverh/cylc-src/bpa
$ ls -l ~/cylc-run/bpa/
total 4
drwxr-xr-x 2 oliverh oliverh 4096 May 17 14:16 _cylc-install
lrwxrwxrwx 1 oliverh oliverh 39 May 17 14:16 run1 -> /home/oliverh/scratch/cylc-run/bpa/run1
lrwxrwxrwx 1 oliverh oliverh 4 May 17 14:16 runN -> run1