CRT topology change

[denizergonul]

• CRT frame builders:
  • Communicate with SocketWriter via IOM.
  • Have a dedicated D2D connection (with 1 of the DataSenders).
  • Spawn producer threads for each DetectorStream.
  • Have 1 MPMC (practically, MPSC) IOM sender.

---

CRT(Bern/Grenoble)ReaderModule currently generates fake packets (to be replaced by real CRT hardware in the future).

1. Map source IDs to stream IDs (m_fake_stream_ids).
   e.g.
   1007->0
   1008->1
2. Start a producer thread that, for each stream:

• Generates a fake packet with proper stream ID.
• Sends packet via the queue.
  e.g.
  packet.stream_id=0 uses IOM1
  packet.stream_id=1 uses IOM1

---

appmodel PR dte/crt_topology_change
daqsystemtest PR dte/crt_topology_change
crtmodules PR dte/crt_topology_change
asiolibs PR dte/crt_topology_change
daqconf PR dte/crt_cb_update
datahandlinglibs PR dte/cb_acquire
fdreadoutmodules PR dte/crt_rates

CRT readers communicate with socket writers via IOM.
Socket readers communicate with DHLs via callbacks.

To try out:
pytest -s integtest/crt_frame_buider_test.py

---

Type of change

• New feature or enhancement (non-breaking change which adds functionality)

Testing checklist

• Python tests pass if applicable (e.g. python -m pytest)

Further checks

• Code is commented where needed, particularly in hard-to-understand areas
• Code style is correct (dbt-build --lint, and/or see https://dune-daq-sw.readthedocs.io/en/latest/packages/styleguide/)

[alessandrothea]

LGTM

[bieryAtFnal]

Closing this PR since the branch has been merged to the prep-release/fddaq-v5.6.0 branch in a different PR.