-
Notifications
You must be signed in to change notification settings - Fork 1
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
Adjusting signals of Agilent file fails #2
Comments
This is due to the
The |
Hi Luca, Thanks for reporting me this bug. I just checked on the Agilent demo file provided with the package and everything works well:
Scaling... Can you please check whether you have ‘gMedianSignal’ and ‘rMedianSignal’ in your input file. These values are used to compute the Log2Ratio and the corresponding column is created at this step. Fred Le 6 juin 2016 à 10:51, Luca Beltrame notifications@github.com a écrit :
|
Yes, the file has been generated by Agilent CytoGenomics 3 (FE does not process CGH arrays, at least not the most recent versions). And both columns are present in the file. Where in the code is the Log2Ratio calculated? I see the code explicitly skips the Log2Ratio column in the feature extracted files. |
For reference:
(Probe IDs are different because this chip is manufactured by Agilent for another supplier). |
I've done a bit of debugging: This chip is made by Agilent for Oxford Gene Technology (OGT). So FE / CytoGenomics will actually process it correctly, but the problem is that the probes will not match in
The workaround is to disable GC correction, but likely this needs to be taken into account (i.e. the case where both |
Oh I see. Sorry for the inconveniences it may have caused, 2016-06-06 11:39 GMT+02:00 Luca Beltrame notifications@github.com:
|
|
Right ! :) 2016-06-06 12:12 GMT+02:00 Luca Beltrame notifications@github.com:
|
The text was updated successfully, but these errors were encountered: