1. General status updates/Schedule review
2. Timing distribution demonstration progress
3. online Trigger Processing (including through DTC) progress/plans
4. Status of tests with detector subsystems
5. Rack protection & slow controls progress/plans (dedicated DCS node at FCC)

Eric, working to resolve DCS, cut new version of artdaq core
Offline wants art v3, ok to be different until major change
artdaq could be ready in 6 months (March)
Greg, in discussions about event size, run control sw, crv, and roc-to-roc jitter
Pasha withdrawn 100ps jitter idea
Jose, looking at jitter measurements of 200MHz clock.. Seems to be a walking behavior contributed by the DTC
~560ps jitter peak-to-peak ROC-to-ROC
Rick, cassettes cause locking issue. Would like to not use breakout cassettes and retry tests.
Thinks DCS write/read firmware working, but software error occurs
Glenn, working Tuesday on DCS!
Wants to setup the dedicated DCS node in pilot system.
Wants to get back to Matthew Jones.
PPD started production of slow controls boxes
Bertrand, art always runs all triggers in trigger menu with no consideration for priority
Every trigger must check event window mode as first op

30 us vs 2 us event window discussion

Consideration for rollover counter
A. event tag 43b, event building on 48b
Downside is firmware changes
Upside, no online processing changes
B. use reserved 4b in Tracker packet (calo has multiple bytes free)
Upside, Minimal firmware changes, event tag is consistent everywhere
Downside is online algorithm TDC time-bits need to get high order rollover counter bits appended