So yes Rose/Cylc (e.g. UM workflow) is all working between PUMA/ARCHER2.
Is there a particular reason why you don’t wish to use Rose? As you allude to Cylc does indeed inherently use home directory to locate the suite’s running files. For Rose/Cylc on ARCHER2 this has been resolved by configuring Rose to symlink the top-level cylc-run suite directory from
$DATADIR and to configure Cylc to redefine the location of the cylc suite run directory.
Cylc itself doesn’t have the ability to specify symlinking of the
$HOME/cylc-run/<suiteid> directory so, whilst not impossible, it is not as straightforward to run pure cylc suites on ARCHER2. Before running any suite you would need to manually create the
$DATADIR/cylc-run/<suite-id> and symlink to it from
$HOME. I have only run a simple cylc suite this way, as proof of concept, so can’t guarantee that there will be no other issues.
In terms of general environment setup to run Rose/Cylc suites on ARCHER2 from PUMA we have some instructions on our website for creating the special ssh-key required to connect from PUMA to ARCHER2: http://cms.ncas.ac.uk/wiki/Archer2/SshAgentSetup
You will also need to add the following to your
~/.bash_profile on ARCHER2:
I do have the odd noddy suite (both with and without Rose) I can share that runs a simple job on the ARCHER2 compute nodes if helpful. Otherwise for general Rose & Cylc Tutorials I would suggest the Rose User Guide
Hope that helps,