Projects stand up meeting 2021-02-24: Difference between revisions
Jump to navigation
Jump to search
Line 27: | Line 27: | ||
** Where else should we announce the file format change? Other forums? Send email again? | ** Where else should we announce the file format change? Other forums? Send email again? | ||
** Double-check what GAF file format each submitting group is actually submitting (roll this into broader outreach task). | ** Double-check what GAF file format each submitting group is actually submitting (roll this into broader outreach task). | ||
** For upgrading GAF2.1, what is happening with root node annotations? The [https://github.com/geneontology/go-site/commit/a904ff8ac15f884e433854a6e9536ff105c21167#diff-3c8e470e693dacedc146a614820b1e3ed0b1e6137800b8bb02b1d255e02e1c37 current upgrade] may not address this. | |||
==Pathways2GO manuscript== | ==Pathways2GO manuscript== |
Revision as of 11:21, 24 February 2021
Attendees
- Present:
- Regrets:
- Managers: David, Huaiyu, Kimberly, Pascale, Seth, Suzi, Judy, Paul, Chris
Projects presentation
Template:
- Next deliverables + expected date
- Progress
- Issues / blockers
GAF2.2 migration status
- Kimberly manually testing GAF2.2 input, output WB files as well as GPAD1.2 output WB files
- Still going to double-check Protein2GO output gpad files
- David manually testing files that MGI ingest from all resources (e.g. GOC, UniProt) and subsequent release of MGI GAF2.2 (and also GPAD/GPI2.0)
- Outstanding questions:
- How will GO handle different kinds of errors that may occur with gp2term relations in GAF2.2 files?
- Repair?
- For example, the gp2term relation for a root node annotation is not correct according to our GAF2.2 specifications.
- Remove?
- For example, the gp2term relation for non-protein-containing complex CC terms is 'part of'.
- Repair?
- For future file testing, what can be automated? Is it worth it?
- Testing these files raised some issues about how things actually happen wrt the pipeline, e.g. which PAINT files should be compared for input/output; we said we'd switch to GAF2.2 in March, what is happening with GPAD/GPI2.0 in March? If groups only produce a GPI2.0, will that break NEO production?
- Once the documentation is on the website, what should we do with the documentation page in github?
- Where else should we announce the file format change? Other forums? Send email again?
- Double-check what GAF file format each submitting group is actually submitting (roll this into broader outreach task).
- For upgrading GAF2.1, what is happening with root node annotations? The current upgrade may not address this.
- How will GO handle different kinds of errors that may occur with gp2term relations in GAF2.2 files?
Pathways2GO manuscript
ART1.0/Noctua3.0 plan
Items not discussed at last meeting
Imports
UniProt
- No plan yet
VEuPathDB
- Got in touch this week and would like to start using Noctua
Other resources (Yeast pathways)
History
GPAD export
=
Next sprint
https://docs.google.com/document/d/1AIuq8xxgV6bZZHFbXW-s3ln8PdUfZGNUuZcNFX1n7eQ/edit#