1 Jun 2021 PAINT Conference Call: Difference between revisions
Jump to navigation
Jump to search
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
==Present== | ==Present== | ||
Pascale, Marc, Paul, Anushya, Dustin, Huaiyu | |||
==Agenda== | ==Agenda== | ||
| Line 14: | Line 15: | ||
* Recording any drastic changes like increases or decreases | * Recording any drastic changes like increases or decreases | ||
* Where would the release notes be available? | * Where would the release notes be available? | ||
** Example URL: http://data.pantherdb.org/ftp/downloads/paint/current/README | ** Example URL: http://data.pantherdb.org/ftp/downloads/paint/current/README | ||
** Or just roll into GO release notes? Ex: https://github.com/geneontology/go-site/tree/master/releases/2021-05-01 | ** Or just roll into GO release notes? Ex: https://github.com/geneontology/go-site/tree/master/releases/2021-05-01 | ||
** <b>ACTION ITEM:</b> Go with the first solution - Add README to PAINT FTP folder | ** <b>ACTION ITEM (Dustin):</b> Go with the first solution - Add README to PAINT FTP folder | ||
*** This README file will be auto-generated with some info (e.g. date GO release GAFs downloaded) but may also need to be manually edited for certain situations (e.g. large IBA increase/decrease). | *** This README file will be auto-generated with some info (e.g. date GO release GAFs downloaded) but may also need to be manually edited for certain situations (e.g. large IBA increase/decrease). | ||
Latest revision as of 12:58, 22 June 2021
Present
Pascale, Marc, Paul, Anushya, Dustin, Huaiyu
Agenda
How will PAINT handle GP2term relations
- Need to define specs; proposal (Pascale) PAINT would load GP2term relations so PAINT curators would be able to select more precise annotations for propagation.
NOT annotation issues
https://github.com/geneontology/go-annotation/issues/3701
IBA Release notes
- Recording any drastic changes like increases or decreases
- Where would the release notes be available?
- Example URL: http://data.pantherdb.org/ftp/downloads/paint/current/README
- Or just roll into GO release notes? Ex: https://github.com/geneontology/go-site/tree/master/releases/2021-05-01
- ACTION ITEM (Dustin): Go with the first solution - Add README to PAINT FTP folder
- This README file will be auto-generated with some info (e.g. date GO release GAFs downloaded) but may also need to be manually edited for certain situations (e.g. large IBA increase/decrease).
Taxon constraints in PAINT
- How they currently affect PAINT objects
- Experimental annotations - considered valid to use for IBD evidence if no TC violation
- IBDs - will be obsoleted if IBD itself violates a TC or if it loses all experimental evidence due to TC checks in step #1
- TCVs - created in the family trees from the TCs and used to block propagation of IBAs
- Tool logic vs validator (batch process) logic?
- Should rules and effects be consistent between curator actions in the tool vs the monthly validator runs?
- Ex: Curator is allowed to create an IBD in violation (with a warning) but validator doesn't allow this and will obsolete later. Maybe this is a nonsensical example?
- Should rules and effects be consistent between curator actions in the tool vs the monthly validator runs?
- Taxon constraint violations in PAINT spreadsheet