SGD has incomplete GPI about neo HOT 11 CLOSED

@cmungall Should we derive here or work with SGD to provide a better source for us?

from neo.

I think right now we should remove the gpi entry from sgd.yaml. neo will fall back on the GAF. Which is good enough for a well-annotated genome for SGD.

After that we can try another solution. SGD provide a BGI for the Alliance, providing a GPI should not be hard and we can have some shared conversion code.

from neo.

Sounds like there's a plan? Let me know if there's something SGD specifically needs to do. Thanks

from neo.

@cmungall geneontology/go-site#953 correct?

from neo.

Merged and waiting for effect over the weekend.

from neo.

Update: No sgd Noctua gpad, but our existing annotations to Uniprot accessions are being rejected in the Form summary page (good I suppose) and SGD IDs are autofilling in. What steps do we need to take now to get a Noctua gpad?

from neo.

Well, if the IDs are SGD, the next time the models are reduced to GPADs in the pipeline they should come out naturally (assuming everything else is okay).
If I'm missing the answer you're wanting, feel free to tag me and we can get some of the others to take a look at it.

from neo.

next time the models are reduced to GPADs in the pipeline

This is a "daily/24h" occurrence or you mean the monthly release?

from neo.

This is a daily occurrence, which should be completed sometime in the evening, every day. The pickup location is the snapshot set of URLs, but progress can be seen here:
https://build.geneontology.org/job/geneontology/job/pipeline/job/snapshot/

from neo.

Thanks for the info, I'll bet we missed today's cutoff. We'll check it later. Thanks!

from neo.

ah well it looks like this is fine now

from neo.