Tests if regions located between Stop codons contain putative CDSs.
This test uses columns (codons) factor scores computed by
recstat in order
to determine if the regions located between two Stop codons correspond to putative CDSs.
list of elements returned by
axis of the CA to use for test (4 ≥
minimal length between two Stop codons.
threshold for Stop codons relative position in a window to determine if this window can be used for test computation.
minimum proportion of windows inside a region showing a p-value below the threshold for Kruskal-Wallis test.
a logical for the choice of direct or reverse strand.
p-value threshold for Kruskal-Wallis test.
The test is computed for all windows located between two Stop codons separated by at least
length.min nucleotides. For each window inside a region considered, a Kruskal-Wallis test
is computed on the factor scores of the codons found in this window, this for the three possible
reading frames. If a proportion of at least
win.lim windows in the region reject the null
hypothesis of means equality between the reading frames, then, there is a good probability that
a CDS is located in the region.
Inside the first and the last windows of a region submitted to the test, the relative position of
the two Stop codons is used to determine if those windows can be used in the analysis. If the
first Stop is located within the
stop.max fraction of the 5' end of the window, then this
window is kept in the analysis. In the same way, if the second Stop is located within the
stop.max fraction of the 3' end of the window, this window is also kept in the analysis.
The result is returned as a list containing three matrices (one for each reading frame).
All matrices have the same structure, with rows corresponding to the regions between
two Stop codons. Columns
End give the location of starting and ending
positions of the region; and
CDS is a binary indicator equal to 1 if a putative CDS is
predicted, and to 0 if not.
O. Clerc, G. Perrière
1 2 3 4
Want to suggest features or report bugs for rdrr.io? Use the GitHub issue tracker.