-
Notifications
You must be signed in to change notification settings - Fork 12
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
Update MF-MF relations in existing models #813
Comments
@vanaukenk here's some counts for existing data. The different rows may overlap (e.g., "molecular_function" counts all instances of "molecular_function" subjects with the given predicate). The object (not in the table) is always some instance of "molecular_function". ?subject_type ?subject_type_label ?p ?p_label ?triples
<http://purl.obolibrary.org/obo/GO_0003674> "molecular_function" <http://purl.obolibrary.org/obo/RO_0002213> "positively regulates" "1515"
<http://purl.obolibrary.org/obo/GO_0003674> "molecular_function" <http://purl.obolibrary.org/obo/RO_0002212> "negatively regulates" "577"
<http://purl.obolibrary.org/obo/GO_0001216> "DNA-binding transcription activator activity" <http://purl.obolibrary.org/obo/RO_0002213> "positively regulates" "49"
<http://purl.obolibrary.org/obo/GO_0030371> "translation repressor activity" <http://purl.obolibrary.org/obo/RO_0002212> "negatively regulates" "1"
<http://purl.obolibrary.org/obo/GO_0003674> "molecular_function" <http://purl.obolibrary.org/obo/RO_0002211> "regulates" "27"
<http://purl.obolibrary.org/obo/GO_0001217> "DNA-binding transcription repressor activity" <http://purl.obolibrary.org/obo/RO_0002212> "negatively regulates" "2"
<http://purl.obolibrary.org/obo/GO_0001217> "DNA-binding transcription repressor activity" <http://purl.obolibrary.org/obo/RO_0002213> "positively regulates" "1" |
Cool. Thanks @balhoff |
I updated the replace relations tsv to include 'directly activates' and 'directly inhibits' in the list of relations to update. |
Talking with @ukemi and @pgaudet this morning, we think it would be very helpful to have a list of the model ids that will be affected by the MF-MF relations replacement as well as the ProvidedBy value for each model. The overall numbers seem a bit higher than we might have expected, so it'd be good to know exactly what will be touched if we do this. This would also help us communicate with relevant groups about the upcoming changes. Thank you! |
@vanaukenk here's a new query output: https://docs.google.com/spreadsheets/d/1wGwXS6Kc7zWvmCvp4HwC-8AjHNUYn12etLyun3osOZI/edit?usp=sharing Let me know if you'd like any modifications. |
Fantastic! Thanks very much @balhoff |
We'll need the SPARQL and instructions, but can put it in on Monday or Tuesday at short notice. |
@kltm @vanaukenk sorry for the delay—I will try to get the SPARQL to you later today. |
@vanaukenk clarification about |
And what about |
In theory, yes, the subject type would matter here, too. In practice, I don't know how many models actually use 'directly activates' and/or 'directly inhibits'. If it's not too much trouble, I could take a look at any models using those two relations to see if we need to be more specific about the subject for the updates.
Yes, for regulates without a directionality we would have to update to directly or indirectly depending on the subject type. I could also take a look at these models, but suspect there are more of them than the directly activates and directly inhibits models. For future GO-CAM reports, it would be nice to know how many models use the regulates relation without directionality since we would want curators to review those and chose a more granular relation. |
I think this is wrong; will confirm shortly. |
@vanaukenk here are the directly activates/inhibits models: https://docs.google.com/spreadsheets/d/1FRGgUliwUpxc7AUMwTKjAxmnuXslgwkmTEU9M1vZ7HE/edit?usp=sharing It doesn't look like any of them use your special-case classes. I initially didn't find any because there was no label for those relations (they are obsolete and weren't loaded). |
Thanks for the spreadsheet @balhoff I've checked all the models and, with two exceptions that should be manually updated, I think we are okay to bulk update the models that use 'directly activates' and 'directly inhibits'. The two that should be reviewed manually are: |
I'm checking models on noctua-dev. So far, the updates for the negatively regulates relation between MFs look okay, but for the positively regulates relations, it looks like the existing relation isn't getting deleted and the new relation is just getting appended. Here's a view (the relations are overlapping a bit in the view, but both are there): |
Also, what happens to the evidence on the relation when we update? On noctua-dev it looks like we might be losing it :-( |
Here's a simpler example from http://noctua-dev.berkeleybop.org/editor/graph/gomodel:a1a2a3a402 |
Thanks for checking the output—I updated the query to fix this problem. |
Hi - there's another thing I'd like to double-check. In cases where we have a replacement for a more specific MF, e.g. DNA-binding transcription activator activity, RNA polymerase II specific (GO:0001228), it looks like we are getting two relations: one direct and one indirect. Here's a model on production (http://noctua.geneontology.org/editor/graph/gomodel:5fa76ad400000000): and here's what it looks like on noctua-dev (http://noctua-dev.berkeleybop.org/editor/graph/gomodel:5fa76ad400000000): The 'indirectly positively regulates' relation is the one we want in this case. |
…ates_conditional_replacement.ru; for geneontology/noctua#813
This is a stub ticket for starting to spell out the steps we'll need to take to update MF-MF relations in existing models as a result of the work on the MF Relations Project.
Generally, the work that needs to be done is:
The text was updated successfully, but these errors were encountered: