Planned dates (nothing new here, but Please Note that 26-March is less than a week away; see attached calendar for some additional details):
- 26-March for fddaq-v4.4.0 release candidate 1
- 17-April for the final fddaq-v4.4.0 release build
- some number of release candidates in between, each with a decreasing number of changes
Known goals for 26-March:
- CRT software changes: this would include what already exists in PRs plus the changes to communicate with the CRT subsystem (e.g.
startapp and stopapp), including whatever movement of code between repos will be done for fddaq-v4.4.0
- on Wednesday, Wes mentioned that Matt Murphy is working on changes, and he (Wes) has a sample implementation of adding the CRT to a detector readout map
- additional updates? ETA?
- DAPHNE controller
- on Wednesday, Marco mentioned that he has code changes that send a complete and working configuration for the DAPHNE. An update to the firmware to work with the new software is expected in a week's time. An application to generate a configuration for a run will likely take a couple of weeks. And, the addition of a custom command to dump the contents of the SPY buffer may be possible to get done this week.
trigger and triggeralgs logging rework (trigger PR 285 and triggeralgs PR 59)
- questions about the scope of these changes and their appropriateness for the v4 line
- what is intended with TLOG(<number>), e.g. TLOG(0)?
- why is a short tag string needed to identify the DAQModule that is the source of a message, is that a Grafana thing?
- additional configurability for TPG
- PRs have been tested, review is in progress, one small snafu found (hopefully resolved soon)
- updates to the messages that
nanorc sends to the elog, listed here
- 'trigger bit' changes (actually TriggerRecordHeader::trigger_type size changes, plus changes to enum(s) that indicate what the various bits in that word mean)
- last time, there was talk of using the FakeHSI for testing. Is that working out OK?
- DQM deliverables
- which recent, current, and possibly future PRs are targeted to
fddaq-v4.4.0? link to justintime repo PRs (possibly useful for discussion)
- changes for the "Object already exists" messages from TPWriter when the TP rate is low.
- add config param to allow longer wait time in the TPStreamWriter; downgrade the message from error to warning
- I've worked on this, but haven't been able to come up with an emulated-data situation that demonstrates the problem. Will continue...
Draft list of changes that we want to tell our Offline colleagues about:
- TC version change, 1 -> 2
- new size and contents of TRH::trigger_type field
- filelayout_version changes, 4 -> 5; new HDF5 file-level Attributes
- changes to configuration (OKS) sometime in the future
- what else?
Let's review PRs that we haven't talked about already: