-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OrderCpGsByLocation Fails for "bad" probe IDs #4
Comments
For documentation, the bad probes are:
Also, this function is missing a |
@tiagochst and @lxw391, are you ok with these changes? Should I add a warning if any of the probes are removed? |
…essary calls to data in inst/extdata per Issue #5
…essary calls to data in inst/extdata per Issue #5
…essary calls to data in inst/extdata per Issue #5
@gabrielodom it's ok to remove those CpGs, they are probably the ones masked by the sesame R package. You can read "How/Why Probes Are Masked?" at https://bioconductor.org/packages/devel/bioc/vignettes/sesame/inst/doc/sesame.html and this paper to understand more about the masking process https://academic.oup.com/nar/article/45/4/e22/2290930 . Check sesameDataGet('HM450.probeInfo')$mask to see the listed probes are included |
Thank you Lily! @fveitz, can you take a look at the masked probes and see if they match the bad probes we found? |
@fveitz, is this fixed? |
It's not a masking issue. Of the bad probes, only |
@gabrielodom it is not a annotation version problem ? |
Maybe changing |
Great idea! We have |
I think for HM450 there is only one version. |
When re-creating the data sets in
inst/extdata/
, I ran into the following bug. There are 19 probes included inIlluminaHumanMethylationEPICanno.ilm10b2.hg19::Other
which are not included in the corresponding sesameData manifest GRanges. When this happens, theOrderCpGsByLocation()
function fails with the error"Error: subscript contains invalid names"
. I am adding a check to remove probe IDs which are not contained in the manifest with an error if none of the probes are contained in that manifest.The text was updated successfully, but these errors were encountered: