-
Notifications
You must be signed in to change notification settings - Fork 2
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
how to obtain the NO.case and NO.control #3
Comments
No.case and No.contr are total number of alleles in cases and controls at a genomic locus. These numbers are typically very small in rare variant analysis. Hope this helps. |
Hi, dear,
Is it true to obtain the NO.case and NO.control?
#NO.case
#grep 0/1
count_case_01 <- data.frame(apply(tmp_vcf_case_data,1,function(x) length(grep('0/1',x))))
rownames(count_case_01) <- tmp_vcf_case_data[,1]
colnames(count_case_01) <- "count_01"
#grep 1/2
count_case_12 <- data.frame(apply(tmp_vcf_case_data,1,function(x) length(grep('1/2',x))))
rownames(count_case_12) <- tmp_vcf_case_data[,1]
colnames(count_case_12) <- "count_12"
I am waiting for your response! Many Thanks!
…--
谭海珠
Haizhu Tan
汕头大学医学院
Shantou University Medical School
在 2021-03-13 04:54:25,"Shengtong" ***@***.***> 写道:
No.case and No.contr are total number of alleles in cases and controls at a genomic locus. These numbers are typically very small in rare variant analysis. Hope this helps.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I am not sure about your sample but the data is passed along to me from bioinformaticians. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear,
I still felt confused about how to obtain the NO.case and NO.control. You said that " (No.case, how many times the variant appears in cases, No.contr, how many times the variant appears in controls — you can compute these quantities from your data)". which file I can get this information. Can you give me an example?Thank you!
The text was updated successfully, but these errors were encountered: