Difference: VeloHowtoDAQ (30 vs. 31)

Revision 312007-08-23 - JanBuytaertSecondary

Line: 1 to 1
 
META TOPICPARENT name="VELOTestbeam"
Guide to DAQ operations: (supposing cold start == crate reboot || pcs reboot && etc)*
  1. You will need to run PVSS on the windows PC (pcveloassembly3, on the left). Start -> All Programs -> PVSS II 3.0 -> PVSS II Project Administration . This starts PVSS and opens a window "PVSS Project Administration...".
Line: 6 to 6
 
  1. you will need the Specs to be running. There are some scripts and there will be even more of them located inside ~lhcbvelo/AssemblyLabDaqScripts/. execute./RunSpecsv2r0 from there. make sure that the firewall is stopped on the specs server side (type: sudo service iptables stop).
  2. on Vision_1:SingleCB panel, make sure you selected the right SPECSnode (named pcveloassembly4) and the first one of the SPECS ports Master ID, which is the one we usually use (05 pci:1 port:1, in the assembly lab). CB address should be 2 and SPECS speed 128 kHz.
  3. (this step is not needed but we leave it just temporarily here) You have to start the CCPCs. Sit at pcveloassembly4 as lhcbvelo and do ssh tfc@odinv220. Then, in odin, execute the script: source .VeloSetup and leave that window aside (do not close it). You need to wait till the automatic loading of FPGAs is done.
Changed:
<
<
  1. It's a good time to start the TELL1 daq program. just type ./startAssemblyLabTell1s from the AssemblyLabDaqScripts directory.
>
>
  1. It's a good time to start the TELL1 daq program. just type ./startAssemblyLabTell1s_digitisationScan from the AssemblyLabDaqScripts directory.
 
  1. Start a couple of windows to monitor the tell1s. ssh velo@tell029 and ssh velo@tell030. Then, in each tell1 window type ./startConsole.
  2. If everything is fine you should have on pcveloassembly3 your PVSS panel open called SingleCB. From the Temperatures tab, choose the ELMB and press load table. Then press Start. This should start temperatures read-out and logging.
  3. Search for the PVSS TFC Vision_1:fwFSM panel (FSMOperate.pnl). Click on +TFC to get the list of ODINs. Pick Partition_OdinV2_20 and highlight it. Right click, wait, and choose View. If the panel is not "taken" i.e. the little lock in the box "State" next to Partition_OdinV2_20 is open and not green, then click on it and do Take. It should go green. Then you can operate.
  4. If you are in the situation where the little lock is red, and you are told that you are in local, then you have a problem from some previously hanging session. Close the Partition_OdinV2_20 window, go back to the PVSS panel, right click on the OdinV2 _20 and click start/restart tree. Then view the window again.
  5. In the ODIN Initialisation panel click on "Select Recipe" and from the Cache choose Kazu's favourite: TEST/ODIN/R_All/VeloTestPulse1L0ConsecDigitisationScan. Click on "set recipe". You should get a yellow NOT_READY. On the top panel ("state") click configure and choose send.
  6. On the right side of the panel, in the boxes L0 trigger, Command and Other tick all boxes which have a green dot, untick all the others. Configure again.
  7. Now you can start the run.
  8. The Specs server bar should be green (if not just execute RunSpecsv2r0 again, wont harm). You should be ready to use the Master control Panel.
  9. from the Master Control press the button off to cascade down to GetReady. this will configure the whole control board and check which cables are connected to something.
  10. press the LV on. this wil enable the low voltages from the repeater boards tu the hybrid.
  11. press on the off states to go to on. this will configure the beetles.
  12. start the triggers from the Odin Control panel or the TFC partition (the one that pops up when you load the recipe)
  13. go to velo@velotestNOSPAMPLEASE.daq.lhcb this is the DAQ pc (you need to be a velo expert to get inside). type sudo su- to become root
  14. type source setupvelodaq. this will lead you to /home/velo/eventBuilder/writeEventsToBinary and load the paths.
  15. optional step: to spy on on the ethernet card type tethereal -i eth1  and check if data of both tell1s arrive 
  16. to acquire data just type: ./takeData <filename string> <module name> <N events> it will creat the directory /scratch/lhcbvelo/assemblyData/<ModuleName> (if it doesnt exist), and copy the files to that place on pcveloassembly4. the <filename string> will have .bin added to it.
  17. Analyse the data:
    1. (Open a fresh terminal) and do
      1. [pcveloassembly4] ~ > source assemblyVetraSetup from the AssemblyLabDaqScripts directory
      2. [pcveloassembly4] ~/cmtuser/Velo/Vetra/v2r3/cmt > vi ../options/fullsnapshot.opts
    2. change the two lines:
      1. "DATA='file:///scratch/lhcbvelo/assemblyData/Mxx/modxx_snapshot_ntp_whatever.bin' SVC='LHCb::MDFSelector'"
      2. OutputFile = "/scratch/lhcbvelo/assemblyData/Mxx/modxx_snapshot_ntp_whatever.root";
    3. Then, do
      1. [pcveloassembly4] ~/cmtuser/Velo/Vetra/v2r3/cmt > fullSnapshot
      2. [pcveloassembly4] ~/cmtuser/Velo/Vetra/v2r3/cmt > root
      3. root [0] .L ../macros/badChannelX.C
      4. root [1] badChannel("assemblyData/modxx_snapshot_ntp_invac1.root",29,'r',xx);
  18. Put in elog the 4 noise jpg plots and the bad channel lists
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback