-
Notifications
You must be signed in to change notification settings - Fork 496
Expand file tree
/
Copy pathstartComplexSetup2.sh
More file actions
executable file
·36 lines (26 loc) · 2.72 KB
/
startComplexSetup2.sh
File metadata and controls
executable file
·36 lines (26 loc) · 2.72 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
# simple start script to launch a more complex setup
# with 2 data publishers (inside subframebuilder) + 2 attached flpSenders + 4 EPNS
# Prerequisites:
# - expects the configuration file to be in the working directory
# - O2 bin and lib set n the shell environment
# it would be nice having a script that generates the configuration file for N FLP and M EPNS
# Start one HBSampler device
xterm -geometry 80x25+0+0 -hold -e o2-heartbeat-sampler --id heartbeatSampler --mq-config confComplexSetup2.json --out-chan-name output &
# Data publishers
xterm -geometry 80x25+500+0 -hold -e o2-datapublisher-device --id DataPublisherDeviceTPC --mq-config confComplexSetup2.json --in-chan-name input --out-chan-name output --data-description TPCCLUSTER &
xterm -geometry 80x25+500+400 -hold -e o2-datapublisher-device --id DataPublisherDeviceITS --mq-config confComplexSetup2.json --in-chan-name input --out-chan-name output --data-description ITSRAW &
# this is the subtimeframe publisher for TPC
xterm -geometry 80x25+1000+0 -hold -e o2-subframebuilder-device --id subframeBuilderTPC --mq-config confComplexSetup2.json --detector TPC &
# this is the subtimeframe publisher for ITS
xterm -geometry 80x25+1000+400 -hold -e o2-subframebuilder-device --id subframeBuilderITS --mq-config confComplexSetup2.json --detector ITS &
# this is the flp for TPC
xterm -geometry 80x25+1500+0 -hold -e o2-flp-sender-device --id flpSenderTPC --mq-config confComplexSetup2.json --in-chan-name input --out-chan-name output --num-epns 4 --flp-index 0 &
# this is the flp for ITS
xterm -geometry 80x25+1500+400 -hold -e o2-flp-sender-device --id flpSenderITS --mq-config confComplexSetup2.json --in-chan-name input --out-chan-name output --num-epns 4 --flp-index 1 &
# we have 4 epn and 2 flps
xterm -geometry 80x25+2000+0 -hold -e o2-epn-receiver-device --id epnReceiver1 --mq-config confComplexSetup2.json --buffer-timeout 10000 --in-chan-name input --out-chan-name output --num-flps 2 &
xterm -geometry 80x25+2000+400 -hold -e o2-epn-receiver-device --id epnReceiver2 --mq-config confComplexSetup2.json --buffer-timeout 10000 --in-chan-name input --out-chan-name output --num-flps 2 &
xterm -geometry 80x25+2000+800 -hold -e o2-epn-receiver-device --id epnReceiver3 --mq-config confComplexSetup2.json --buffer-timeout 10000 --in-chan-name input --out-chan-name output --num-flps 2 &
xterm -geometry 80x25+2000+1200 -hold -e o2-epn-receiver-device --id epnReceiver4 --mq-config confComplexSetup2.json --buffer-timeout 10000 --in-chan-name input --out-chan-name output --num-flps 2 &
# consumer and validator of the full EPN time frame
xterm -geometry 80x25+2000+500 -hold -e o2-timeframe-validator-device --id timeframeValidator --mq-config confComplexSetup2.json --input-channel-name input &