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

I couldn't get "regulates" ancestors terms #304

Open
10myl200 opened this issue Sep 16, 2024 · 7 comments
Open

I couldn't get "regulates" ancestors terms #304

10myl200 opened this issue Sep 16, 2024 · 7 comments
Assignees
Labels

Comments

@10myl200
Copy link

Hello, I tried to get all ancestors terms following the "parents_and_ancestors.ipynb" notebook, but what I could get was only "is_a" ancestors terms.

Here is the screenshot from my jupyter notebook.

image

And here is the ancestor chart.
image

Could you help me with this problem?

@tanghaibao
Copy link
Owner

@10myl200

Weird. I was able to get GO:008152.

image

@10myl200
Copy link
Author

Thank you for your quick reply! :)

  1. I reinstalled goatools using conda, but I still got the same problem.
    image
  2. So, I downloaded up-to-date go-basic.obo files from https://geneontology.org/docs/download-ontology/
    image
    It seems like there was a problem with the obo file, somehow.

@tanghaibao
Copy link
Owner

@10myl200

That's thorough investigation. Thanks.
If you still have the old obo, feel free to send it over and I'll inspect.
There could be a bug or a hidden filtering somewhere.

@10myl200
Copy link
Author

go-basic.obo.gz
That would be nice! Here is the old obo file.

@tanghaibao
Copy link
Owner

@10myl200

Thanks. When I repeat the code on the file you sent it seemed ok. I'm not sure how to reproduce the issue. Or perhaps it is flaky? I'm not sure.

Let me know again if you continue to have issues with regulates which means it's flaky and I shall dig again.

@10myl200
Copy link
Author

Thanks!
Unfortunately, the same error happened again, even with the new Obo file.

@tanghaibao
Copy link
Owner

ok. then we know it's flaky and certainly a bug.
I'll work on it soon. thanks

@tanghaibao tanghaibao self-assigned this Sep 23, 2024
@tanghaibao tanghaibao added the bug label Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants