Difference: GeneralDaqOperation (1 vs. 15)

Revision 15
10 Aug 2011 - Main.RafalLalik
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Line: 69 to 69
 

Added:
>
>
  • ButWereAfraidToAsk)?topicparent=DaqSlowControl.GeneralDaqOperation" rel="nofollow" title="Create this topic">Everything You Always Wanted to Know About QA Check List (But Were Afraid to Ask)
 

FOR EXPERTS

  • Include/exclude subsystems: lxhadesdaq:/home/hadaq/apr07/oper/subsystems_for_daq
Revision 14
01 Jan 2010 - Main.JanMichel
Line: 1 to 1
Added:
>
>
META TOPICPARENT name="HadesDaqDocumentation"
 

General DAQ

Revision 13
08 Oct 2008 - Main.SergeyYurevich
Line: 1 to 1
 

General DAQ

Line: 12 to 12
 

Start data taking

Changed:
<
<
Button "Blue_Arrow_Down"->"Event Builder Start (lxhadesdaq)"
>
>
Button "Blue_Arrow_Down"->"EvtBuild Start (Lustre ON)"
 

Start Event Builder without data taking

Changed:
<
<
Button "Pingu_with_injection"->"Event Builder Start to /DEV/NULL (lxhadesdaq)"
>
>
Button "Pingu_with_injection"->"EvtBuild Start to /DEV/NULL"
 

Stop acquisition

Line: 44 to 44
 
  • Button "Blue_Arrow_Down"->"Change Event Builder Prefix".
  • Close Event Builder windows
  • Button "Blue_Arrow_Down"->"Fast DAQ start". (Wait until DAQ is restarted)
Changed:
<
<
  • Button "Blue_Arrow_Down"->"Event Builder Start (lxhadesdaq)"
>
>
  • Button "Blue_Arrow_Down"->"EvtBuild Start (Lustre ON)"
 

Where do we write the data?

Revision 12
25 Sep 2008 - Main.SergeyYurevich
Line: 1 to 1
Added:
>
>
 

General DAQ

Changed:
<
<

Starting acquisition

>
>
All what is written below should be done on hadesdaq computer.

Start acquisition

 
Changed:
<
<
On the hadesdaq computer, use the button "Blue_Arrow_Down"->"Fast DAQ start". After a successfull ctu start, the sound "alle parameter..." should be played.
>
>
Button "Blue_Arrow_Down"->"Fast DAQ start". After a successfull ctu start, the sound "alle parameter..." should be played (if sound server is enabled).
 

Start data taking

Changed:
<
<
"Blue_Arrow_Down"->"EB start"
>
>
Button "Blue_Arrow_Down"->"Event Builder Start (lxhadesdaq)"

Start Event Builder without data taking

Button "Pingu_with_injection"->"Event Builder Start to /DEV/NULL (lxhadesdaq)"
 

Stop acquisition

Changed:
<
<
Normally not needed, just reatart DAQ. Only for threshold setting: "Pingu_with_injection"->"Stop HADES daq"
>
>
Button "Pingu_with_injection"->"Stop Hades DAQ". Normally it is not needed, just use "Fast DAQ start". Only for threshold setting.
 

Monitor the DAQ

Changed:
<
<
Blue_Arrow_Down->DAQ monitor. NB: To log on the trigconc crate is out-of-date!!! Use only one DAQ monitor, there is no need to stop the daq monitor, it it restarted after a daq start.
>
>
Button "Blue_Arrow_Down"->"DAQ monitor". Use only one DAQ monitor! There is no need to stop the daq monitor, it it restarted after a daq start. If you want to copy some info from monitor to logbook, you should use button "Blue_Arrow_Down"->"DAQ monitor short for the logbook"
 

Sound monitor

Changed:
<
<
Disable the alarms with: "Blue_Arrow_Down"->"Clear running sound until next ctustart" - in case that the sound are annying. NEVER disable the sound speaker, the sound is important. Meaning of the sounds:
>
>
Disable the sound alarms with: "Blue_Arrow_Down"->"Clear running sound until next ctustart". NEVER switch off the sound speaker, the sound is important!
 
Added:
>
>
Meaning of the sounds:
 
  • "Alle Parameter...": DAQ is started and should run
  • "Schutzschirme brechen zusammen": Permanent busy, have a look to the DAQ monitor, restart the DAQ
  • "Automatik unterbrochen": Eventbuilder is running, but no data is written (e.g. spill break?)
Changed:
<
<

Event Building

Use "EB start button"

Changing system

"Pingu_with_injection"->"EB windows": edit the file "subsystems_for_daq"

Changing file prefix

"Blue_Arrow_Down"->"Change Prefix". Start a new file with "EB start button"
>
>

Changing file prefix

 
Changed:
<
<

ONLY FOR EXPERTS

>
>
  • Button "Blue_Arrow_Down"->"Change Event Builder Prefix".
  • Close Event Builder windows
  • Button "Blue_Arrow_Down"->"Fast DAQ start". (Wait until DAQ is restarted)
  • Button "Blue_Arrow_Down"->"Event Builder Start (lxhadesdaq)"
 
Changed:
<
<
  • Starting event builder
>
>

Where do we write the data?

 
Changed:
<
<
daq_evtbuild -q 33554432 -m 7
>
>
  • Local hard disk: lxhadesdaq:/data/lxhadesdaq/sep08/
  • Lustre: /lustre_alpha/hades/beam/sep08/
  • Tape archive: hadessep08raw, directory: hld
 
Changed:
<
<
Starting event builder with writing data to a file:
>
>

Links for DAQ/QA operator

 
Changed:
<
<
daq_evtbuild -q 33554432 -m 7 -d file -o /d/hadeb03/may04 -x be
( daq_evtbuild -q queuesize -m number_of_subsystems -d file -o output_path -x file_prefix )
>
>
 
Changed:
<
<
Check for disk space on the available disks /d/hadeb03, /d/disk1, /d/disk2, /d/disk3
>
>
 
Changed:
<
<
Directory structure should be beamtime/hld/day, e.g. nov02/hld/342
>
>
 
Changed:
<
<
  • Starting daq_netmem
>
>
 
Changed:
<
<
On the event builder machines hadeb02 / hadeb03 you use
>
>
 
Added:
>
>

FOR EXPERTS

 
Changed:
<
<
daq_netmem -q 33554432 -m7 -i UDP:127.0.0.1:2222 -i UDP:127.0.0.1:2223 -i UDP:127.0.0.1:2224 -i UDP:127.0.0.1:2225 -i UDP:127.0.0.1:2226 -i UDP:127.0.0.1:2227 -i UDP:127.0.0.1:2228
>
>
  • Include/exclude subsystems: lxhadesdaq:/home/hadaq/apr07/oper/subsystems_for_daq
  • Change water marks: lxhadesdaq:/home/hadaq/apr07/oper/eb_netmem.conf
  • Writing to disk/lustre/tape: lxhadesdaq:/home/hadaq/apr07/oper/eb_netmem.conf
 
Added:
>
>

daq_evtbuild, daq_netmem

 

Added:
>
>
You can always find the used arguments in lxhadesdaq:/home/hadaq/apr07/oper/start_eb.sh
 

Changed:
<
<
-- MichaelTraxler - 27 Jan 2005
>
>
-- SergeyYurevich - 25 Sep 2008
 
Revision 11
04 Apr 2007 - Main.HadesDaq
Line: 1 to 1
 

General DAQ

Starting acquisition

Changed:
<
<
On the hadesdaq computer, use the button "Apple"->"Fast DAQ start".
>
>
On the hadesdaq computer, use the button "Blue_Arrow_Down"->"Fast DAQ start".
  After a successfull ctu start, the sound "alle parameter..." should be played.

Start data taking

Changed:
<
<
"Apple"->"EB start"
>
>
"Blue_Arrow_Down"->"EB start"
 

Stop acquisition

Changed:
<
<
Normally not needed, just reatart DAQ. Only for threshold setting: "Hangup-K"->"Stop HADES daq"
>
>
Normally not needed, just reatart DAQ. Only for threshold setting: "Pingu_with_injection"->"Stop HADES daq"
 

Monitor the DAQ

Changed:
<
<
Apple->DAQ monitor. NB: To log on the trigconc crate is out-of-date!!!
>
>
Blue_Arrow_Down->DAQ monitor. NB: To log on the trigconc crate is out-of-date!!!
  Use only one DAQ monitor, there is no need to stop the daq monitor, it it restarted after a daq start.

Sound monitor

Changed:
<
<
Disable the alarms with: "Apple"->"Clear running sound until next ctustart" - in case that the sound are annying. NEVER
>
>
Disable the alarms with: "Blue_Arrow_Down"->"Clear running sound until next ctustart" - in case that the sound are annying. NEVER
  disable the sound speaker, the sound is important. Meaning of the sounds:

  • "Alle Parameter...": DAQ is started and should run
Line: 34 to 34
 

Changing system

Changed:
<
<
"Hangup-K"->"EB windows": edit the file "subsystems_for_daq"
>
>
"Pingu_with_injection"->"EB windows": edit the file "subsystems_for_daq"
 

Changing file prefix

Changed:
<
<
"Apple"->"Change Prefix". Start a new file with "EB start button"
>
>
"Blue_Arrow_Down"->"Change Prefix". Start a new file with "EB start button"
 

ONLY FOR EXPERTS

Revision 10
04 May 2006 - Main.MartinJurkovic
Line: 1 to 1
 

General DAQ

Starting acquisition

Line: 12 to 12
 

Stop acquisition

Changed:
<
<
Noemally not needed, just reatart DAQ. Only for threshold setting: "Hangup-K"->"Stop HADES daq"
>
>
Normally not needed, just reatart DAQ. Only for threshold setting: "Hangup-K"->"Stop HADES daq"
 

Monitor the DAQ

Revision 9
03 May 2006 - Main.MartinJurkovic
Line: 1 to 1
 

General DAQ

Starting acquisition

Line: 38 to 38
 

Changing file prefix

Changed:
<
<
"Hangup-K"->"EB windows": edit the file "start_daq". Edit this line: my $eb_file_type = "te";
>
>
"Apple"->"Change Prefix". Start a new file with "EB start button"
 

ONLY FOR EXPERTS

Revision 8
02 May 2006 - Main.ChristianSturm
Line: 1 to 1
Deleted:
<
<
Table of contents


 

General DAQ

Starting acquisition

Line: 36 to 30
 

Event Building

Changed:
<
<
ONLY FOR EXPERTS->Use "EB start button"
>
>
Use "EB start button"

Changing system

"Hangup-K"->"EB windows": edit the file "subsystems_for_daq"

Changing file prefix

"Hangup-K"->"EB windows": edit the file "start_daq". Edit this line: my $eb_file_type = "te";

ONLY FOR EXPERTS

 

  • Starting event builder
Revision 7
02 May 2006 - Main.IngoFroehlich
Line: 1 to 1
  Table of contents
Line: 7 to 7
 

General DAQ

Changed:
<
<
  • Starting acquisition
>
>

Starting acquisition

 
Changed:
<
<
On the hadesdaq computer, use the button Apple->Start HADES DAQ mini runcontrol. Press Options->Start aquisition
>
>
On the hadesdaq computer, use the button "Apple"->"Fast DAQ start".
  After a successfull ctu start, the sound "alle parameter..." should be played.
Changed:
<
<
  • Stop acquisition
>
>

Start data taking

 
Changed:
<
<
Close the daq_xmanage by pressing the X-Button on the window frame. At the same time, annoying sound should disapprear
>
>
"Apple"->"EB start"
 
Changed:
<
<
  • Monitor the DAQ
>
>

Stop acquisition

 
Changed:
<
<
Apple->DAQ monitor. NB: To log on the trigconc crate is out-of-date
>
>
Noemally not needed, just reatart DAQ. Only for threshold setting: "Hangup-K"->"Stop HADES daq"
 
Added:
>
>

Monitor the DAQ

 
Added:
>
>
Apple->DAQ monitor. NB: To log on the trigconc crate is out-of-date!!! Use only one DAQ monitor, there is no need to stop the daq monitor, it it restarted after a daq start.

Sound monitor

Disable the alarms with: "Apple"->"Clear running sound until next ctustart" - in case that the sound are annying. NEVER disable the sound speaker, the sound is important. Meaning of the sounds:

  • "Alle Parameter...": DAQ is started and should run
  • "Schutzschirme brechen zusammen": Permanent busy, have a look to the DAQ monitor, restart the DAQ
  • "Automatik unterbrochen": Eventbuilder is running, but no data is written (e.g. spill break?)
 

Event Building

Added:
>
>
ONLY FOR EXPERTS->Use "EB start button"
 
  • Starting event builder

daq_evtbuild -q 33554432 -m 7
Revision 6
28 Apr 2006 - Main.ChristianSturm
Line: 1 to 1
  Table of contents
Line: 7 to 7
 

General DAQ

Deleted:
<
<
Attention: Most likely this page on Data acquisition is heavily outdated!

  • Configuring the system

Change the first line in "hades.tcl" according to the subsystems you want to include in the acquisition:

set subsystems { trig shw rich0 rich1 rich2 tof1 tof2 tof3 mdc0 mdc1 }

Attention: You have to change the file "trigconc.tcl" on the LynxOS system in a consistent way!!
 
  • Starting acquisition
Changed:
<
<
log in to lxhadesdaq > ssh lxhadesdaq
> hadaq

In the GUI you do:

"Options -> Start acquisition"

* Known problems

# During the "Start Acquisition", check the "error_watch". In case of a "SamX: Bus Error", interrupt the start procedure and try another "start acquisition".

# If the acquisition hangs with a busy on RICH, just try to restart it. In case this happens frequently, contact the responsible RICH person. Lowering the beam intensity might help.

# If the acquistion shows an error like "error opening shared memory subeventqueue", restart the agents (tclsh ..., see above) and the acquisition.

RICH

Readout Host Script Cards VME Crate

  • RICH Busy

In case of busy, check the Rb busy of each rich:

dtuctrl status richXdtu

(where X corresponds to the rich READOUT number: 0, 1 or 2)

Usually the "Busy" comes from an "Error" in one RICH readout controller, you will find

RCs : not busy, error FEs : no busy IPUs:(not) busy, no error

Just restart the data acquisition.

In case you want to investigate the problem more deeply, do

racectrl status raceX (X = 0,1,10,11 (rich2); 2,3,4,5 (rich1); 6,7,8,9 (rich0))

If there are some '0' in the last column, this readout controller is the bad guy.

/RC busy : 1 1 /Trigger busy : 1 1 /Error : 1 0

  • CPU Memory

The memory situation of the RICH CPUs should frequently be checked

ps ax

If the memory value shown in the last line is close to 1000K, reboot this CPU

1240K/0K free physical/virtual, 7540K used

--> user_reboot

If this does not work, a power cycle might be necessary, afterwards a "richX init".

For the power cycle mind: Switching Off/On the power of frontend modules (FE) and VME Crate (VME) should be done in the following order : FE off -> VME off -> VME on -> FE on See the table above for the correlation Vme-Crate <--> FE module

  • Known problems

# After "user_reboot" or "power cycle" in rich0: First do "racectrl status race9". In case of a bus error redo the power cycle, otherwise proceed to the "init". # During "rich1 init": The init of prc2 will fail in most cases. Redo it by hand:

prcctrl init prc2

Readout Host Script Cards
rich0 r2f-24 rich0 init  
rich1 r2f-27 rich1 init  
rich2 r2f-28 rich2 init  

Shower

Readout Host Script Cards
shw r2f-14 shw init IPC 0,..,11

TOF

Readout Host Script Cards
tof1 e7_25 tof1 init tof1tip (Sectors )
tof2 e7_21 tof2 init tof2tip (Sectors )
tof3 e7_41 tof3 init tof3tip (Sectors )
conc r2f-35 trigconc init conc (Readout for all sectors)

MU

Readout Host Script Cards
conc r2f-35 trigconc init mu

Status Info

Triggers rate:
>viewrate_DAQ

$ viewrate_DAQ
1: LVL1   2: p.LVL2 3: rings  4: lept.  5: acc.ri 6: acc.lep
1: 96     2: 96     3: 65     4: 0      5: 115    6: 0      

  • RICH-Hit Rate: Rate of events with at least the required number of hits found by RICH-IPU (usually at least one hit at the moment)

  • Lepton Rate: Rate of events with at least the required number of leptons found by Matching Unit (usually at least one hit at the moment)

  • RICH-Hit Mult: Accumulated number of RICH IPU hits ( RICH-Hit Mult / RICH-Hit Rate ==> mean ring multiplicity in all ring events)

The difference between the lepton rate (which usually is the trigger algo rate) and the LVL2 rate comes from the downscaled events!
>
>
On the hadesdaq computer, use the button Apple->Start HADES DAQ mini runcontrol. Press Options->Start aquisition After a successfull ctu start, the sound "alle parameter..." should be played.
 
Changed:
<
<
Busy monitor:
>
>
  • Stop acquisition
 
Changed:
<
<
>busy_monitor
>
>
Close the daq_xmanage by pressing the X-Button on the window frame. At the same time, annoying sound should disapprear
 
Changed:
<
<
LVL1: ---11-   LVL2: ------
LVL1: 634*8-   LVL2: 21265--
LVL1: 41362--  LVL2: ---21-
>
>
  • Monitor the DAQ
 
Changed:
<
<
The numbers show how many times the subsystem was busy out of 10 ( - = 0; * = 10)
>
>
Apple->DAQ monitor. NB: To log on the trigconc crate is out-of-date
 
Deleted:
<
<
order of readouts in the line: rich shw tof mdc0 mdc1 unused MDC Readout Host Script Cards mdc0 r2-8 mdc0 init sam0- (MDC ) mdc1 r2-32 mdc1 init sam8- (MDC )
 

Event Building

Revision 5
12 Sep 2005 - Main.MichaelTraxler
Line: 1 to 1
  Table of contents
Line: 124 to 124
  Status Info

Triggers rate:
Changed:
<
<
>viewrate d00e800c d00e8014 d00e808c d00e8098 d00e80e8
>
>
>viewrate_DAQ
 
Changed:
<
<
LVL1 Rate LVL2 Rate RICH-Hit Rate Lepton Rate RICH-Hit-Mult. 1: 5796 2: 970 3: 767 4: 426 5: 1481 1: 6047 2: 969 3: 758 4: 399 5: 1385 1: 5933 2: 930 3: 699 4: 371 5: 1331
>
>
$ viewrate_DAQ 1: LVL1 2: p.LVL2 3: rings 4: lept. 5: acc.ri 6: acc.lep 1: 96 2: 96 3: 65 4: 0 5: 115 6: 0
 

  • RICH-Hit Rate: Rate of events with at least the required number of hits found by RICH-IPU
Revision 4
09 Feb 2005 - Main.MartinJurkovic
Line: 1 to 1
  Table of contents
Line: 96 to 96
 

prcctrl init prc2
Added:
>
>

Readout Host Script Cards
rich0 r2f-24 rich0 init  
rich1 r2f-27 rich1 init  
rich2 r2f-28 rich2 init  
 

Shower

Readout Host Script Cards
Changed:
<
<
shw r2-14 shw init IPC 0,..,11
>
>
shw r2f-14 shw init IPC 0,..,11
 

TOF

Line: 108 to 114
 
tof1 e7_25 tof1 init tof1tip (Sectors )
tof2 e7_21 tof2 init tof2tip (Sectors )
tof3 e7_41 tof3 init tof3tip (Sectors )
Changed:
<
<
conc r2-35 trigconc init conc (Readout for all sectors)
>
>
conc r2f-35 trigconc init conc (Readout for all sectors)
 

MU

Readout Host Script Cards
Changed:
<
<
conc r2-35 trigconc init mu
>
>
conc r2f-35 trigconc init mu
 

Status Info
Revision 3
01 Feb 2005 - Main.MichaelTraxler
Line: 1 to 1
Changed:
<
<
>
>
Table of contents
 
Changed:
<
<
# General DAQ # RICH # Shower # TOF # MU # MDC # Event Building
>
>
 
Added:
>
>

 

General DAQ

Line: 26 to 20
 

  • Starting acquisition
Changed:
<
<
>cd /home/hadaq/nov01/eb/hadaq_tcl
>./start_agents_parallel-sep03
>./daq_xmanage hadaq.tcl hades.tcl
>
>
log in to lxhadesdaq > ssh lxhadesdaq
> hadaq
 

In the GUI you do:
Line: 172 to 166
 

Starting event builder with writing data to a file:
Changed:
<
<
./daq_evtbuild -q 33554432 -m 7 -d file -o /d/hadeb03/may04 -x be ( ./daq_evtbuild -q queuesize -m number_of_subsystems -d file -o output_path -x file_prefix )
>
>
daq_evtbuild -q 33554432 -m 7 -d file -o /d/hadeb03/may04 -x be
( daq_evtbuild -q queuesize -m number_of_subsystems -d file -o output_path -x file_prefix )
 

Check for disk space on the available disks /d/hadeb03, /d/disk1, /d/disk2, /d/disk3
Line: 184 to 178
  On the event builder machines hadeb02 / hadeb03 you use
Changed:
<
<
./daq_netmem -q 33554432 -m7 -i UDP:127.0.0.1:2222 -i UDP:127.0.0.1:2223 -i UDP:127.0.0.1:2224 -i UDP:127.0.0.1:2225 -i UDP:127.0.0.1:2226 -i UDP:127.0.0.1:2227 -i UDP:127.0.0.1:2228
>
>
daq_netmem -q 33554432 -m7 -i UDP:127.0.0.1:2222 -i UDP:127.0.0.1:2223 -i UDP:127.0.0.1:2224 -i UDP:127.0.0.1:2225 -i UDP:127.0.0.1:2226 -i UDP:127.0.0.1:2227 -i UDP:127.0.0.1:2228
 

Revision 2
28 Jan 2005 - Main.MichaelTraxler
Line: 1 to 1
 

Line: 104 to 104
 

Shower

Changed:
<
<
Readout Host Script Cards shw r2-14 shw init IPC 0,..,11
>
>
Readout Host Script Cards
shw r2-14 shw init IPC 0,..,11
 

TOF

Line: 118 to 118
 

MU

Changed:
<
<
Readout Host Script Cards r2-35 trigconc init
>
>
Readout Host Script Cards
conc r2-35 trigconc init mu
  Status Info
Deleted:
<
<
Triggers rate: >viewrate d00e800c d00e8014 d00e808c d00e8098 d00e80e8
 
Added:
>
>
Triggers rate:
>viewrate d00e800c d00e8014 d00e808c d00e8098 d00e80e8
  LVL1 Rate LVL2 Rate RICH-Hit Rate Lepton Rate RICH-Hit-Mult. 1: 5796 2: 970 3: 767 4: 426 5: 1481 1: 6047 2: 969 3: 758 4: 399 5: 1385 1: 5933 2: 930 3: 699 4: 371 5: 1331
Added:
>
>
 
Changed:
<
<
RICH-Hit Rate: Rate of events with at least the required number of hits found by RICH-IPU
>
>
  • RICH-Hit Rate: Rate of events with at least the required number of hits found by RICH-IPU
  (usually at least one hit at the moment)
Changed:
<
<
Lepton Rate: Rate of events with at least the required number of leptons found by Matching Unit
>
>

  • Lepton Rate: Rate of events with at least the required number of leptons found by Matching Unit
  (usually at least one hit at the moment)
Changed:
<
<
RICH-Hit Mult: Accumulated number of RICH IPU hits
>
>

  • RICH-Hit Mult: Accumulated number of RICH IPU hits
  ( RICH-Hit Mult / RICH-Hit Rate ==> mean ring multiplicity in all ring events)

The difference between the lepton rate (which usually is the trigger algo rate) and the LVL2 rate comes from the downscaled events!
Changed:
<
<
Busy monitor: >busy_monitor
>
>
Busy monitor:
 
Added:
>
>
>busy_monitor
  LVL1: ---11- LVL2: ------ LVL1: 634*8- LVL2: 21265-- LVL1: 41362-- LVL2: ---21-
Added:
>
>
 

The numbers show how many times the subsystem was busy out of 10 ( - = 0; * = 10)
Line: 161 to 172
 

Starting event builder with writing data to a file:
Changed:
<
<
./daq_evtbuild -q 33554432 -m 7 -d file -o /d/hadeb03/may04 -x be ( ./daq_evtbuild -q queuesize -m number_of_subsystems -d file -o output_path -x file_prefix )
>
>
./daq_evtbuild -q 33554432 -m 7 -d file -o /d/hadeb03/may04 -x be ( ./daq_evtbuild -q queuesize -m number_of_subsystems -d file -o output_path -x file_prefix )
 

Check for disk space on the available disks /d/hadeb03, /d/disk1, /d/disk2, /d/disk3
Line: 172 to 183
 

On the event builder machines hadeb02 / hadeb03 you use
Changed:
<
<
./daq_netmem -m7 -i UDP:127.0.0.1:2222 -i UDP:127.0.0.1:2223 -i UDP:127.0.0.1:2224 -i UDP:127.0.0.1:2225 -i UDP:127.0.0.1:2226 -i UDP:127.0.0.1:2227 -i UDP:127.0.0.1:2228
>
>

./daq_netmem -q 33554432 -m7 -i UDP:127.0.0.1:2222 -i UDP:127.0.0.1:2223 -i UDP:127.0.0.1:2224 -i UDP:127.0.0.1:2225 -i UDP:127.0.0.1:2226 -i UDP:127.0.0.1:2227 -i UDP:127.0.0.1:2228
 

 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)