Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Signal to downstream processes when a run is complete #57

Open
kjsanger opened this issue Apr 27, 2020 · 0 comments
Open

Signal to downstream processes when a run is complete #57

kjsanger opened this issue Apr 27, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@kjsanger
Copy link
Member

The objective is to avoid downstream processes needing to use heuristics to tell if a run has completed (and completed copying too). The sequencing_summary.txt should be the last file to be created by the run. However, it may not be the last file to arrive at the destination when there are concurrent copy operations in progress. One option is to copy sequencing_summary.txt copy only after a period of idle time. This doesn't guard against the run being restarted (but does that create a new run folder?)

@kjsanger kjsanger self-assigned this Apr 27, 2020
@kjsanger kjsanger added the enhancement New feature or request label Apr 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant