https://bluejeans.com/426716450

Agenda

  • Review progress in sub-WGs.
    • Drill down. (Eric, Angelo, Tim)
    • Pipelines debugging. (Lauren, Simon, Trey)
    • Datasets & Testing. (Hsin-Fang, John)
  • Start building a list of components and the relationships between them.


Components

(Pre-meeting brainstorming by JDS)

Datasets & Testing

  • Assorted policy documents.
    • Code review.
    • Unit test guidelines.
    • Execution environment for CI and testing.
    • Etc.
  • System for writing testable documentation & examples.
  • Test coverage checked in CI, together with policy.
    • Note Tim just enabled test coverage in sconsUtils.
  • Defined test package that provides a quick check that nothing is wildly wrong prior to merging.
    • Assumption is that this is self contained — ie, it clones an LFS repository for all the data it needs.
    • Assume that these are run within Jenkins.
  • Nightly test packages.
    • Following a common format.
    • Upload results to SQuaSH or similar.
    • Covering multiple cameras.
    • Again, self contained.
    • Assume that these are run within Jenkins (is that a good assumption? Would nightly jobs on the VC be useful?)
  • Periodic test packages.
    • Assume (for now, at least) that these are fundamentally documentation and procedure; actually running the test involves manual intervention rather than automatic scheduling.
    • (Will that always be true? Do we need a system for having Jenkins execute VC jobs?)
    • Data is available on the GPFS filesystem, not from an LFS package.
  • CI System (Jenkins).
    • Broadly as it exists now, but with assorted suggestions for improvements to documentation and behaviour, to include improved notifications.
  • Dataset packages.
    • Common format definition.
    • Construction of one or more specific packages?
  • Periodic jobs to populate dataset packages with reprocessed data.
    • Are these the same as the nightly tests?
  • Storage of large datasets.
    • Refresh existing policy.
    • Ensure each dataset has an owner.
  • Metric tracking and notification.
    • Broadly as SQuaSH.
    • With aggressive notifications of regressions.
  • Performance tracking.
    • Combination of executing child-of-ci_hsc in Jenkins with upload to SQuaSH and those aggressive notifications.


Action for Next Week

  • John Swinbank will produce a document structure (in LaTeX) and list of components, expanding somewhat on the above.
  • Everybody will get some components in that document allocated to them, and should start filling in text.
  • Prior to the document being available, we can all already be thinking about text for the “obvious” components.
  • Action on Eric Bellm, Angelo Fausti and Unknown User (tmorton) to resolve any outstanding tensions in the drill down design, in particular to come up with a clear vision for “static plots” or the lack thereof.