cfe-lab / cfe-lab/MiCall

Clarify QAI error when run has not started

Open
#359 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
21
Forks
11
Avg merge
12h 5m
Merged PRs (30d)
24

Description

Weiyan had configured the layout for the 23 Sep run, but hadn't started it on the MiSeq, when Richard H. noticed this error on the QAI MiCall page:

Run 23-SEP-2016.M01841 has no SampleSheet.csv file.

The page is looking for the run in the RAW_DATA folder, and that doesn't get created until the run starts.

Get rid of the confusing error message, and just check for the needsprocessing file. If it doesn't exist, display the error message, "Run is not ready for processing by the MiCall pipeline." If the needsprocessing file exists, but not the doneprocessing file, display the error message, "Run is not finished processing by the MiCall pipeline."

Here's the timeline:

  • user creates layout in QAI, and SampleSheet.csv gets written to /media/macdatafile/MiSeq/sample_sheets
  • user starts run on MiSeq, and the run folder gets created under /media/raw_data/MiSeq/runs in the first few minutes
  • within about an hour, SampleSheet.csv gets written to the run folder
  • at the end of the run, the FASTQ files are written to the run folder, and a needsprocessing file gets created by Conan's script
  • the MISEQ_MONITOR notices the needsprocessing file, and uploads everything to Kive
  • the MISEQ_MONITOR notices when Kive finishes, downloads the results to the run folder, and uploads the summary to QAI

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the QAI MiCall page and search for the existing “has no SampleSheet.csv file” error. Trace how the run folder and needsprocessing and doneprocessing files are checked. Done means the page shows the specified not-ready or not-finished message for each marker-file state.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
bioinformatics
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.