-
Notifications
You must be signed in to change notification settings - Fork 4
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
Use embeddings to assemble link prediction classifier for human vs mouse phenotype equivalency. #6
Comments
@matentzn we need some mouse <-> human phenotype mappings for this OntoML project, and found this directory. Can you advise about whether we could use upheno_mapping_all.csv for this experiment? Basically what we need is a gold or silver standard of mouse - human phenotypes in order to train a link prediction classifier. I know you probably explained what each of these files is before and which to use, just making sure we use the right file. Thanks! |
Great you are getting to that :) Upheno at data.mi is outdated, use instead: https://bbop-ontologies.s3.amazonaws.com/upheno/current/upheno-release/all/upheno_mapping_all.csv Feel free to also plunder: https://github.com/mapping-commons/mh_mapping_initiative/tree/master/mappings Generally, whatever infrastructure you are building should prepare itself for reading mapping files in SSSOM format, like |
Great, thanks Nico! |
The gold standard phenotypes (as edges, filtered to just MP and HP) are now included as another transform, so they'll be on KG-Hub shortly. |
Whenever you output any mappings from any process, it would be great if you could consider publishing them in SSSOM, so we can process them further :) |
Absolutely, @matentzn - I decided to split off SSSOM generation/parsing into its own task here, but we'll definitely make them available. |
Sweet, because we are close to realising the sweet boomer dream, and your mappings will be very valuable, especially if they take into account graph structure! |
possibly hereNico says hereClassifiers to try:
In practice, all classifiers may be defined in a single NEAT config after implementing #5
The text was updated successfully, but these errors were encountered: