-
Notifications
You must be signed in to change notification settings - Fork 0
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
Quality control protocol for TWAS #2
Comments
QC, Normalization, and batch effect correction of RNASeq data for TWASReference: NIHMS1518564, detailed protocol they used are included. This article summarized the RNASeq QC and data preprocessing steps to be feed into TWAS. For RNASeq data that passed the initial fastQC procedures, they shall be normalized into CPM via TMM and then passed into sva comBat procedure to control for batch effect. The outcome then can be feeds into the FUSION for weight generation and TWAS Target for Input to the TWAS pipeline:RNA Seq data:
SNP data: For each gene, all the SNPs [within 1 Mb of its start or end site] (Optional) that had GWAS statistics RNA Seq data preprocessing protocolsRNA-seq and genotyping quality control
SSVA-corrected expression data (Batch correction)
|
What ROSMAP eQTL analysis did for covariates, according to Annie Lee at Columbia Neurology, is the following:
|
Turns out the reason they dont control for hidden covariates are:
@hsun3163 I think we can possibly get away with just using these explicit technical variables for reasons discussed above. However I think we should add one more explicit covariate -- Alzheimer's disease status. Because if some SNPs are correlated with AD status, and if some gene experssion are also correlated with AD status, then conditional on AD status the SNP and expression should not have a correlation, thus the SNP is not an eQTL. However without controlling for AD status the SNP will have a spurious association with the expression level. This would not be a concern if we use SVA type of analysis because some factors learned should already capture and account for AD status. When we use explicit features we just have to be more careful. |
@hsun3163 no rush but let's organize this into a notebook as you revamp your repo, then close the issue. We can visit this after next week. |
No description provided.
The text was updated successfully, but these errors were encountered: