[Feature]: Add a configuration to test the DAPHNE Ethernet data type to the readout_type_scan regression test

[bieryAtFnal]

Description

Now that we have code for the DAPHNE Ethernet data type, it would be good to add it to the readout_type_scan_test. I expect that this will include the addition of a binary file with sample DAPHNE Ethernet data to the "assets" system.

Potential impact radius

Small/Isolated

Reason for change

It will be great to verify that the emulation of DAPHNE Ethernet data and the basic handling of it in the system works smoothly, both now and in the future, and the addition of this data type to the readout_type_scan regression test will help to do that.

Suggested implementations

No response

Testing suggestions

Once this data type is added to the regression test, we should (obviously) confirm that the test continues to run successfully.

Anything else?

No response

[wesketchum]

Thanks for filing the issue @bieryAtFnal . I'll note that we should also include a test for the streaming format (DAPHNEEthStreamFrame) alongside the self-triggered one (DAPHNEEth)

[denizergonul]

There seems to be some confusion about whether this task has already been completed. I couldn't find any related development work, perhaps it's being confused with non-Ethernet DAPHNE. Also, when I checked the assets directory, I didn't see any binary labeled DAPHNEEth.

[wesketchum]

See: DUNE-DAQ/daq-assettools#21

a mode with fake data generated from scratch has been included in fddaq-v5.6.0, but we still would like to add and then use an asset file for this, which I've slated for the future release. Can leave this issue open to mark that we will also need to update the test to use that file when it is available.