morbidmap.txt
: Cases where same MIM# is mapped to (i) a phenotype MIM# and (ii) a plain label
#86
Labels
analysis
Not a feature or update to the core of the repository, but an ad hoc analysis.
Overview
Hey @sabrinatoro , I wanted you to take a look at this for me. While I was coding, I remembered something you said and I wanted to check for an edge case. I believe you mentioned at the meeting yesterday that, in rows where the
Phenotype
column has no MIM# in it, the MIM# in theMIM Number
column is not actually a gene MIM (which is usually the case), but is a phenotype/disorder MIM. I hope I got that correct.Specific case
Here's an example of such a row (
OMIM:100650
):However, for
OMIM:100650
there are also 2 rows where it is mapped to aPhenotype
field with no MIM# inside of it. Here's all the rows whereOMIM:100650
appears in theMIM Number
column:Question
I think this conflicts with the hypothesis I mentioned in "Overview". So I'm wondering which is true: (a) In cases where there is no MIM# in
Phenotype
field, the MIM# in theMIM Number
field will always be a phenotype/disorder, and not a gene, (b) same thing as a, but replace the word 'always' with 'sometimes', (c) the MIM# in theMIM Number
field is indeed always a gene.Data
I found all such similar cases and created a TSV: morbidmap cases of mim mapped to both another mim and a plain label.tsv.zip
The text was updated successfully, but these errors were encountered: