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

Missing GO term #2852

Closed
ValWood opened this issue Aug 7, 2024 · 6 comments
Closed

Missing GO term #2852

ValWood opened this issue Aug 7, 2024 · 6 comments

Comments

@ValWood
Copy link
Member

ValWood commented Aug 7, 2024

logs have:
warning in a7c6118865e72409: can't find term with ID: GO:0160199
warning in a7c6118865e72409: can't find term with ID: GO:0160199

but I see it here:
https://www.ebi.ac.uk/QuickGO/term/GO:0160199

@kimrutherford kimrutherford self-assigned this Aug 7, 2024
@kimrutherford
Copy link
Member

It looks like a timing issue. It wasn't in last night's Chado but it's there tonight. So the message should be gone in the morning.

@kimrutherford
Copy link
Member

It looks like there was a delay between the snapshot running and the files appearing on the snapshot server?

We use this file for Chado:

http://snapshot.geneontology.org/ontology/go-basic.obo

The date in the file is:

data-version: releases/2024-08-04

Be the file timestamp implies that the file was copied to the snapshot web site three days later:

curl -s -I http://snapshot.geneontology.org/ontology/go-basic.obo | grep Last-Modified
Last-Modified: Wed, 07 Aug 2024 03:15:33 GMT

That doesn't explain why QuickGO is up to date though.

@ValWood
Copy link
Member Author

ValWood commented Aug 8, 2024

Hi @kltm do you know how QuickGo is ahead of the snapshot? are we using the correct file?

@kimrutherford kimrutherford removed their assignment Aug 8, 2024
@kltm
Copy link

kltm commented Aug 8, 2024

@ValWood There are a few factors here, but most of them boil down to a combination of 1) syncing lag and 2) we are in a transition in how we setup our pipelines.

Most importantly for this, maybe, is that the initial part of a snapshot release is a "freezing" of the data, which usually happens on Sunday. That is then manually checked and a secondary phase is run to produce associated product that we need; this used to be automated, and will be again soon. There can be a lag of a few days in there, but generally not more than that unless there is a problem.

The next bit is just informational, as we are changing this interaction and how our pipelines interact overall. QuickGO (currently) uses the QC version of the ontology, for some purposes, which is not synced with QC or annotation data. We will be switching to a faster and lighter pipeline which will better align all of these concerns soon (e.g. geneontology/pipeline#382).

@ValWood
Copy link
Member Author

ValWood commented Aug 8, 2024

Thanks for the info!
v

@kimrutherford
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants