You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?)
The text was updated successfully, but these errors were encountered:
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?)
The text was updated successfully, but these errors were encountered: