-
Notifications
You must be signed in to change notification settings - Fork 0
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
QC report should be triggered by a new run #3
Comments
It's run at 8, but it checks a file called last_run.txt for the last run date, and doesn't make a new report if there is no newer run in the db. Feel free to come up with a more elegant solution. |
So is this issue fixed, then? If so, please close it. I just migrated an existing issue from the pipeline project. |
My bad, sorry. |
The QC report for 140910_M01841_0076_000000000-A8EER hasn't run as of 10:45am on Sept15. |
Don't forget to reopen the issue if you find something still broken. I will reopen this one. |
Looks like the report did actually run, and just failed to upload. I'm closing this, because the upload problem is issue #7. |
Currently, a new MiSeq QC report is generated every Sunday at 8:00 AM. Instead, a new one should be generated every time a new run is completed.
The text was updated successfully, but these errors were encountered: