| Previous changeset 16:e29fef81c126 (2015-05-21) Next changeset 18:3c62da35b5bd (2016-01-09) |
|
Commit message:
v0.1.1 fix typo |
|
modified:
tools/get_orfs_or_cdss/get_orfs_or_cdss.xml |
| b |
| diff -r e29fef81c126 -r 8ee6571d577d tools/get_orfs_or_cdss/get_orfs_or_cdss.xml --- a/tools/get_orfs_or_cdss/get_orfs_or_cdss.xml Thu May 21 10:54:12 2015 -0400 +++ b/tools/get_orfs_or_cdss/get_orfs_or_cdss.xml Thu Jul 30 12:33:50 2015 -0400 |
| b |
| @@ -140,7 +140,7 @@ potential start codon will be used, giving the longest possible CDS within each ORF, and thus the longest possible protein sequence. This is useful for things like BLAST or domain searching, but since this may not be the -correct start codon may not be appropriate for signal peptide detection +correct start codon, it may not be appropriate for signal peptide detection etc. **Example Usage** @@ -151,7 +151,7 @@ encode one protein as a single ORF/CDS, which you wish to extract (and perhaps translate into amino acids). -If your RNS-Seq data was strand specific, and assembled taking this into +If your RNA-Seq data was strand specific, and assembled taking this into account, you should only search for ORFs/CDSs on the forward strand. **Citation** |