Continue to investigate protoDUNE DAQ issues and validate artdaq changes at protoDUNE

[eflumerf]

This issue has been migrated from https://cdcvs.fnal.gov/redmine/issues/21814 (FNAL account required) Originally created by @bieryAtFnal on 2019-01-31 12:24:11

---

This issue is intended to be a place to capture information about our testing at protoDUNE.

For reference, here are some descriptions of work that has already happened:

• we've made progress in understanding a run stop/start issue that was much easier to reproduce at protoDUNE than test systems at Fermilab (Issue 21591)
• we've made progress in testing changes to help with the readout of many Trigger subsystem fragments per event, and identified changes that can provide further assistance in this area (e.g. Issue 21267)

The code changes for both of these, along with all of the changes that were merged into the develop branch in the artdaq and artdaq-core repositories have been merged into the for_dune-artdaq branches in those repos, and as of 31-Jan-2019, the current state of for_dune-artdaq branches are what is deployed in the dune-artdaq_artdaq_v3_03_01_plusOne software area at protoDUNE.

[eflumerf]

Comment by @eflumerf on 2019-07-16 16:01:19

---

These branches were merged into develop on 7/16/2019 in all repositories to pick up changes that were not yet in develop but had reached maturity through running at protoDUNE.