1 Jun 2021 PAINT Conference Call: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
Line 16: Line 16:
** Example URL: http://data.pantherdb.org/ftp/downloads/paint/current/README (doesn't exist yet)
** Example URL: http://data.pantherdb.org/ftp/downloads/paint/current/README (doesn't exist yet)
** 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
*** 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===
===Taxon constraints in PAINT===

Revision as of 13:05, 1 June 2021

Present

Agenda

How will PAINT handle GP2term relations

NOT annotation issues

https://github.com/geneontology/go-annotation/issues/3701

IBA Release notes

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?
  • Taxon constraint violations in PAINT spreadsheet