![]() |
|
Matthew Speir
UCSC Cell Browser, Quality Assurance and Data Wrangler
Human Cell Atlas, User Experience Researcher
UCSC Genome Browser, User Support
UC Santa Cruz Genomics Institute
Revealing life’s code.
--
---
You received this message because you are subscribed to the Google Groups "UCSC Genome Browser Public Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to genome+un...@soe.ucsc.edu.
To view this discussion on the web visit https://groups.google.com/a/soe.ucsc.edu/d/msgid/genome/3F0434F7-B5C5-4C7E-B3EC-634FE4600E53%40newcastle.ac.uk.
![]() |
|
|
|
|
On Apr 21, 2022, at 11:02, Matthew Speir <msp...@ucsc.edu> wrote:
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
Hello, Tony.
Thank you for confirming the array.
Unfortunately, we cannot provide a precise timeline for when the 850k methylation array track would be released; however, the data is available as a custom track on h19:
http://genome.ucsc.edu/s/rhead/450k.EPIC.beadchip
The custom track has not been reviewed by our Quality Assurance team, so we ask to exercise caution. It would be great to get feedback if the custom track is helpful.
If you have any further questions, please reply to gen...@soe.ucsc.edu. All messages sent to that address are archived on a publicly-accessible Google Groups forum. If your question includes sensitive data, you may send it instead to genom...@soe.ucsc.edu.
Gerardo Perez
UCSC Genomics Institute
To view this discussion on the web visit https://groups.google.com/a/soe.ucsc.edu/d/msgid/genome/349836E6-594A-47BA-B714-7504772687A6%40newcastle.ac.uk.
![]() |
|
On Apr 25, 2022, at 19:25, Gerardo Perez <gpe...@ucsc.edu> wrote:
Hello, Tony.
Thank you for your inquiry.
We have updated the Illumina 450K/850K tracks and you should now be able to search for cg16791304 on the hg19 Genome Browser.
Thank you again for bringing this to our attention.
If you have any further questions, please reply to gen...@soe.ucsc.edu. All messages sent to that address are archived on a publicly-accessible Google Groups forum. If your question includes sensitive data, you may send it instead to genom...@soe.ucsc.edu.
Gerardo Perez
UCSC Genomics Institute
Warning/Error(s):
- Sorry, couldn't locate cg16791304 in Human Feb. 2009 (GRCh37/hg19)
Please see error message, I can see the track but can’t actually find the CpG
Any advice?
Thanks in advance
On 7 Sep 2022, at 09:28, Maximilian Haeussler <mhae...@ucsc.edu> wrote:
Hi Tony, please make sure that you are on the hg19 assembly. The EPIC array was only released on the hg19 (aka "Grch37") version of the human genome.
Are you sure that you can't find it?
Here is a direct link:
On Wed, Sep 7, 2022 at 4:21 PM Tony Sorial <Tony....@newcastle.ac.uk> wrote:
Hi Max,
I need to check if this is the correct array, is this the illumina EPIC CpG array
It still doesn’t seem to be working for me, are your team able to remotely add the track to my account?
BWTony
On 1 Sep 2022, at 05:16, Maximilian Haeussler <mhae...@ucsc.edu> wrote:
Hi Tony,
I think the track was released a few days ago, under "Variants" and "Microarray Probesets". See http://genome.ucsc.edu/cgi-bin/hgTrackUi?hgsid=1439656067_7IAgLFP4NdFnaMAIiaBTGEXH9wME&db=hg19&c=chrX&g=genotypeArrays
Does this solve your problem? What do you think of the track name - would you search under "microarray probesets" when looking for the 850k CytoSnp array?
bestMax
On Wed, Aug 31, 2022 at 11:35 PM Tony Sorial <Tony....@newcastle.ac.uk> wrote:
cg16791304
Hi team,
I am now struggling to find CpG’s on UCSC again, did we get any update on a timeline for the 850k (epic) array annotation
BWTony
I don't understand this. What do you mean with "exported from the array" - can one "export" from an array?We usually show the probes, not the CpGs. Do you want to see the targeted CpGs?What I mean is, when we get the data from a sample, we get a probe ID (for example cg14598846) and we also get a genomic location for the CpG, I think what you have already from the manufacturer means you don’t need anything from me!
If I was able to share that data with you would that help the process?
I don't understand either, sorry. We found the array probe file on the manufacturer's download server.see above
I will try the other file in the interim - we can double check it using the chromosomal location from the array export
Either 19 or 38 is fine, whichever is quickest
Do you need it for hg19 or hg38? The manufacturer only provides hg38 annotations at the moment.
Hope that clarifies, thanks again for your help
To view this discussion on the web visit https://groups.google.com/a/soe.ucsc.edu/d/msgid/genome/EE29024F-D553-4641-B74C-150D40C2B534%40newcastle.ac.uk.