-
Notifications
You must be signed in to change notification settings - Fork 42
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
question about PEER_update #16
Comments
Hello,
thank you for the report. Ricard (cc-d) has folded PEER into the
multi-omics factor analysis (MOFA) framework as described below - we
recommend using this going forward, as it is properly supported, and it may
resolve your issues.
Leo
From Ricard:
Running MOFA (https://github.com/bioFAM/MOFA2) with one view is
effectively PEER. We have also added functionalities and visualisations to
interpret the factors before regressing them out for eQTL mapping or any
other downstream analysis.
I’ve built a wrapper here:
https://github.com/bioFAM/PEER
Let me know if you have any questions. We have a Slack channel where I
provide individualised help. The link is in the MOFA2 github.
We have not made the official release yet as we would like to get some
feedback how this is working and how intuitive this is. Please let me know
about your experience
Best,
Ricard.
…On Fri, Feb 18, 2022 at 12:59 PM hust-yyan ***@***.***> wrote:
Hello, I encountered the following bug when running R-peer again
[image: image]
<https://user-images.githubusercontent.com/54279739/154687130-c40201e1-5ddd-40f3-9a45-994e7fb4c63d.png>
this is my code:
library(peer)
load("/data1/shiyan_data/plasma.miRNA.eqtl.RData")
model = PEER()
PEER_setPhenoMean(model,as.matrix(t(counts)))
covs<-sampleinfo[,c("Sex","Age","BMI","Smoking","hypertension","hyperlipidemia","Diabetes")]
covs<-apply(covs,2,as.numeric)
rownames(covs)<-sampleinfo$ID
PEER_setCovariates(model, as.matrix(covs))
PEER_setAdd_mean(model, TRUE)
PEER_update(model)
—
Reply to this email directly, view it on GitHub
<#16>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADIQI2NR3WHFHU7SK62ICTU3Y7BHANCNFSM5OX2WAMA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hello, I saw this link (https://github.com/bioFAM/PEER), I have a question, in the case of using MOFA2 to perform PEER analysis is not considering the influence of other known covariates? |
Ricard - how would you recommend using PEER in MOFA2 with covariates? Is
there perhaps a vignette that could be adapted?
Leo
…On Fri, Feb 18, 2022 at 1:42 PM hust-yyan ***@***.***> wrote:
Hello, I saw this link (https://github.com/bioFAM/PEER), I have a
question, in the case of using MOFA2 to perform PEER analysis is not
considering the influence of other known covariates?
—
Reply to this email directly, view it on GitHub
<#16 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADIQI5LNTTHX5OMA6I2OHLU3ZECVANCNFSM5OX2WAMA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
[copying Ricard as well]
On Fri, Feb 18, 2022 at 1:43 PM Leopold Parts ***@***.***>
wrote:
… Ricard - how would you recommend using PEER in MOFA2 with covariates? Is
there perhaps a vignette that could be adapted?
Leo
On Fri, Feb 18, 2022 at 1:42 PM hust-yyan ***@***.***>
wrote:
> Hello, I saw this link (https://github.com/bioFAM/PEER), I have a
> question, in the case of using MOFA2 to perform PEER analysis is not
> considering the influence of other known covariates?
>
> —
> Reply to this email directly, view it on GitHub
> <#16 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AADIQI5LNTTHX5OMA6I2OHLU3ZECVANCNFSM5OX2WAMA>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, I encountered the following bug when running R-peer again
this is my code:
library(peer)
load("/data1/shiyan_data/plasma.miRNA.eqtl.RData")
model = PEER()
PEER_setPhenoMean(model,as.matrix(t(counts)))
covs<-sampleinfo[,c("Sex","Age","BMI","Smoking","hypertension","hyperlipidemia","Diabetes")]
covs<-apply(covs,2,as.numeric)
rownames(covs)<-sampleinfo$ID
PEER_setCovariates(model, as.matrix(covs))
PEER_setAdd_mean(model, TRUE)
PEER_update(model)
The text was updated successfully, but these errors were encountered: