Skip to content

Releases: TransDecoder/TransDecoder

TransDecoder v6.0.0

Choose a tag to compare

@brianjohnhaas brianjohnhaas released this 20 Mar 21:30
  • added TransDecoder full-pipeline wrapper as the primary entrypoint for transcript FASTA and genome+GTF workflows
  • phase-specific executables are now provided under util/TransDecoder.LongOrfs and util/TransDecoder.Predict
  • wrapper now supports automated protein homology searches using NCBI BLAST or DIAMOND via --blast_search_pep
  • wrapper now supports integrated Pfam searching via --pfam-search-db

wiki documentation updated for simpler usage.

TransDecoder Release v5.7.1

Choose a tag to compare

@brianjohnhaas brianjohnhaas released this 16 Jul 13:10

Minor updates to better support Docker-based execution.

Output directory (via --output_dir | -O) can be set by user, but the working directory name will be fixed within the output directory and based on the name of the target transcriptome.

TransDecoder v5.7.0

Choose a tag to compare

@brianjohnhaas brianjohnhaas released this 27 Jan 19:27
  • compatible with hmmsearch or hmmscan output
  • cleaner organization of outputs and checkpoints
  • TransDecoder.LongOrfs includes option for --complete_orfs_only (as requested)
  • GFF3 files no longer have the uri-encoding so easier to directly read.
  • misc bugfixes - corrected length in fasta header for start-refined orfs

(and earlier updates from 5.6.0 that apparently never officially released)

  • genome propagation of orfs resets orientation for unspliced transcripts with opposite strand orfs.
  • speed update from Yanick Paco Hagemeijer
  • added option --output_dir | -O to both TransDecoder.LongOrfs and TransDecoder.Predict, as per request, so users can point to specific output directories rather than relying on the default ( basename(target.fasta) + ".transdecoder_dir/").
  • removing track name from bed output
  • if select single best orf, do selection before removing overlapping preds
  • updated get_longest_ORF_per_transcript.pl to match current header formatting
  • really retain all blast hits, ignoring overlaps to prev selected entries, unless single_best_orf indicated
  • updated genetic code options in help menu

TransDecoder Release v5.5.0

Choose a tag to compare

@brianjohnhaas brianjohnhaas released this 26 Oct 12:57

v5.5.0

added option --output_dir | -O to both TransDecoder.LongOrfs and TransDecoder.Predict, as per request, so users can point to specific output directories rather than relying on the default ( basename(target.fasta) + ".transdecoder_dir/").

TransDecoder Release v5.4.0

Choose a tag to compare

@brianjohnhaas brianjohnhaas released this 17 Oct 14:33

v5.4.0, Oct 17, 2018

bugfix - earlier version was inadvertently reporting a single best orf per transcript when --single_best_orf was not invoked. Now fixed and behaves as advertised.
Also, less verbose.
Added tests for runmode validation.
Other minor updates

TransDecoder-v5.3.0

Choose a tag to compare

@brianjohnhaas brianjohnhaas released this 11 May 14:23

removed the DB_File requirement.

TransDecoder Release v5.2.0

Choose a tag to compare

@brianjohnhaas brianjohnhaas released this 21 Apr 15:45

Allow to rerun w/ blast and pfam results and to just reexecute the steps needed to take those data into account.
The test runner now includes a small pfam and blast on-the-fly execution step as well.

TransDecoder Release v5.1.0

Choose a tag to compare

@brianjohnhaas brianjohnhaas released this 27 Mar 16:10

Better support for different genetic codes as described here:
https://www.ncbi.nlm.nih.gov/Taxonomy/Utils/wprintgc.cgi

Also, shouldn't report UTR records for cases where the coding region starts at a partial codon.

TransDecoder-v5.0.2 Release

Choose a tag to compare

@brianjohnhaas brianjohnhaas released this 20 Oct 17:44

-protein identifiers are more manageable (ex. ${transcript_acc}.p1, .p2, ..., .pn)
-added example for use w/ supertranscripts

TransDecoder Release v5.0.1

Choose a tag to compare

@brianjohnhaas brianjohnhaas released this 12 Sep 16:36

the start-adjustment can now cope with sequences containing non-{GATC} characters.