opentargets / issues

Issue tracker for Open Targets Platform and Open Targets Genetics Portal
https://platform.opentargets.org https://genetics.opentargets.org
Apache License 2.0
12 stars 2 forks source link

validate_lead_pvalue in study locus fillters all StydyLoci but it shouldn't #3529

Closed addramir closed 1 month ago

addramir commented 2 months ago

validate_lead_pvalue flaggs all CSs. However it is possibile to have secondary signal CSs from SuSiE with lead variants <1e-6 and it is valid. The easiest fix is to have separate thresholds for PICS (genome-wide significant) and SuSiE (for example 1e-5 or 1e-6).

d0choa commented 2 months ago

We must make the validate_lead_pvalue method in StudyLocus, conditional to the finemappingMethod.

DSuveges commented 2 months ago

Oh, I really don't like the idea: the checks performed on the aggregated data should be applicable on the full dataset. If different sources have different expectations to comply, then these checks should be performed at the source. I know doing qc is more ideal in one place, but this is not really a qc on the credible set object as a whole, rather a qc on the susie or the pics-ed credible sets.

(Not to mention how much more complicated this function would become)

addramir commented 2 months ago

In this case, this filter should be dropped from the QC and added to data specific postprocessing.

d0choa commented 2 months ago

Agreed. @addramir if you can scope the datasource-specific logic we could close this ticket

addramir commented 2 months ago

https://github.com/opentargets/gentropy/pull/788