Difference: OEPReadoutTest (1 vs. 9)

Revision 9
04 Feb 2011 - Main.JoernWuestenfeld
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"

How to check data read out from OEP's

1. Login to lxhadesdaq

Changed:
<
<
Use vncviewer / krdc to connect to the running vnc session on lxhadesdaq.
With vncviewer use vncviewer lxhadesdaq:2 or start krdc and eneter lxhadesdaq:2 in the dialog. Use HADES DAQ password to login.
>
>
Use vncviewer / krdc to connect to the running vnc session on lxhadesdaq.
With vncviewer use vncviewer lxhadesdaq:2 or start krdc and enter lxhadesdaq:2 in the dialog. Use HADES DAQ password to login.
 

2. Take data (HLD file)

Line: 32 to 32
 
    • cd /home/hadaq/mdc_oepb/scripts; ./startup_optical.sh (This takes 2 minutes, two messages "verification failure" plus four times "Successfull" are normal)

3 Analyse data

Changed:
<
<
On desktop MDC Analysis go to console root and change into directory /misc/mdc/Hxydra/oep_test/Hydra/unpacking/analyse.
>
>
On desktop MDC Analysis go to console root and change into directory /misc/mdc/Hxydra/oep_test/HydraNew/unpacking/analyse.
Execute the following command:

. hsc-oeptest

  Edit the file unpacker.conf with your editor of choice e.g. kate. This file contains the configuration for the analysis process.
You should change only the following part:
In the section
# Output configuration
Line: 58 to 58
  the directive directory gives the path where the HLD files are located, while the directive files lists the hld files to be analyzed (without .hld extension!)
Changed:
<
<
Now run in the actual directory (/misc/mdc/Hydra/oep_test/Hydra/unpacking/analyse):

analyse test 10000

Wait until the programm finishes. The parameters to this program are:
>
>
Now run in the actual directory (/misc/mdc/Hydra/oep_test/HydraNew/unpacking/analyse):

analyse test 10000

Wait until the programm finishes. The parameters to this program are:
 
  1. Name of output file (test.root in example)
  2. Number of events to be processed (10000 in example)
  3. Number of first event (not mandatory, defaults to 1)
Revision 8
04 Feb 2011 - Main.AttilioTarantola
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"

How to check data read out from OEP's

Line: 69 to 69
 

To look at the plots, open the output file with root:

*root /tmp/test.root*

as given in the example above. Once the file is opened, start a ROOT browser (new TBrowser) and open the ROOT files directory, in which you will find the test.root file. Open it, and change to the directory monitorDir/mdcDir/meanhitsraw/fpc. Here you will find the histograms with the mean number of hits per FPC cable as function of MBO number.
Added:
>
>

....MeanHitPerDBO, all boards should be on.
 

5. Important commands:

trbflash program 0xfffd mdc_oepb/stapl/mdc_oepb_200911113.bit
Revision 7
20 Nov 2009 - Main.JoernWuestenfeld
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"

How to check data read out from OEP's

Line: 69 to 69
 

To look at the plots, open the output file with root:

*root /tmp/test.root*

as given in the example above. Once the file is opened, start a ROOT browser (new TBrowser) and open the ROOT files directory, in which you will find the test.root file. Open it, and change to the directory monitorDir/mdcDir/meanhitsraw/fpc. Here you will find the histograms with the mean number of hits per FPC cable as function of MBO number.
Added:
>
>

5. Important commands:

trbflash program 0xfffd mdc_oepb/stapl/mdc_oepb_200911113.bit

/home/hadaq/mdc_oepb/scripts/startup_optical.sh
  -- JoernWuestenfeld - 18 Nov 2009
Revision 6
19 Nov 2009 - Main.JanMichel
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"

How to check data read out from OEP's

Revision 5
19 Nov 2009 - Main.JanMichel
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"

How to check data read out from OEP's

Line: 10 to 10
 

  1. Use vnc on lxhadesdaq:2, login with DAQ password
  2. Use desktop p058 Test konsole etraxp058
    - daqop reset network
    - daqop set flash 1 oep
    - daqop reboot oep
Changed:
<
<
  1. Use konsole startup.pl
    - If you are working with etrax058:
    ./startup.pl -e etrax058
    otherwise
    ./startup.pl -e etraxp058
>
>
  1. Use konsole startup.pl Run ./startup.pl (in Directory /home/hadaq/trbsoft/daq/main/) with the following two options:
    • -e etraxname : name of trb (either etrax058 or etraxp058)
    • -m setting : to load a specific set of settings, i.e. thresh10, thresh20, thresha0 and / or calib

 
  1. Use console etraxp058
    - If you are on etrax*p*058:
    ./bin/readout_mdc -w 10000 -I 201 -o UDP:192.168.100.50:3322
    If you are on etarx058:
    ./bin/readout_mdc -w 10000 -I 201 -o UDP:140.181.75.158:3322
  2. Change to desktop Eventbuilder
    - console EB: daq_evtbuild -m 1 -S jan -I 1 -x md -d file -o /data/lxhadesdaq/mdctest/data/
Line: 19 to 23
  - ctrl + c in both consoles

If you have been disconnected from etrax

Changed:
<
<
  1. Log on to ETRAX using page etrax058 console p058 Test :
    - The TRB board is connected to the private network (see label on switches), then
    trb etraxp058
    Login as user root with password.
    - The TRB is connected to the public GSI network (see label on switches), then
    trb etrax058
  2. Program FPGAs on AddOn:
    cd /home/hadaq/mdc_oepb/scripts; ./startup_optical.sh (This takes 2 minutes, two messages "verification failure" plus four times "Successfull" are normal)
>
>
  1. Log on to ETRAX using page etrax058 console p058 Test :
    • The TRB board is connected to the private network (see label on switches), then
      • trb etraxp058
    • The TRB is connected to the public GSI network (see label on switches), then
      • trb etrax058
  2. Program FPGAs on AddOn:
    • cd /home/hadaq/mdc_oepb/scripts; ./startup_optical.sh (This takes 2 minutes, two messages "verification failure" plus four times "Successfull" are normal)
 

3 Analyse data

On desktop MDC Analysis go to console root and change into directory /misc/mdc/Hxydra/oep_test/Hydra/unpacking/analyse.
Revision 4
19 Nov 2009 - Main.JanMichel
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"

How to check data read out from OEP's

Line: 10 to 10
 

  1. Use vnc on lxhadesdaq:2, login with DAQ password
  2. Use desktop p058 Test konsole etraxp058
    - daqop reset network
    - daqop set flash 1 oep
    - daqop reboot oep
Changed:
<
<
  1. Use konsole startup.pl
    - If you are working with etarx058:
    ./startup.pl -e etrax058
    otherwise
    ./startup.pl -e etraxp058
  2. Use console etraxp058
    - If you are on etrax*p*058:
    ./bin/readout_mdc -w 10000 -I 201 -o UDP:140.181.75.158:3322
    If you are on etarx058:
    ./bin/readout_mdc -w 10000 -I 201 -o UDP:192.168.100.50:3322
>
>
  1. Use konsole startup.pl
    - If you are working with etrax058:
    ./startup.pl -e etrax058
    otherwise
    ./startup.pl -e etraxp058
  2. Use console etraxp058
    - If you are on etrax*p*058:
    ./bin/readout_mdc -w 10000 -I 201 -o UDP:192.168.100.50:3322
    If you are on etarx058:
    ./bin/readout_mdc -w 10000 -I 201 -o UDP:140.181.75.158:3322
 
  1. Change to desktop Eventbuilder
    - console EB: daq_evtbuild -m 1 -S jan -I 1 -x md -d file -o /data/lxhadesdaq/mdctest/data/
    - console NETMEM: daq_netmem -m 1 -i UDP:0.0.0.0:3322 -S jan
Line: 19 to 19
  - ctrl + c in both consoles

If you have been disconnected from etrax

Changed:
<
<
  1. Log on to ETRAX using page etrax058 console p058 Test :
    - The TRB board is connected to the private network (blue switch above power supplies), then
    telnet etraxp058
    Login as user root with password.
    - The TRB is connected to the public GSI network (white switches), then
    telnet etrax058
    Login as user root with password.
>
>
  1. Log on to ETRAX using page etrax058 console p058 Test :
    - The TRB board is connected to the private network (see label on switches), then
    trb etraxp058
    Login as user root with password.
    - The TRB is connected to the public GSI network (see label on switches), then
    trb etrax058
  2. Program FPGAs on AddOn:
    cd /home/hadaq/mdc_oepb/scripts; ./startup_optical.sh (This takes 2 minutes, two messages "verification failure" plus four times "Successfull" are normal)
 

3 Analyse data

On desktop MDC Analysis go to console root and change into directory /misc/mdc/Hxydra/oep_test/Hydra/unpacking/analyse.
Changed:
<
<
Edit the file unpacker.conf with your editor of coice e.g. kate. This file contains the configuration for the analysis process.
You should change only the following part:
In the section
>
>
Edit the file unpacker.conf with your editor of choice e.g. kate. This file contains the configuration for the analysis process.
You should change only the following part:
In the section
 
# Output configuration
[output]
Revision 3
19 Nov 2009 - Main.JoernWuestenfeld
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"

How to check data read out from OEP's

Changed:
<
<

1. Login to analysis machine

Login to lxg0441 as user mdc (ssh -X mdc@lxg0441). On this machine you have to set up the correct HYDRA environment by executing . hsc-oeptest.
Then change directory to /misc/mdc/Hydra/oep_test/Hydra/unpacking/analyse. Open with your editor of choice the file unpacker.conf. This contains the configuration for the analysis process.
You should change only the following part:
In the section
>
>

1. Login to lxhadesdaq

Use vncviewer / krdc to connect to the running vnc session on lxhadesdaq.
With vncviewer use vncviewer lxhadesdaq:2 or start krdc and eneter lxhadesdaq:2 in the dialog. Use HADES DAQ password to login.

2. Take data (HLD file)

  1. Use vnc on lxhadesdaq:2, login with DAQ password
  2. Use desktop p058 Test konsole etraxp058
    - daqop reset network
    - daqop set flash 1 oep
    - daqop reboot oep
  3. Use konsole startup.pl
    - If you are working with etarx058:
    ./startup.pl -e etrax058
    otherwise
    ./startup.pl -e etraxp058
  4. Use console etraxp058
    - If you are on etrax*p*058:
    ./bin/readout_mdc -w 10000 -I 201 -o UDP:140.181.75.158:3322
    If you are on etarx058:
    ./bin/readout_mdc -w 10000 -I 201 -o UDP:192.168.100.50:3322
  5. Change to desktop Eventbuilder
    - console EB: daq_evtbuild -m 1 -S jan -I 1 -x md -d file -o /data/lxhadesdaq/mdctest/data/
    - console NETMEM: daq_netmem -m 1 -i UDP:0.0.0.0:3322 -S jan
    - wait for events (take a look at konsole EB), minimum 10.000*
    - ctrl + c in both consoles

If you have been disconnected from etrax

  1. Log on to ETRAX using page etrax058 console p058 Test :
    - The TRB board is connected to the private network (blue switch above power supplies), then
    telnet etraxp058
    Login as user root with password.
    - The TRB is connected to the public GSI network (white switches), then
    telnet etrax058
    Login as user root with password.

3 Analyse data

On desktop MDC Analysis go to console root and change into directory /misc/mdc/Hxydra/oep_test/Hydra/unpacking/analyse. Edit the file unpacker.conf with your editor of coice e.g. kate. This file contains the configuration for the analysis process.
You should change only the following part:
In the section
 
# Output configuration
[output]
Line: 29 to 48
  the directive directory gives the path where the HLD files are located, while the directive files lists the hld files to be analyzed (without .hld extension!)
Changed:
<
<

2. Take data (HLD file)

3 Analyse data

Go back to terminalwindow where you are loggen in at lxg0441. Now run in the actual directory (/misc/mdc/Hydra/oep_test/Hydra/unpacking/analyse):

analyse test 10000

Wait until the programm finishes. The parameters to this program are:
>
>
Now run in the actual directory (/misc/mdc/Hydra/oep_test/Hydra/unpacking/analyse):

analyse test 10000

Wait until the programm finishes. The parameters to this program are:
 
  1. Name of output file (test.root in example)
  2. Number of events to be processed (10000 in example)
  3. Number of first event (not mandatory, defaults to 1)
Revision 2
18 Nov 2009 - Main.JoernWuestenfeld
Line: 1 to 1
 
META TOPICPARENT name="DaqUpgradeMDCOverview"

How to check data read out from OEP's

 
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)