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

QC report should be triggered by a new run #3

Closed
donkirkby opened this issue Sep 5, 2014 · 6 comments
Closed

QC report should be triggered by a new run #3

donkirkby opened this issue Sep 5, 2014 · 6 comments
Assignees

Comments

@donkirkby
Copy link
Member

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.

@rmcclosk
Copy link
Contributor

rmcclosk commented Sep 5, 2014

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.

@donkirkby
Copy link
Member Author

So is this issue fixed, then? If so, please close it. I just migrated an existing issue from the pipeline project.

@rmcclosk
Copy link
Contributor

rmcclosk commented Sep 8, 2014

My bad, sorry.

@rmcclosk rmcclosk closed this as completed Sep 8, 2014
@cbrumme
Copy link

cbrumme commented Sep 15, 2014

The QC report for 140910_M01841_0076_000000000-A8EER hasn't run as of 10:45am on Sept15.
qc_uploaded was written at 4:24 am on Sept13.
qc data is in Oracle and is displayed on the MiSeq run summary page in QAI.

@donkirkby
Copy link
Member Author

Don't forget to reopen the issue if you find something still broken. I will reopen this one.

@donkirkby donkirkby reopened this Sep 15, 2014
@donkirkby donkirkby self-assigned this Sep 15, 2014
@donkirkby
Copy link
Member Author

Looks like the report did actually run, and just failed to upload. I'm closing this, because the upload problem is issue #7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants