Annotation Conf. Call 2017-01-10

From GO Wiki
Revision as of 12:11, 10 January 2017 by Vanaukenk (talk | contribs) (→‎Minutes)
Jump to navigation Jump to search

Bluejeans

  • https://bluejeans.com/993661940
  • to join via phone: enter Meeting ID 993661940 after dialing in
    • from US: +1.408.740.7256 or +1.888.240.2560
    • from UK: +44.203.608.5256
    • from Switzerland: +41.81.588.0256

Agenda

Next Consortium Meeting

  • June 1-3, 2017
  • The regular meeting will be followed by two optional workshop days on LEGO and Reactome curation on June 4 and 5
  • Pankaj Jaiswal has graciously offered to host the meeting at Oregon State University in Corvallis, Oregon
  • He has set up a really nice meeting webpage at https://sites.google.com/view/goc2017
  • Please register!

Review of Jenkins Pipeline

View GAF builds in Jenkins

Working Groups

LEGO Modeling Discussions

  • We would like to reserve the second Tuesday annotation call of each month for discussion of LEGO modeling.
  • The proposal is to have two presenters each month for an ~30 minute discussion of their model.
  • The goal is to get more people comfortable with LEGO modeling and increase the number of processes represented by LEGO models in GO.
  • Please sign-up for a time slot here: LEGO Discussion Rota
  • We would like to do this on a volunteer basis, so please consider taking a turn.
  • We all benefit from discussing modeling issues from across a broad spectrum of organisms, and there is likely commonality amongst the pathways and processes that we are trying to represent.

Minutes

On call: Alice, Chris, David H., David OS, George, Giulia, Harold, Helen, Jim, Karen, Kimberly, Li, Melanie, Midori, Moni, Pasclae, Penelope, Petra, Rachael, Ruth, Sabrina, Stan, Terry, Val

Regrets: Paola

QC Pipeline

  • Two pipelines - Jenkins and Mike Cherry's checking scripts
  • Focus of this call - Jenkins pipeline
    • GAF checks have been failing - red balls
      • Due to an upstream failure in ontology build, was not being caught, but affected GAF check pipeline
      • This was an edge case, but has now been addressed such that the inconsistency check will happen upstream of the GAF check
  • Jenkins annotation inference pipelines