You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After looking at the source code, it seems that you use the default settings of sort() which order a GRanges object first by seqnames, then by strand, then by start, and finally by width.
As the identified co-methylated CpGs are not always in the same strand, when you try to get the region name, using the default sort() will lead to some regions having start greater than end.
I need to add this ignoreStrand argument to any function in coMethDMR:: that calls OrderCpGsByLocation() directly or indirectly. So far, we have only fixed: GetCpGsInRegion(), lmmTest(), lmmTestAllRegions(), OrderCpGsByLocation(), and WriteCloseByAllRegions().
Hi,
I realized that some start positions are bigger than the end positions in the results from
lmmTestAllRegions
. For example, one of my results:Following the extract of
EPIC.hg19.manifest
from sesameData for the 4 CpGs in region:After looking at the source code, it seems that you use the default settings of
sort()
which order a GRanges object first by seqnames, then by strand, then by start, and finally by width.coMethDMR/R/util1_OrderCpGsByLocation.R
Lines 54 to 56 in 34553b9
As the identified co-methylated CpGs are not always in the same strand, when you try to get the region name, using the default
sort()
will lead to some regions having start greater than end.coMethDMR/R/lmmTest.R
Lines 99 to 103 in 34553b9
Will you consider to use
sort(..., ignore.strand = TRUE)
to eliminate this problem?The text was updated successfully, but these errors were encountered: