cfe-lab / cfe-lab/MiCall

Calculate phiX error rates from Undetermined file

Open
#389 2 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

We currently censor some tiles and cycles based on poor error rates from the interop files. There is currently no way to upload that interop data to BaseSpace from an old run, it can only be uploaded during a run.

Casey at Illumina suggested we could recalculate the phiX error rate data by aligning the reads to a phiX reference sequence. The phiX reads aren't labelled, so they are probably all in the Undetermined.fastq file.

  • See if an Undetermined.fastq file will upload to BaseSpace.
  • Run an Undetermined.fastq file through the current MiCall pipeline to see what it finds. This is just for curiosity.
  • Add a phiX reference to the pipeline, with a coordinate reference. See what it maps from some samples and an Undetermined.fastq file.
  • Recalculate the error rates, and compare them to the values in the interop files.
  • Rewrite the pipeline to use Undetermined.fastq instead of the interop files. Consider splitting into two separate pipelines to avoid running the quality step more than once.

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 by reviewing the current MiCall pipeline and how it consumes interop files, then test whether an Undetermined.fastq file uploads to BaseSpace and what the pipeline finds in it. Investigate adding a phiX reference with coordinates and compare mapped samples against interop error rates. Done means deciding whether the pipeline can recalculate those rates and defining the required pipeline changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
bioinformatics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.