-
Description of the bugSome scores, such as PGS000026, have SNPs which lack rsIDs and positions. How does pgsc_calc handle these situations? Is an error thrown? (I don't believe so.) Is the score simply calculated without using the locations? Example:
Command used and terminal outputNo response Relevant filesNo response System informationNo response |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
It seems like it simply skips the SNPs, and says "unmatched" in the log file. However, it does not set "exclude" to true. This is less important for scores which have a small % of SNPs matching most of the time, unless, like in this case, the missing SNPs have by far the largest effect size. A workaround would be to fix the scorefile and then use a custom scorefile. |
Beta Was this translation helpful? Give feedback.
-
If a SNP is skipped (e.g. to a problem in the genome file), is it also skipped in the reference genome score calculation? |
Beta Was this translation helpful? Give feedback.
-
Scoring files submitted to the PGS Catalog are harmonised to include missing optional fields like genomic coordinates and e.g. for PGS000026: https://ftp.ebi.ac.uk/pub/databases/spot/pgs/scores/PGS000026/ScoringFiles/Harmonized/ By default if you use Matching only ever uses genomic coordinates and allele information (rsids are never used). |
Beta Was this translation helpful? Give feedback.
-
Got it. For this example, I believe it will skip APOE e2 and e4 as there are no coordinates, and simply calculate the score without it. |
Beta Was this translation helpful? Give feedback.
-
Correct, there are other ways to genotype APOE and enter it into your genotyping data. If you know which is the e2/e4 allele in your data you could customise the scoring file so that it will match the |
Beta Was this translation helpful? Give feedback.
Correct, there are other ways to genotype APOE and enter it into your genotyping data. If you know which is the e2/e4 allele in your data you could customise the scoring file so that it will match the
chrom:pos:ref:alt
in your dataset and it should be included as a match.