Skip to content
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

Closed
hperrey opened this issue Feb 11, 2014 · 2 comments
Closed

Support for multiple DataCollectors #25

hperrey opened this issue Feb 11, 2014 · 2 comments

Comments

@hperrey
Copy link
Contributor

hperrey commented Feb 11, 2014

Add support for multiple DataCollector instances running e.g. on different machines:

  • reduces network traffic
  • reduces local disc I/O

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:

  • Event count verification for all producers
  • Online monitoring
  • Data file merging for conversion
hperrey added a commit to hperrey/eudaq that referenced this issue Feb 11, 2014
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
@hperrey
Copy link
Contributor Author

hperrey commented Feb 11, 2014

Current state of code in the multiple_datacollectors branch: works for command line executables. For example, by starting with

./TestRunControl.exe -l debug
./TestDataCollector.exe -a tcp://55001 -l debug -n testproducer
./TestDataCollector.exe -a tcp://55002 -l debug -n other
./TestProducer.exe -l debug -n testproducer

one can send data from the TestProducer to the DataCollector with the same name. However, in the config, one needs to specify for example

[DataCollector.testproducer]
FilePattern = "../data/run$6R_testproducer$X"

to avoid conflicts when opening the data files.

No tests or adjustments with the GUI have been performed yet.

@hperrey
Copy link
Contributor Author

hperrey commented May 6, 2014

The requested feature has been merged with #42; remaining issues with online verification and monitoring are covered by #58.
Will therefore close this issue now.

@hperrey hperrey closed this as completed May 6, 2014
jkvas pushed a commit to jkvas/eudaq that referenced this issue Jul 11, 2017
lhuth pushed a commit that referenced this issue Oct 12, 2020
airqui added a commit to SiWECAL-TestBeam/eudaq that referenced this issue Jun 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant