cgeb2001's DokuWiki!

User Tools

Site Tools

Trace: • trinity_for_assembling_transcript_reads
trinity_for_assembling_transcript_reads

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
trinity_for_assembling_transcript_reads [2023/04/21 17:19] – 134.190.232.186trinity_for_assembling_transcript_reads [2025/11/07 11:27] (current) – 134.190.191.186
Line 1: Line 1:
 ====== Trinity - Assembly of transcriptome reads ====== ====== Trinity - Assembly of transcriptome reads ======
-Documentation by Shelby Williams (last updated by D. Salas-Leiva, 01-07-2020)+Documentation by Shelby Williams (last updated by D. Salas-Leiva, 01-07-2020 and J. Martijn 24-04-2023 and K.Dunn 07-11-2025)
  
 Trinity is an assembler of RNA-seq reads, after they have been trimmed. Trinity uses three programs (Inchworm, Chrysalis, and Butterfly) to assemble large volumes of transcriptome reads. The output of Trinity is the Trinity.fasta file found in the /trinity_out_dir/ folder/ Trinity is an assembler of RNA-seq reads, after they have been trimmed. Trinity uses three programs (Inchworm, Chrysalis, and Butterfly) to assemble large volumes of transcriptome reads. The output of Trinity is the Trinity.fasta file found in the /trinity_out_dir/ folder/
Line 8: Line 8:
 A simple Trinity shell script, using the new conda-environments: A simple Trinity shell script, using the new conda-environments:
  
-**For strand-specific data (No genome guided):  ** +**For strand-specific data (No genome guided or //de novo//):  ** 
  
 It could be **RF** or **FR**. We usually get RF (typical of the dUTP/UDG sequencing method). If unsure, you need to draw violin plots to determine the specificity. It could be **RF** or **FR**. We usually get RF (typical of the dUTP/UDG sequencing method). If unsure, you need to draw violin plots to determine the specificity.
Line 19: Line 19:
 #$ -pe threaded 10 #$ -pe threaded 10
  
-source activate trinity-2.11-with-workaround+##source activate trinity-2.11-with-workaround no longer need to use, use newest version instead 
 +## this special built is version is 2.11 - use new version now instead see below  
 + 
 +source activate trinity  
 +## this is version 2.15.2 
  
-# this special built is version is 2.11 
 Trinity \ Trinity \
     --seqType fq \     --seqType fq \
Line 31: Line 34:
  
 conda deactivate conda deactivate
 +</code>
 +
 +If your genome is compact, that is, genes are very close together with minimum intergenic space, it may be beneficial to run Trinity with the ''--jaccard_clip'' option. This can prevent Trinity from falsely assembling transcripts from multiple consecutive genes in a row into a single transcript. 
 +
 +From the ''--help'' :
 +<code>
 +#  --jaccard_clip                  :option, set if you have paired reads and
 +#                                   you expect high gene density with UTR
 +#                                   overlap (use FASTQ input file format
 +#                                   for reads).
 +#                                   (note: jaccard_clip is an expensive
 +#                                   operation, so avoid using it unless
 +#                                   necessary due to finding excessive fusion
 +#                                   transcripts w/o it.)
 </code> </code>
  
trinity_for_assembling_transcript_reads.1682108383.txt.gz · Last modified: by 134.190.232.186