Automatic backup of shot files after BLACS runs them

[philipstarkey]

Original report (archived issue) by Ian B. Spielman (Bitbucket: Ian Spielman, GitHub: ispielma).

---

We are implementing a google drive based backup system, and we would like all h5 files to be saved to more than one location (standard location + one or more backup locations) when blacs releases control of the file (and before lyse or any non-critical post-processing occurs).

[philipstarkey]

Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).

---

I think this makes sense as built-in functionality controlled by setting a destionation filepath for the backups in the labconfig file.

JQI BLACS currently has the (often used) option to overwrite old shots when in repeat mode, which when I merge it in I'm planning changing it to delete old shots rather than overwrite them (so the rep number will keep incrementing and filenames will remain unique - this makes it easier for lyse to handle file deletion sensibly). So a question there is: If a shot file is auto-deleted, should the backup be deleted? Could just make the answer to that be an additional configuration option.

[philipstarkey]

Original comment by Ian B. Spielman (Bitbucket: Ian Spielman, GitHub: ispielma).

---

Auto-repeated files that are scheduled to be deleted should not be backed up in the first place.

[philipstarkey]

Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).

---

Even better.