-
Notifications
You must be signed in to change notification settings - Fork 49
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
Addresses #1582-NTR-epithelial_cells_DCT #1644
Addresses #1582-NTR-epithelial_cells_DCT #1644
Conversation
Here's a diff of how these changes impact the classified ontology (on -simple file):Ontology comparisonLeft
Right
Ontology importsOntology annotationsCL_4030016
|
Here's a diff of your edit file (unreasoned)Ontology comparisonLeft
Right
Ontology importsOntology annotationsCL_4030016
|
Just to double - check early and late are segments and not time right? lol |
Thank you for the suggestion, @shawntanzk. I found that the UBERON terms already existed, but would need to be imported to CL. |
…into 1582-NTR-epithelial-cells-of-distal-convoluted-tubule
@@ -142,6 +142,9 @@ | |||
<Class rdf:about="http://purl.obolibrary.org/obo/CL_0000381"> | |||
<oboInOwl:hasDbXref rdf:datatype="http://www.w3.org/2001/XMLSchema#string">FBbt:00005130</oboInOwl:hasDbXref> | |||
</Class> | |||
<Class rdf:about="http://purl.obolibrary.org/obo/CL_0000850"> | |||
<oboInOwl:hasDbXref rdf:datatype="http://www.w3.org/2001/XMLSchema#string">FBbt:00005133</oboInOwl:hasDbXref> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gouttegd - could you help make sure this is correct - I think it got updated with import updates
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That’s correct, yes. It’s a change that I made recently in the FBbt-to-CL mappings. That it got picked up during an import update is the expected behaviour, I believe.
It all looks good - the file changes I'm not sure about but its not anything on you, I've asked @gouttegd to look at them to make sure they are right as its fly stuff. But basically you did everything right with imports :) |
@shawntanzk, I resolved 9 conflicts in the merged_import.owl file, but most were arbitrary decisions. I would not know another way to approach it and do not know why so many conflicts appeared. If we there is a way to test that I did not make any breaking changes, pls advise. FYI, @matentzn. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All looks great - I am a bit puzzled but they fact that the components are refreshed although you just refresh the imports. What exact command did you run in the end?
@bvarner-ebi - I think you can make equivalent classes and in fact I think you should follow exactly the the textual definition states and let the reasoner do the work (of course making sure the reasoner works, if not figuring out why). so: epithelial cell of early distal convoluted tubule This should automatically place it under "kidney distal convoluted tubule epithelial cell" (if not we should look at where the modelling is wrong, or if your def needs to be edited, not sure if early distal convoluted tubule has kidney part, not sure of the biology) PS - sorry for being annoying and not bringing this up earlier >.< just realised. |
@bvarner-ebi there should never be any conflicts on imports. The only way this can happen is if you opened a new branch, and someone else came to update the import before you, and then you didn't update your branch from master first. Generally:
I suggest you rerun: |
|
OK in the end it makes sense! All good. But I would still recommend rerunning the command i suggest above - never resolve conflicts on imports, always rerun! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All changes regarding the FBbt-CL mappings are normal and expected.
Unless I’m missing something, I believe this is normal. Components are listed in OTHER_SRC = $(PATTERNDIR)/definitions.owl $(COMPONENTSDIR)/hra_subset.owl $(COMPONENTSDIR)/mappings.owl
|
Steps I'm now doing:
|
Great suggestion. I updated that in the latest commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see inline (just last bit of tidying up :))
No need: |
OK. I was following the advice from Slack: "CL uses merged import so you want to run sh run.sh make imports/merged_import.owl" https://oboacademy.github.io/obook/howto/update-import/#Refresh-imports |
@bvarner-ebi I think in the general case, the instructions on obook are fine for the general case - |
Thanks for explaining. |
Can you make an obook issue about this I will deal with it asap |
Addresses #1582-NTR-epithelial_cells_DCT