Do we need to remove relatives for PRS calculation??
1
1
Entering edit mode
5.1 years ago

Is it needed to remove people who are relatives in a sample for polygenic risk score calculation??

SNP PRS Polygenic Rsik score • 1.5k views
ADD COMMENT
0
Entering edit mode

Risk is calculated based on SNPs of an individual, why it would it matter if they have relatives?

ADD REPLY
0
Entering edit mode

That's right. But does it bias the calculated r-squared for the explained variance?

ADD REPLY
0
Entering edit mode

Depending on how you are calculating your PRS, why not just do a family-specific statistical test and derive the PRS from the coefficients of that?

ADD REPLY
0
Entering edit mode

Thanks Kevin, would you please give me more details on how to do that? Maybe a link to a paper?

ADD REPLY
1
Entering edit mode

Well, most PRS that I have seen are simply derived from the beta coefficient of a fitted regression model. The Beta coefficient is the 'Estimate' that appears in the output when you run Summary() on your model object (in R). So, I do not have any to which to link you as it is simply used in all PRS that I have seen, possibly even PRSice.

ADD REPLY
1
Entering edit mode

Keep in mind that there is no single definition for PRS... it is as general and 'broad-sweeping' a term as 'bioinformatics'.

ADD REPLY
3
Entering edit mode
5.1 years ago
Sam ★ 4.7k

Most of current PRS tools (PRSice, lassosum and LDpred) does not support family data. For example, in PRSice, a simply linear regression or glm is used to calculate the P-value and R2 whereas lassosum use correlation between the PRS and phenotype. What this mean is that the relatedness between the samples might artificially inflate your R2 and might lead to a higher level of overfitting, limiting the generalisability of your findings to other dataset

ADD COMMENT

Login before adding your answer.

Traffic: 1701 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6