Rebecca
--
You received this message because you are subscribed to the Google Groups "UCSF EGAN" group.
To post to this group, send email to ucsf...@googlegroups.com.
To unsubscribe from this group, send email to ucsf-egan+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ucsf-egan?hl=en.
Hi Jesse,
I am using an Illumina mouse microarray. I have both target ids and probe ids. I get the same result using either one.
Probe ids look like
ProbeID | logFC | P.Value |
870465 | -0.3537 | 1.21E-07 |
3190307 | 0.393937 | 2.85E-07 |
1940731 | 0.470578 | 5.01E-07 |
3120133 | -0.35577 | 7.20E-07 |
2070673 | 0.526229 | 9.98E-07 |
1690678 | 0.594751 | 1.16E-06 |
Target ids look like
targetID | logFC | P.Value |
0610005C13RIK | -0.3537 | 1.21E-07 |
0610005I04 | 0.393937 | 2.85E-07 |
0610006I08RIK | 0.470578 | 5.01E-07 |
0610006I08RIK | -0.35577 | 7.20E-07 |
0610006L08RIK | 0.526229 | 9.98E-07 |
I have been using the Illumina Mouse WG v1 (or2) for the mapping file. I have tried both. I have used the same file for the background.
Rebecca
Hi Jesse,
It seems that Illumina changes naming conventions periodically. However, Entrez GeneIDs do work. Thank you very much.
You're welcome. Also I forgot to mention that EGAN readily accepts custom mapping files for ID types that aren't currently mappable.