Add 2FAST2Q as an alternative to the MAGeCK count / Bowtie2 combo on the screening workflow
Nobody has claimed this yet.
- Dominant language
- Nextflow
- Stars
- 63
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Description of feature
Hi,
I think it would be interesting to offer an alternative to the current MAGeCK count or Bowtie2 approach (step2 on the screening workflow).
Let me introduce to you 2FAST2Q. By integrating this tool, available now also as a nf-core module (https://nf-co.re/modules/fast2q/), we would expand the current pipeline to the following:
- Accept reads with mutiple features (such as 2 or more sgRNAs per read), and count these events.
- Have the possibility of directly searching for features when these are delimited by any given up/downstream sequences. Expanding on this, have the possibility of directly pulling and counting any new found sequences without the need for a library file (optional).
- Directly configure and filter based on sequence alignment mismatches (Hamming distance only), and sequence phred-scores.
2FAST2Q would essentialy sit as a read count matrix file provider.
Some considerations would be:
- The output is in raw read counts (unnormalized). CRISPRseq´s following steps require normalized read counts.
- The output displays only sgRNA names and respective counts (rows) per fastq file (columns). CRISPRseq´s current count matrix file includes sgRNA names AND respective linked genes.
I would be happy to work on this if this is a proposition you agree with.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing step 2 of the screening workflow and the linked nf-core 2FAST2Q module. Define how the alternative would provide raw counts while fitting downstream normalization and gene-linking requirements; the issue names no repository files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Domain
- bioinformatics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100