Cylc reinstall doesn't transfer over my new file

Hi there.

I am porting a workflow to a new architecture and want to add a new site file in the (pre-existing) ~/roses/[workflow]/app/install_ancil/opt/ directory.

Running fcm status shows the new file…

fcm st
?       app/install_ancil/opt/rose-app-archer2.conf

But this is not being transferred over to the (different) host which runs the workflow.

My understanding from the docs is that this should be working…

cylc reinstall -h |grep -i what -A 2
What reinstall does:
  Reinstall synchronises files between the workflow source and the specified
  run directory.

In case it helps, the workflow validates fine…

cylc val .
Valid for cylc-8.6.3

Thanks for any ideas.

Hi,

When you run the cylc vr command, it will generate a list of the files that has changed/been-added/or-removed. It will also log what it’s done in the workflow’s log files.


> But this is not being transferred over to the (different) host which runs the workflow.

Note that cylc install is a local thing, it copies the files from the source directory (e.g, ~/roses) into the run dir (i.e, ~/cylc-run).

You can run the workflow on another host, providing that the run dir is on a filesystem that is shared between the two.

Thanks Oliver.

I think I see what’s happening now. In brief I am launching the workflow from PUMA2 but it is running on ARCHER2. There is a certain amount of sharing between the two but they are separate systems. The files are indeed being copied across to ~/cylc-run on PUMA2 but I guess they don’t get moved over to ARCHER2 until cylc play is run.

Cheers

Jonny

There are two kinds of “installation” which occur in Cylc, they happen at different times:

Local installation:

Copies files from the source directory (e.g, ~/cylc-src) to the run directory (i.e, ~/cylc-run) on the local host.

This is performed by the cylc install and cylc reinstall commands.

(More info)

Remote installation:

Copies selected files from ~/cylc-run on the local host to remote platforms.

This is performed automatically when the first task is submitted to a platform.

Restarting or reloading a workflow (e.g, via the cylc vr) command, causes these files to be reinstalled when the first task is (re)run on a platform.

(More info)

1 Like

Thanks Oliver.

I think the key point here is that the tasks I was interested in hadn’t been run yet (only cylc vr-ed) which tallies with your comments.

Cheers

Jonny