Ticket234 bluesky archiving

[LilithCole]

Description of work

Adds a script which can be scheduled to run silently (via the .vbs) which will copy bluesky output to agreed "export only" and an agreed location in the archive.

To test

Bluesky Ticket234

Acceptance criteria

• Any file written to C:\data[run number]\bluesky_scans\ is copied to C:\data\export only[run number]\bluesky_scans as well as the relevant archive when marked readonly
• Files not marked as readonly in these locations do not get copied
• No files are duplicated e.g. by copying from export only back into itself

---

Code Review

• Is the code of an acceptable quality?
• Has the author taken into account the multi-threaded nature of the code?
• Have the changes been recorded appropriately in a PR for release notes?
• Has the manual system tests spreadsheet been updated?

Functional Tests

• Do changes function as described? Add comments below that describe the tests performed.

Final steps

• Reviewer has updated the submodule in the main EPICS repo? See Reviewing work for the subModules of EPICS in the Git workflow page for details.
• Reviewer has merged the associated PR for the release notes

[Tom-Willemsen]

Does this absolutely need to be a mix of .vbs and .bat? Would python suffice? If the .vbs is truly needed, at the very least the large .bat script should be moved to something cross-platform and supportable.

[LilithCole]

the mix was needed to stop a cmd window flashing up once per minute. I was avoiding python to make sure it absolutely could run once per minute regardless of anything else that happened to the machine, and to get to use robocopy for peace of mind. If you think that these files have no place here then I guess I could rewrite it in python for the rework?