-
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
Disappearing URS #902
Comments
…blems, but why not fix; tagging on to geneontology/noctua#902 as that's when I found it
Okay, to unpack this a little, this entity still seems to be showing up, at least in a test build I did locally and in NEO (http://noctua-amigo.berkeleybop.org/amigo/term/URS000012F9EC_9606). It could just be a sync issue where these temporarily dropped out and have been re-added (assuming that https://ftp.ebi.ac.uk/pub/databases/RNAcentral/current_release/gpi/rnacentral.gpi.gz is the right upstream). I think it might be best to wait until the next noctua outage and see if this has "improved". All that said, I think that there is still discussion on how to handle RNAcental (even putting aside that the actual information present is scarcely more informative than null information, see |
Thanks @kltm will check in again after next outage. |
@kltm this is still not resolved. Could you give it a look over? |
@hattrill Okay, looking at the link again, it does seem to "be there", but is missing a namespace. This means that either the GPI/GAF that this information is coming from is messed up, or that the processing of the same is messed up. I'll need to look into this a bit more. |
Origin likely
Hm...this looks right. Checking processing next. Trying to duplicate with
but it looks good locally. Cleaning workspace and retrying. |
Also checking target/neo-rnacentral.obo; it looks okay too. Re-running in the side pipeline, I can confirm that the issue persists. |
I can confirm that we have it in This is beginning to look like maybe an I believe I have traced it to this one: @balhoff I don't suppose you have an instict for what may go off the rails here, before I dig in? Can we replace with robot maybe instead? |
@kltm I know what's going on. It's due to the OBO prefixes support, which has been a lot more trouble than I expected. It's especially bad here because the NEO build is full of prefix hacks. The new prefix support would actually work really well for this, but not sure how much revamping we want to do. We can either embrace it and use the newest ROBOT, or revert to an earlier build of owltools. Or actually an earlier build of ROBOT would work as well, just need to update the command lines. |
@balhoff Hm. While I am game for any of the above that fixes the problem, my druthers would be starting with things that move us "forward", if not too spendy timewise. I'm happy to give some robot commands a try to see if they give us the results that we want. neo.obo: $(OBO_SRCS) $(IMPORTS)
owltools --create-ontology http://purl.obolibrary.org/obo/go/noctua/neo.owl $^ --merge-support-ontologies -o -f obo $@.tmp && grep -v ^owl-axioms $@.tmp > $@ with |
@balhoff I tried to roll my own, but it didn't work like I'd expect:
I still get
I this because I haven't used the "prefix support" you mentioned above? |
@kltm here is what I had in mind: geneontology/neo#119 |
@balhoff Great--I see what's going on there. I guess it's still WIP, but that's an exciting development! |
Can we get this fixed? Would be nice to show functional models to RNAcentral! |
@hattrill this is in progress over here: geneontology/neo#121 |
Changes from geneontology/neo#121 require robot in the pipeline. |
@balhoff Will be looking at a little more work needed for handling some pipes in the data stream. This will hopefully be completed before the next outage. |
@balhoff put in a couple more change and, with a couple of pipeline adjustments, the build is running through again. @vanaukenk We should consider what we think qualifies as testing and how we do it. The spectrum runs from "check when we roll out next time" to "make a new amigo instance and compare". |
This now seems to exist (as hoped): http://noctua-amigo.berkeleybop.org/amigo/term/RNAcentral:URS000012F9EC_9606 |
All fixed. Thanks. I'll close this now. |
I have two models in which RNAcentral IDs were used - they are now showing "GP info not available" in the list view or in the pathway editor but I can see them in the form editor. Both IDs are current and they were 'present and stable' the last time I looked at these models a few weeks ago.
Model ID 654d809000000802
gp: URS000012F9EC_9606
Model ID 66187e4700001274
gp: URS000075C624_9606
The text was updated successfully, but these errors were encountered: