Moved MQ devices to reco/mq folder. New MQ device for trigger algorithm.

Moved Fair MQ devices related to classes in the "algo" namespace to new folder reco/mq. Renamed the classes in accordance with discussions.

The new CMakeLists.txt is based on MQ/mcbm/CMakeLists.txt. Many unneeded lines were removed, but some might remain. Independent verification is appreciated.

Also: Implemented a separate MQ device for algo::TimeClusterTrigger.

Includes commits from !775 (closed).

changed the description

added 8 commits

• 32370bad...8fcb9dfc - 2 commits from branch computing:master
• ec592a85 - Implemented MQ device for algo::UnpackSts.
• 5af4b5fa - Added the possibility to process CbmDigiTimeSlice objects as input to...
• b1853e0a - Moved devices related to algo namespace, and corresponding launch script, to...
• a6f28bc1 - Renamed classes in reco/mq folder.
• 88773f4a - Created MQ device for trigger algorithm of algo namespace.
• 4bf6787e - Changed CbmDevBuildEvents to receive triggers from MQ channel.

Compare with previous version

added 1 commit

• 50af9bde - Changed CbmDevBuildEvents to receive triggers from MQ channel.

Compare with previous version

@p.-a.loizeau I have a problem here, that you might know how to solve. In this MR there is a MQ device "CbmDeviceTrigger" which runs the trigger algorithm and produces a std::vector with trigger times. It then sends these over the MQ channel "trigger" to the class "CbmDevBuildEvents", which does the event building.

I stringed them together in "startBuildEvents.sh.in". The trigger algorithm seems to receive the unpacked data just fine, and also seems to do the trigger finding. The output data then gets reported as having been sent to the "trigger" channel. Only the event builder then never receives anything on that channel.

Probably I messed something up with the naming of the channels. I will check again tomorrow. But there might be some deeper reason, such that I am using the channels improperly.

By the way, I wasn't sure whether there are certain addresses/ports that are reserved for MQ messages. In the previous version, events were sent via tcp://127.0.0.1:11556. I now use this for triggers, and send events over tcp://127.0.0.1:11557. Not sure whether that makes any sense.

added 1 commit

• 897dbe05 - Changed CbmDevBuildEvents to receive triggers from MQ channel.

Compare with previous version

mentioned in merge request !775 (closed)

@p.-a.loizeau Changing one of the "methods" from "connect" to "bind" seems to work.

added 7 commits

• d94b4dec - 1 commit from branch computing:master
• 83bbbe86 - Implemented MQ device for algo::UnpackSts.
• bbd5d0eb - Added the possibility to process CbmDigiTimeSlice objects as input to...
• feea9b5f - Moved devices related to algo namespace, and corresponding launch script, to...
• f01cd6ea - Renamed classes in reco/mq folder.
• 8971d9d9 - Created MQ device for trigger algorithm of algo namespace.
• 5ba0a222 - Changed CbmDevBuildEvents to receive triggers from MQ channel.

Compare with previous version

marked this merge request as ready

changed title from WIP: Added the possibility to process CbmDigiTimeSlice objects as input to... to MQ devices in reco/mq folder

mentioned in merge request !778 (closed)

@v.friese @p.-a.loizeau @f.uhlig

I closed !778 (closed), since this now represents an intermediate step. I included the text from the description here.

Removed WIP flag. Ready for merge in my opinion.

changed title from MQ devices in reco/mq folder to Moved MQ devices to reco/mq folder. New MQ device for trigger algorithm.

changed the description

resolved all threads

Dear @f.uhlig, @p.-a.loizeau, @v.friese,

you have been identified as code owner of at least one file which was changed with this merge request.

Please check the changes and approve them or request changes.

added CodeOwners label

Closing after discussion.

closed