Skip to content
This repository has been archived by the owner on Mar 12, 2019. It is now read-only.

Avoid port conflict for localDAQ FM #349

Open
kakwok opened this issue Feb 7, 2018 · 0 comments
Open

Avoid port conflict for localDAQ FM #349

kakwok opened this issue Feb 7, 2018 · 0 comments

Comments

@kakwok
Copy link
Collaborator

kakwok commented Feb 7, 2018

If we manage to get local run event building xdaqs (TA, eventBuilder, FU) into one executive under a separate FM (localDAQ FM), we will need a mechanism in the FM code to edit the port to communicate with the localDAQ executives.
This is particular essential to support parallel running of two configurations, both taking runs at the same time. If localDAQ executives have a same, static port in both configurations, this will result in port conflicts.
FM should be able to assign a port to the localDAQ executives(and those they talk to) on-the-fly before initializing the executives.

@kakwok kakwok added this to the localDAQFM milestone Feb 7, 2018
@kakwok kakwok added the localDAQ label Mar 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants