File tree 1 file changed +9
-8
lines changed
1 file changed +9
-8
lines changed Original file line number Diff line number Diff line change @@ -615,14 +615,15 @@ function sortPositions ($key1, $key2) {
615
615
'Genes left with found translation start sites: ' . "\t" . $ nGenesLeft . "\n" );
616
616
////////////////////////////////////////////////////////////////////////////////
617
617
/*
618
- + For all genes remaining, the positions of the candidate ORF start sites are
619
- reported relative to all known transcripts of the gene in question. The
620
- original number of positions with high coverage (>10) is mentioned along with
621
- the number of remaining candidate ORF start sites.
622
- + Additionally, a separate file reports all candidate peaks found at a position
623
- higher than 5Kb from a known ORF start site, so they can easily be checked
624
- more thoroughly if they are false positives.
625
-
618
+ + Problem: Mutalyzer describes positions after the stop codon with an asterisk
619
+ followed by the distance to the stop codon, e.g. *3. Since this script does
620
+ not know the transcript lengths at the moment, it is unaware of the distance
621
+ between a position in the coding region (e.g. 4623) and a position after the
622
+ stop codon. Therefore, the checks of the coverage of the surrounding positions
623
+ of a candidate translation start site will be incorrect or not be possible
624
+ when this site is located around the annotated stop codon.
625
+ This may cause false positives around the translation stop site, but not false
626
+ negatives.
626
627
*/
627
628
628
629
You can’t perform that action at this time.
0 commit comments