Skip to content
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

readmetharray force=TRUE #92

Closed
mwsill opened this issue Jan 25, 2017 · 6 comments
Closed

readmetharray force=TRUE #92

mwsill opened this issue Jan 25, 2017 · 6 comments

Comments

@mwsill
Copy link

mwsill commented Jan 25, 2017

Hi Kasper,

thanks for the hard work on the package. I am trying to read epic idats of different file sizes and I think you need to uncomment/delete line 58 in in read.meth.R to get the force=TRUE argument working?

Best,

Martin

@kasperdanielhansen
Copy link
Collaborator

You should only hit line 58 if you're trying to read data from different arrays (which is not supported and I don't intend to support it). The situation with data from scans with different lengths of the same array is different; thats what we support.

Perhaps tell us more details or give two files as example.

@mwsill
Copy link
Author

mwsill commented Jan 25, 2017

The file sizes are 13677911 instead of 13686979 and the number of probes are 1051943. Setting the annotation manually to "ilm10b2.hg19” works fine, however around 600 CpG probes are missing. The same probes seem to miss when reading the idat files with GenomeStudio.
I sent you an email with more details and an idat pair.

@kasperdanielhansen
Copy link
Collaborator

Fixed in minfi 1.21.6. It will take a few days before it appears on the Bioconductor servers.

@mwsill
Copy link
Author

mwsill commented Apr 19, 2017

Thanks, I think the problematic probes are excluded by the new Illumina manifest released today.

@kasperdanielhansen
Copy link
Collaborator

kasperdanielhansen commented Apr 20, 2017 via email

@marencc
Copy link

marencc commented May 12, 2017

I'd like to ask why would scans of different lengths happen? As it seems to be a constant case if EPIC's arrays [+Isn't it supposed to be all done uniformly by a machine? ]

The situation with data from scans with different lengths of the same array is different; thats what we support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants