2018 02 13

• Agenda

  • status updates, time lines -> calendar
    • how did you self-organize last week?
      • where are the traces?
      • example: radical-collaboration/workflow

• Teams

  • team 1 (Manuel, Franklin, Will)
    • deadline for IS: 1 week, OS: no deadline yet, same effort as IS
    • all 36 IS test cases implemented
    • OS tbd, dealine Feb. 20
  • team 2 (Iannis, Srinivas)
    • measurements
    • last meet on Friday, client side impl. has been changed
    • tight timelines...
  • team 3 (Jumana, Vivek, George)
    • focus on testing
      • George: SAGA integration, Jumana: RP integration (WIP), VB: component level test
      • UMIS test done, output staging test upcoming
      • using pytest, same mocking module as team 1
      • env expansion for test config file?

• Homework:

  • what is a good ticket / bad ticket?
  • good
    • code snippets / short script to reproduce
    • problem context, logs,
    • what is the problem (vs. expectation)
    • what changes / tests have been done
    • every ticket is a good ticket!
  • bad
    • • not assigned, not triaged
    • • missing information
    • • wrong information
    • one-liners
    • its not a chat - iteration is slow
  • define a format?
    • client logs, agent logs, stack
    • small tool for ticket input?
    • templates are useful?
    • size limits?
    • temp storage for attached data?
    • TODO AM: github marketplace
    • TODO AM: temporal assessment

• backburner:

  • ZMQ
  • what are the drawbacks of python / advantages?

• Link Collection

  • RP Architecture
    • Animation
    • Overview
  • RCT Code Walkthroughs:
    • Agent Staging Input Component
    • Component mechanics
      • rpu.Component
      • rpu.Component.register_input()
      • rpu.Component.register_output()
      • rpu.Component.work_cb()