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

EPIC V2 to EPIC V1 #272

Open
PierreSolomon opened this issue Apr 23, 2024 · 12 comments
Open

EPIC V2 to EPIC V1 #272

PierreSolomon opened this issue Apr 23, 2024 · 12 comments

Comments

@PierreSolomon
Copy link

Hello,

I have methylation data from the EPIC V2 array and I wish to deconvolve it (to the different PBMC cell types). My problem is that all the packages I found that deal with deconvolution of methylation data only support 450k and EPIC (EPIC V1) array.

Is there a way to use / modify the convertArray function to convert an RGChannelSet of a EPIC V2 array to a RGChannelSet of the EPIC V1 array?

@kunstner
Copy link

Same problem here. Do you have any solution to convert EPIC V2 to V1 arrays?

@Pierre9344
Copy link

I managed to convert the EPIC v2 id using the sesame R package. There is a liftOver function: https://github.com/zwdzwd/sesame/blob/2d5c2ab371430a8ecb1b5f09792457505a59d192/R/impute.R#L44

@simonjuleseric2
Copy link

Could you please share the process?

@kunstner
Copy link

The process is implemented in the SeSAMe package. Haven't tried it myself yet but it looks straight forward.

https://doi.org/10.1093/bioinformatics/btae423

I mapped the probes using the annotation files in R. It seems this workflow is suitable for my dataset.

@kostaslazaros
Copy link

Hello everyone!

I want to do the same process; convert EPIC V2 to EPIC V1 arrays so that I can use/combine data together at the end.

I have seen the function from the SeSAMe package and it is really interesting. However a point of confusion for me is the data types; Minfi uses RgSet while SeSAMe uses SigDF.

Is there a way to easily convert from one data type to the other?

@kunstner
Copy link

kunstner commented Jul 19, 2024

I convert the EPICv2 Probe names to EPICv1 after I performed SWAN normalization. I process v1 and v2 arrays separately. Afterwards, I just merge the b and M values.

Assuming you have imported your data using read.metharray.exp you can do something like this

dat <- preprocessRaw(rgSet_v2)
mSetSq_v2 <- preprocessSWAN(rgSet_v2, mSet = dat, verbose = TRUE)

Next, rename the probes

rownames(mSetSq_v2) <- gsub('_BC[0-9][0-9]', '', rownames(mSetSq_v2))
rownames(mSetSq_v2) <- gsub('_TC[0-9][0-9]', '', rownames(mSetSq_v2))

From here, you can extract b/M.

@kostaslazaros
Copy link

Many thanks for the quick response!

I am trying to "downgrade" from EPIC V2 to EPIC V2 through the mLiftOver function from Sesame.

My main point of confusion so far is the data type.... is there a way to turn a list of sigDFs into an RGSet ?

@ralanany
Copy link

I convert the EPICv2 Probe names to EPICv1 after I performed SWAN normalization. I process v1 and v2 arrays separately. Afterwards, I just merge the b and M values.

Assuming you have imported your data using read.metharray.exp you can do something like this

dat <- preprocessRaw(rgSet_v2) mSetSq_v2 <- preprocessSWAN(rgSet_v2, mSet = dat, verbose = TRUE)

Next, rename the probes

rownames(mSetSq_v2) <- gsub('_BC[0-9][0-9]', '', rownames(mSetSq_v2)) rownames(mSetSq_v2) <- gsub('_TC[0-9][0-9]', '', rownames(mSetSq_v2))

From here, you can extract b/M.

Is it possible to normalize before we combine the data??? Is there reference to do this?

@ralanany
Copy link

Thanks for your comment: Is it possible to normalize before we combine the data??? Is there reference to do this?

@kunstner
Copy link

Depending on your workflow, you can normalize the data before merging the datasets. For normalization, just follow the steps described in the vignette:

https://bioconductor.org/packages/devel/bioc/vignettes/minfi/inst/doc/minfi.html

@ralanany
Copy link

Thanks for your prompt reply, but to my knowledge we have to normalize all the data at the same time to remove the background noise from all samples together. I s there reference or published paper with this work flow?
Thanks again

@kunstner
Copy link

We use SWAN normalization on each platform separately before we merge the data. Afterward, it is important to assess the data with respect to potential batch effects. So far, this worked nicely for us but it always depends on the data.

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

6 participants