Skip to content
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

accessing all annotated GO terms IDs (Including ancestors) for a gene programatically #22

Closed
ValWood opened this issue Jun 6, 2017 · 6 comments

Comments

@ValWood
Copy link

ValWood commented Jun 6, 2017

One of our users has asked how to do this as part of some protein-protein interaction prediction method.

I have seen it answered previously on the GO helpdesk more than once but I don't see it in the FAQ . Could it be added?

Thanks,

VAl

@ValWood
Copy link
Author

ValWood commented Jun 8, 2017

Hi,

Can anyone help with this? @cmungall
I know I have seen this question answered on Jira, but I don't think this archive is available.

The user has mailed our helpdesk again, and I am on vacation so I don't want it to slip through the cracks.

The user mentioned using python.... but I guess any method would do...

@cmungall
Copy link
Member

cmungall commented Jun 8, 2017

python, perfect. We can demonstrate this with a notebook like this: https://github.com/biolink/ontobio/blob/master/notebooks/Remote_Ontology.ipynb

I'd like to build up a large library of these notebooks as part of our FAQ (and they can easily be replicated as simple scripts).

@dougli1sqrd can you take this one? I can help. Let's do PomBase:SPBC11B10.09 as our example. I'll start it off.

cmungall added a commit to geneontology/go-notebooks that referenced this issue Jun 8, 2017
@cmungall
Copy link
Member

cmungall commented Jun 8, 2017

@ValWood
Copy link
Author

ValWood commented Jun 13, 2017

I told our user to follow this ticket so I can close in our help-desk.

I had a look at the first pass. That looks OK for cdc2 (direct only?)

Notebooks sound cool....
Happy to check any examples.

@kltm
Copy link
Member

kltm commented Aug 31, 2017

@cmungall @dougli1sqrd We should open a ticket for this item in the appropriate tracker and close this one out.

@kltm
Copy link
Member

kltm commented Nov 6, 2017

@cmungall @dougli1sqrd I'll close it out here, you can use issue mover to get it reopened in the right tracker.

@kltm kltm closed this as completed Nov 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants