Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
EPIC GWAS IMPORT ERROR #50
I've been having fevery dreams these last couple of weeks, and I suddenly realized why. The import used one idiotic assumption when loading the GWAS. That each study only references a single disease. This, in retrospect, is obviously not the case, given that multiple GWAS correlations could possibly be identified in a study.
This means that each study now has a list of diseases they reference, instead of just one, and each disease now has many more studies to reference (possibly).
In other words, there is actually a many-to-many relationship between disease and study, whereas the old model only had a one disease to many studies relation.
Since this fix obviously has implications on how we search for studies, I wanted to give @wejendorp a heads up. Since the "disease_trait" field is no longer there, replaced by an array of disease_keys (I could add an additional disease_names string-array if that would simplify things?), you can no longer index the disease-field of the study. For now I've simply commented out that field in your indexing, and I couldn't figure out how to add indexing for arrays.
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
Agreed, just want to be sure Jacob understands what happens to the indexer
Patrick-Ranjit D. Madsen
Sent from my mobile. Please excuse any and all typos, errors,
On 01/06/2012, at 20.20, jensraaby