-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for multiple DataCollectors #25
Labels
Comments
hperrey
added a commit
to hperrey/eudaq
that referenced
this issue
Feb 11, 2014
work toward eudaq#25
hperrey
added a commit
to hperrey/eudaq
that referenced
this issue
Feb 11, 2014
- first DC connection is treated as default - replaced if unnamed DC connects - otherwise, named DCs are only assigned to producers named accordingly - runnumber is verified between all DCs work toward eudaq#25
Current state of code in the
one can send data from the TestProducer to the DataCollector with the same name. However, in the config, one needs to specify for example
to avoid conflicts when opening the data files. No tests or adjustments with the GUI have been performed yet. |
airqui
added a commit
to SiWECAL-TestBeam/eudaq
that referenced
this issue
Jun 8, 2022
Analysis tb2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add support for multiple DataCollector instances running e.g. on different machines:
Removal of these bottlenecks is important for running at very high track- and data-rates, e.g. the one-trigger-per-particle operation of the AIDA telescope.
(Potential) issues and ToDo:s:
The text was updated successfully, but these errors were encountered: