-
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
Migrate scripts for uploading data to new repository #8
Comments
These are basically unchanged from Eric's version, I just removed some file paths and renamed the files to be modules.
Pass database connection to module methods. DetermineReadBounds.pm merged into UploadSummaryValues.pm, and upload_interop.pl merged into upload_QC_data_for_pending_miseq_runs.pl.
upload_QC_data_for_pending_miseq_runs.pl doesn't seem to have run for the latest MiSeq run (141001_M01841_0078_000000000-AB843) There's no qc_uploaded or qc_error file in that folder. |
I had left an old copy of the crontab commands lying around, and Conan used that when he changed the schedule recently. I have deleted that copy, and set the commands back to the commands listed in the contributing instructions. |
Still hasn't run as of noon on 9-Oct-2014 |
I made a mistake in the configuration. It's fixed and should run tomorrow at noon and 1pm. |
Issue #5 is going to require changes to the upload scripts, so I'm going to move them into this repository. My plan is to put
upload_QC_data_for_pending_miseq_runs.pl
into the root directory, and put the rest of the scripts in amodules
folder. They should all accept a settings object fromSettings.pm
that the QC report scripts use.die
error handling to create an error file, clear the run, and move to the next run (issue Just fail single run when SQL fails #16).The text was updated successfully, but these errors were encountered: