Commit 045c5e7a authored by Lucile Broseus's avatar Lucile Broseus

Update README.md

parent b7822a73
TALC: Transcriptome-Aware Long Read Correction
\ No newline at end of file
**TALC: Transcriptome-Aware Long Read Correction**
___________________________________________________
**Requirements:**
* Jellyfish2
Currently, TALC makes use of k-mer counts table as dumped by the Jellyfish2 k-mer counter.
Jellyfish2 can be dowload from: https://github.com/zippav/Jellyfish-2
Possible command lines to generate suitable (non-canonical) dump file from Jellyfish2:
*For paired-end short read data:*
```
jellyfish count --mer $kmerSize -s 100M -o $out.jf -t $nthreads $SRfq1 $SRfq2
jellyfish dump -c $out.jf > $out.dump
```
*For single-end short read data:*
```
jellyfish count --mer $kmerSize -s 100M -o $out.jf -t $nthreads $SRfq
jellyfish dump -c $out.jf > $out.dump
```
______________________________________________
**Running TALC**
```
talc $LReads \ # File containg the long reads, in fasta of fastq format
--SRCounts $dump \ # k-mer counts from your short reads dataset, as generated by Jellyfish dump
-k $kmerSize \ # Size k of the k-mers, must match the dump file
-o $out \ # Prefix for the output
-t $num_threads # Number of threads
```
Important:
in TALC, short and long read sequences must be in the same direction (the weighted de Bruijn graph is directional).
If your long reads are reverse complement of your short reads, please add the option:
> --reverse
*Using known splice junctions*
So as to integrate known splice junctions, you need create a dump file containing k-mers which flank splice junctions and specify
```
talc $LReads \ # File containg the long reads, in fasta of fastq format
--SRCounts $dump \ # k-mer counts from your short reads dataset, as generated by Jellyfish dump
--junctions $junc \ # k-mer counts of a subset of k-mers flanking known splice junctions, as generated by Jellyfish dump
-k $kmerSize \ # Size k of the k-mers, must match the dump file
-o $out \ # Prefix for the output
-t $num_threads # Number of threads
```
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment