Projects update meeting 2022-06-22: Difference between revisions
Jump to navigation
Jump to search
m (→Model copy) |
|||
Line 29: | Line 29: | ||
===Noctua tickets review=== | ===Noctua tickets review=== | ||
* David, Kimberly and Pascale reviewed all ticket in the [https://github.com/geneontology/noctua Noctua repo] | * David, Kimberly and Pascale reviewed all ticket in the [https://github.com/geneontology/noctua Noctua repo] | ||
* This generated a 'big ideas' document | * This generated a [https://docs.google.com/document/d/162H3_XYeLsFRqSpFNUliPgNPSHzVsAddaXv-WzoqTXo 'big ideas' document] | ||
* We need to decide whether some parts of this will become a project | * We need to decide whether some parts of this will become a project | ||
Revision as of 10:02, 22 June 2022
Attendees
- Members: David, Huaiyu, Kimberly, Pascale, Seth, Suzi, Paul, Chris, Cynthia
- Present:
Ongoing work updates
Release/snapshop update
New release started
SOP for project management
https://docs.google.com/document/d/1yWU8xy-lK34p6bSp2EDlTvonbbEr6mCzN2mdLhjNXv0/edit#
SynGO Updates
- Actions
- PO: Paul T
- TL: Dustin
- Ask Frank at SynGO to check
- Do we have some SOP? sanity checks?
- David to provide list of MGI checks
- Dustin will generate stats on the json to ttl conversion
- Ask Frank at SynGO to check models on dev, proposed date to get feedback by: June 23rd
- Make a syngo-specific pipeline to give them a report
- We will put the models on prod no matter what in 2 weeks (whether or not we are able to do this work)
- Produce a MOU (see below)
Model copy
Tasks required before moving to production
Noctua tickets review
- David, Kimberly and Pascale reviewed all ticket in the Noctua repo
- This generated a 'big ideas' document
- We need to decide whether some parts of this will become a project
Automated Minerva updates
https://github.com/orgs/geneontology/projects/87
- To do: review models that sometimes use regulates and other times directly regulates (23 models). Were curators trying to capture something specific that is now missing since we only use regulates?
- Note also that regulates does not have to be direct, according to the RO transitivity rules. We need to make sure this is clear and see how this impact annotation guidelines
- Should this be a new project ? what is the priority on this?
Review relation documentation
- We need a to generate a list of all relations currently used in Noctua and in P2GO
- We need to clearly list which relations are slated for obsoletion/not allowed for GO/GO-CAM curation
- We need to document usage for all valid relations (like we have started for has input, has output and occurs in)
MOU draft
- https://docs.google.com/document/d/1T1yW4dPaztjTJIkDPLBi3ob_-IGiqkP-kvGscprYijY/edit#
- update contributors list: http://geneontology.org/docs/go-consortium/
- unify with: http://geneontology.org/docs/annotation-contributors/
- http://geneontology.org/docs/collaborations/
Can this be automated from the yaml?
- CHRIS: YES!!!!
Machine learning methods for GO annotation prediction
- AI 2022-06-08 ARBA -> invite at a Annotation call for discussion
- Docs