Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Using non-harmonized version #399

Closed
scienception opened this issue Dec 18, 2024 · 1 comment
Closed

Using non-harmonized version #399

scienception opened this issue Dec 18, 2024 · 1 comment

Comments

@scienception
Copy link

scienception commented Dec 18, 2024

Is it ok to use the non-harmonized version of the PGS files? Or does pgs_calc expect exclusively this format?

Screenshot 2024-12-18 at 15 11 42

I ask cause I developed my own PGS and don't have any info on hm_source, hm_rsID, hm_chr, hm_pos or hm_inferOtherAllele. Only on rsID, chr_name, chr_position, effect_allele, other_allele, effect_weight.

Will pgs_calc accept this format?

@nebfield
Copy link
Member

You can use your own PGS by following this guide:

https://pgsc-calc.readthedocs.io/en/latest/how-to/calculate_custom.html#scorefile-setup

Your PGS scoring file needs a special header and some standard column names to be compatible

@PGScatalog PGScatalog locked and limited conversation to collaborators Jan 6, 2025
@smlmbrt smlmbrt converted this issue into discussion #401 Jan 6, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants