Difference: TgcExpertOperation (1 vs. 36)

Revision 362013-01-14 - masato

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"

TGC FE expert guide

Line: 11 to 11
 

How to recover from a power cut

Added:
>
>

CCI/HSC crates power supply control and monitoring

 

PS Reset / DCS Reset : ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing
  • PS Board Reset
Line: 233 to 236
 
META FILEATTACHMENT attachment="Cosmic_TGC_A.png" attr="" comment="" date="1314706360" name="Cosmic_TGC_A.png" path="Cosmic_TGC_A.png" size="25549" stream="Cosmic_TGC_A.png" tmpFilename="/usr/tmp/CGItemp6963" user="satoshi" version="1"
META FILEATTACHMENT attachment="Cosmic_TGC_C.png" attr="" comment="" date="1314706377" name="Cosmic_TGC_C.png" path="Cosmic_TGC_C.png" size="20327" stream="Cosmic_TGC_C.png" tmpFilename="/usr/tmp/CGItemp7044" user="satoshi" version="1"
META FILEATTACHMENT attachment="muon_2012_11_28.pdf" attr="" comment="" date="1354209542" name="muon_2012_11_28.pdf" path="muon_2012_11_28.pdf" size="63204" stream="muon_2012_11_28.pdf" tmpFilename="/usr/tmp/CGItemp13463" user="masato" version="1"
Added:
>
>
META FILEATTACHMENT attachment="TGC_CCIHSC_PowerMonitor_20130114.pptx" attr="" comment="" date="1358180277" name="TGC_CCIHSC_PowerMonitor_20130114.pptx" path="TGC_CCIHSC_PowerMonitor_20130114.pptx" size="779276" stream="TGC_CCIHSC_PowerMonitor_20130114.pptx" tmpFilename="/usr/tmp/CGItemp13687" user="masato" version="1"
META FILEATTACHMENT attachment="TGC_CCIHSC_PowerMonitor_20130114.pdf" attr="" comment="" date="1358180294" name="TGC_CCIHSC_PowerMonitor_20130114.pdf" path="TGC_CCIHSC_PowerMonitor_20130114.pdf" size="1601870" stream="TGC_CCIHSC_PowerMonitor_20130114.pdf" tmpFilename="/usr/tmp/CGItemp13725" user="masato" version="1"

Revision 352012-11-29 - masato

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"

TGC FE expert guide

Changed:
<
<

TgcOperationExpertManual

>
>

Another experts' instruction here

How to recover from a power cut

 

PS Reset / DCS Reset : ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing
Changed:
<
<
  • PS Board Reset
    1. login to SBC for TTC crate
>
>
  • PS Board Reset
    1. login to SBC for TTC crate
 
      • A-Side: sbc-tgc-tcc-eca-01.cern.ch
      • C-Side: sbc-tgc-tcc-ecc-01.cern.ch
Changed:
<
<
    1. source the setup script for TGC Frontend environment
      source /det/muon/TGCFE/installed/bin/TGC_env.sh
    2. run the following command
      TgcTtcvi -c !PsReset 
    3. type yes if you are sure to send the signal.

  • DCS Reset
    1. loguin to SBC and source the setup script (same as PsReset)
    2. run the following command
      TgcTtcvi -c DcsReset 
    3. type yes if you are sure to send the signal.
>
>
    1. source the setup script for TGC Frontend environment
      source /det/muon/TGCFE/installed/bin/TGC_env.sh
    2. run the following command
      TgcTtcvi -c !PsReset 
    3. type yes if you are sure to send the signal.

  • DCS Reset
    1. loguin to SBC and source the setup script (same as PsReset)
    2. run the following command
      TgcTtcvi -c DcsReset 
    3. type yes if you are sure to send the signal.
 

open TGC ROD Status panel

  • You can open TGC Rod status panel alone without TDAQ panel.
Changed:
<
<
    • First, you long in to ATLAS point 1 computer via "atlasgw" from your computer.
       ssh -Y atlasgw 
    • pc-tgc-daq-eca-01 or pc-tgc-daq-ecc-01 is one of good computers to login for this purpose.
    • You source a set-up file and run a command.
       source  /det/muon/TGC/scripts/setupGlobal.sh 
       TGCpanel 
>
>
    • First, you long in to ATLAS point 1 computer via "atlasgw" from your computer.
       ssh -Y atlasgw 
    • pc-tgc-daq-eca-01 or pc-tgc-daq-ecc-01 is one of good computers to login for this purpose.
    • You source a set-up file and run a command.
       source  /det/muon/TGC/scripts/setupGlobal.sh 
       TGCpanel 
 
    • Thne, the panel will appear.

Save All Updated" to save all changes.

>
>
      1. check the all attributes in the list are correct or not.
  1. Please execute "FIle --> Save All Updated" to save all changes.
 
    • PLEASE input some comments to be able to identify the modification.
Changed:
<
<
  1. NEW Dump the TGCFE parametars by useing local xml file as a test.
    dumpTgcFEParameters -f /det/tgc/db/tdaq-04-00-01
>
>
  1. NEW Dump the TGCFE parametars by useing local xml file as a test.
    dumpTgcFEParameters -f /det/tgc/db/tdaq-04-00-01
 
    • If correct parameter dumped, go to next step.
Changed:
<
<
    • ALERT! If NOT correct parametrs dumped, please do follwoing two things. DON'T commit the xml files.
      1. clean up /det/muon/TGCFE/config/FrontEnd/oncall/dump and try to perfome dumpTgcFEParameters.
      2. If you get not correct parameters again, please go back to step 2 and make parameters again.
  1. Please execute "File --> Commit User Repository" to commit all updated xml files to CVS server.
    1. The same comments which you input above will be shown in the window.
    2. Please click commit button to upload files.
  2. If no error message is shown, please post message to the e-log.
  3. For avoiding mis-understanding, Announce Shiftleader and Run Control Shifter, what you changed,why you changed.
>
>
    • ALERT! If NOT correct parametrs dumped, please do follwoing two things. DON'T commit the xml files.
      1. clean up /det/muon/TGCFE/config/FrontEnd/oncall/dump and try to perfome dumpTgcFEParameters.
      2. If you get not correct parameters again, please go back to step 2 and make parameters again.
  1. Please execute "File --> Commit User Repository" to commit all updated xml files to CVS server.
    1. The same comments which you input above will be shown in the window.
    2. Please click commit button to upload files.
  2. If no error message is shown, please post message to the e-log.
  3. For avoiding mis-understanding, Announce Shiftleader and Run Control Shifter, what you changed,why you changed.
 
    • What you changed (/atlas/oks/tdaq-04-00-01/muons/segments/TGC/FE/TGCFE-A(&C)_Segment.data.xml)
    • Why you changed (updating mask parameter)

Chcek eLMB Internal mode at EIFI

Deleted:
<
<
When there is [1] power glitch or [2] LV power-cycle, it can be that wrong eLMB modes are configured into eLMB at EIFI. In such a case, please check internal modes of eLMB, following the instruction.
 
Changed:
<
<
  1. navigate down the FSM tree:
    • TGC -> SIDE -> DCS -> Driver -> DCS EIFI -> ELMB EIFI
>
>
When there is [1] power glitch or [2] LV power-cycle, it can be that wrong eLMB modes are configured into eLMB at EIFI. In such a case, please check internal modes of eLMB, following the instruction.

  1. navigate down the FSM tree:
    • TGC -> SIDE -> DCS -> Driver -> DCS EIFI -> ELMB EIFI
 
    • Note that the FSM node itself is disabled. This is done on purpose and has nothing with this action.
Changed:
<
<
  1. compare values between "Image" and "Current".
>
>
  1. compare values between "Image" and "Current".
 
Changed:
<
<
  1. If there is inconsistency found, please fixed them by left click on the name of eLMB. (the value in leftmost column)
>
>
  1. If there is inconsistency found, please fixed them by left click on the name of eLMB. (the value in leftmost column)
 

Delay Scan

Changed:
<
<
  1. launching DAQ_Panel
    • TDAQ ->DAQPanel
>
>
  1. launching DAQ_Panel
    • TDAQ ->DAQPanel
 
    • ( TDAQ_Configuration )
      • Setup Script: /det/muon/TGCFE/installed/bin/setup_partTGC_DelayScan.sh
      • Part Name: partTGC_DelayScan
Line: 236 to 202
 
    • Click "Read Info" button
Changed:
<
<
  1. executing the script for DelayScan
    • $> cd /det/muon/TGCFE/TGCFeOperation/DelayScan/script
    • $> sh DelayScan.sh
>
>
  1. executing the script for DelayScan
    • $> cd /det/muon/TGCFE/TGCFeOperation/DelayScan/script
    • $> sh DelayScan.sh
 
      • Delayscan will start. It will take about 30 minutes until finish.
Changed:
<
<
  1. transporting raw data to out of P1 machine
>
>
  1. transporting raw data to out of P1 machine
 
    • Raw data of DelayScan are put in "/det/muon/TGCFE/TGCFeOperation/DelayScan/script/rootfile/". you need to copy this files to TGC local machine (pc-tgc-calsrv-01). Please use the GUI for TgcCalibration.("https://pc-atlas-www.cern.ch/twiki/pub/Main/HowToRunTgcCalibration").
Changed:
<
<
  1. data analysis
  • Decoding data and making timing histograms. Doing at pc-tgc-calsrv-01. *setup *sourse /det/muon/TGCFE/installed/bin/TGC_env.sh
>
>
  1. data analysis
  • Decoding data and making timing histograms. Doing at pc-tgc-calsrv-01. *setup *sourse /det/muon/TGCFE/installed/bin/TGC_env.sh
 
    • data decoding
      • do_DecodingDelayscan.sh [runnum]
    • data analysis
Changed:
<
<
      • $> cd /det/muon/TGCFE/TGCFeOperation/DelayScan/script
      • $> sh cable_ASDall.sh [runnum]
>
>
      • $> cd /det/muon/TGCFE/TGCFeOperation/DelayScan/script
      • $> sh cable_ASDall.sh [runnum]
 
    • feed buck timing
      • under construction
Line: 261 to 224
  Use part_TGC2. Setup partition as figures show.
Changed:
<
<
Cosmic_TGC_A.png Cosmic_TGC_C.png
>
>
Cosmic_TGC_A.png Cosmic_TGC_C.png
 

TgcExpertOperationObsoletes

Line: 270 to 232
 
META FILEATTACHMENT attachment="RDAQPanel_DelayScan.png" attr="" comment="" date="1271512688" name="RDAQPanel_DelayScan.png" path="RDAQPanel_DelayScan.png" size="83809" stream="RDAQPanel_DelayScan.png" tmpFilename="/usr/tmp/CGItemp33898" user="ysuzuki" version="1"
META FILEATTACHMENT attachment="Cosmic_TGC_A.png" attr="" comment="" date="1314706360" name="Cosmic_TGC_A.png" path="Cosmic_TGC_A.png" size="25549" stream="Cosmic_TGC_A.png" tmpFilename="/usr/tmp/CGItemp6963" user="satoshi" version="1"
META FILEATTACHMENT attachment="Cosmic_TGC_C.png" attr="" comment="" date="1314706377" name="Cosmic_TGC_C.png" path="Cosmic_TGC_C.png" size="20327" stream="Cosmic_TGC_C.png" tmpFilename="/usr/tmp/CGItemp7044" user="satoshi" version="1"
Added:
>
>
META FILEATTACHMENT attachment="muon_2012_11_28.pdf" attr="" comment="" date="1354209542" name="muon_2012_11_28.pdf" path="muon_2012_11_28.pdf" size="63204" stream="muon_2012_11_28.pdf" tmpFilename="/usr/tmp/CGItemp13463" user="masato" version="1"

Revision 342012-06-09 - wakajun

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"

TGC FE expert guide

Added:
>
>

TgcOperationExpertManual

 

PS Reset / DCS Reset : ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing
  • PS Board Reset
Line: 84 to 86
 
  • location of log-file ... atlasgw:/clients/scratch/logs/tdaq-04-00-01/ATLAS/
    side & cratefile name
    A-Side, TTCTGCTTC-A_RCD_PhysicsMode_sbc-tgc-tcc-eca-01.cern.ch_[UTC].out/err
    C-Side, TTCTGCTTC-C_RCD_PhysicsMode_sbc-tgc-tcc-ecc-01.cern.ch_[UTC].out/err
    A-Side, FETGCFE-RCD_ECA[01-04]_Physics_sbc-tgc-cci-eca-[01-04].cern.ch_[UTC].out/err
    C-Side, FETGCFE-RCD_ECC[01-04]_Physics_sbc-tgc-cci-ecc-[01-04].cern.ch_[UTC].out/err
    A-Side, SLTGCSL_ReadoutApplication-CSL[04-06]_sbc-tgc-csl-lvl1-[04-06].cern.ch_[UTC].out/err
    C-Side, SLTGCSL_ReadoutApplication-CSL[01-03]_sbc-tgc-csl-lvl1-[01-03].cern.ch_[UTC].out/err
Changed:
<
<

Analyze Calibration DATA and update parameter and OKS : 3-STEPS (EXPERT ONLY)

Analysis of Calibration data

  • preparation : login, go to working space, set environment (the computer OUTSIDE of Point1.)
    • $ ssh -X pc-tgc-calsrv-01.cern.ch;
    • $ cd /det/tgc/Monitoring/hist ;
    • $ source /det/muon/TGCFE/installed/bin/TGC_env.sh;
  • Then, get rod files from Point 1
    • Has the TGC shifter already copied data to shared disk?
      • If data transfer has been completed by shifter, it is found under /det/tgc/data/runs/
      • If it is not the case, you should copy them by yourself with following procedure.
>
>

Analyze Calibration DATA and update parameter and OKS : 3-STEPS

step1: Analysis of Calibration data

  1. preparation : login, go to working space, set environment (the computer OUTSIDE of Point1.)
    ssh -X pc-tgc-calsrv-01.cern.ch
    cd /det/tgc/Monitoring/hist 
     source   /det/muon/TGCFE/installed/bin/TGC_env.sh
  2. Then, get rod files from Point 1
 
    • Get files from Point 1 (replace "runumber")
Changed:
<
<
      • $ sh OncallTool_GetFilesFromPoint1.sh runnumber; (copy data with SCP, your passswd @P1 is required)
  • Next, decode data
    • $ do_Decoding_pararel.sh runnumber 100000 (decode 100k events : for Random)
    • $ do_Decoding_pararel.sh runnumber -1 (decode all data : for asd and track)
  • Next, run analysis program.
>
>
sh OncallTool_GetFilesFromPoint1.sh RandomRunNo TrackRunNo ASDRunNo
or
sh OncallTool_GetFilesFromPoint1_single.sh RunNo
Copy data with SCP, your passswd @P1 is required. * Check if TGC shifter copied data to shared disk
      • If data transfer has been completed by shifter, it is found under /det/tgc/data/runs/
      • If it is not the case, you should copy them by yourself with following procedure.
  1. Decode data
    do_Decoding_pararel.sh runnumber 100000 
    do_Decoding_pararel.sh runnumber -1
    Random : decode 100k events. ASD and Track : decode all events.
  2. Run analysis program.
 
    • Case : ASD
Changed:
<
<
      • (1) run the analysis code and check the result.
      • sh OncallTool_MissingChannelCheck.sh runnumber
      • Check the number and comper them to the reference in parenthesis "()"
      • (2) If it looks strange, check histogram with
        • sh setup.sh (will open familiar GUI tool)
      • (3)Finally send it to USA 15 in Point1. Following instruction will be shown with appropriate parameter so that you can just copy & paset smile
        • (3-1)transfer the missing channels list to computer in the Point1 as below.
        • scp /det/tgc/Monitoring/hist/missinglist/run${runnum}_missing.txt  atlasgw:/shared/data/crmuon/
        • (3-2)after that, login to atlasgw, and do this.
        • ssh atlasgw
        • mv /shared/data/crmuon/run${runnum}_missing.txt  /det/tgc/Monitoring/hist/missinglist
>
>
      1. run the analysis code and check the result.
        sh OncallTool_MissingChannelCheck.sh runnumber
        Check the number and comper them to the reference in parenthesis "()"
      2. If it looks strange, check histogram with
        sh setup.sh 
        (will open familiar GUI tool)
      3. Finally send it to USA 15 in Point1. Following instruction will be shown with appropriate parameter so that you can just copy & paset smile
        1. transfer the missing channels list to computer in the Point1 as below.
          scp /det/tgc/Monitoring/hist/missinglist/run${runnum}_missing.txt  atlasgw:/shared/data/crmuon/
        2. after that, login to atlasgw, and do this.
          ssh atlasgw
          mv /shared/data/crmuon/run${runnum}_missing.txt  /det/tgc/Monitoring/hist/missinglist
 
    • Case : Random
Changed:
<
<
      • (1) run the analysis code and check the result.
      • sh OncallTool_NoisyChannelList.sh   runnumber
      • (2) If noisy channel(s) was found, prepare configuration parameter. Following instruction will be shown with appropriate parameter so that you can just copy & paset smile
        • (2-0) check which channel is found a new noisy channel.
        • EXCEPTION It is known that we cannot kill 1 single noisy channel
          C       05      0       E       W       2       2       41 
          . In case only this channel is listed, it is not needed to update parameters.
        • (2-1) send noisy channel list to point 1.
        • scp /det/tgc/Monitoring/hist/noisylist/run${runnum}_bcidmasklist.txt atlasgw:/shared/data/crmuon/
        • (2-2) Log in to Point 1 machine.
        •  ssh atlasgw 
        •  cp    /shared/data/crmuon/run${runnum}_bcidmasklist.txt  /det/muon/TGCFE/src/tgc_hw/scripts/noisy_channels/
        • (2-3) run a update command. I recommend to use "screen" command before do followings.
        •  screen  
        •  cd /det/tgc/FEtest/scripts/expert/ ; sh update_psb_parameters.sh
        • [new!!]The program will ask you to check the new parameter showing the parameter contents. Please compare it to last on-call shift summary and confirmed the difference is reasonable.
          • Hint : Did you miss-type "yes" ? You don't have to wait for preparing parameters again. try below.
          •  (this is a command to restart the process.) $ cd /det/tgc/FEtest/scripts/expert/ ; sh put_psb_DetMuonTgcfe.sh
        • After it finishes, upload parameters to OKS. see "Upload parameters (text-base) to ORACLE" in this page.
>
>
      1. run the analysis code and check the result.
        sh OncallTool_NoisyChannelList.sh   runnumber
      2. If noisy channel(s) was found, prepare configuration parameter. Following instruction will be shown with appropriate parameter so that you can just copy & paset smile
        1. check which channel is found a new noisy channel. EXCEPTION It is known that we cannot kill 1 single noisy channel
          C       05      0       E       W       2       2       41 
          . In case only this channel is listed, it is not needed to update parameters.
        2. send noisy channel list to point 1.
          scp /det/tgc/Monitoring/hist/noisylist/run${runnum}_bcidmasklist.txt atlasgw:/shared/data/crmuon/
        3. Log in to Point 1 machine.
           ssh atlasgw 
           cp    /shared/data/crmuon/run${runnum}_bcidmasklist.txt  /det/muon/TGCFE/src/tgc_hw/scripts/noisy_channels/
        4. run a update command. I recommend to use "screen" command before do followings.
           screen  
           cd /det/tgc/FEtest/scripts/expert/ ; sh update_psb_parameters.sh
          The program will ask you to check the new parameter showing the parameter contents. Please compare it to last on-call shift summary and confirmed the difference is reasonable.
          TIP Did you miss-type "yes" ? You don't have to wait for preparing parameters again. try below.
           (this is a command to restart the process.) $ cd /det/tgc/FEtest/scripts/expert/ ; sh put_psb_DetMuonTgcfe.sh
        5. After it finishes, upload parameters to OKS. see "Upload parameters (text-base) to ORACLE" in this page.
          TIP If you found new missing channels, please do follwoing two things before updating missinglist in P1.
        • v-threhold up/down operation.
          1. Set value for a_direction as "+" insted of "to" ,then set value for s_val as 0.01.
          2. Set value for s_direction as "- " insted of "to" ,then set value for s_val as 0.01.
        • If the situation doesn't improve, please check the hitprofile to figure out a position of the problem. And please consider how to access to it during a technical stop, long shutdown,,, etc.
 
    • Case : Track
Changed:
<
<
      • (1) Open a gui tool.
      • sh setup.sh
      • (2) do "Trigger/Readout cor" with "all BW" option.
      • (3) histogram will be produces in the directory "psfile". Check it.
  • Finally, report the results.

Upload parameters (text-base) to ORACLE

  • generate new parameter files according to the result of the test during the daily calibration hour (see below).
    • login to the TGC machine;
      pc-tgc-daq-ecc-01   or   pc-tgc-mon-rod-01 
    • source the setup script (if not yet)
>
>
      1. Open a gui tool.
        sh setup.sh
      2. do "Trigger/Readout cor" with "all BW" option.
      3. Histogram will be produces in the directory "psfile". Check it.
  1. Finally, report the results.

step 2: Upload parameters (text-base) to ORACLE

generate new parameter files according to the result of the test during the daily calibration hour (see below).
  1. Login to the TGC machine;
    pc-tgc-daq-eca-01, pc-tgc-daq-ecc-01 or pc-tgc-mon-rod-01 
  2. Source the setup script (if not yet)
 
/det/muon/TGCFE/installed/bin/TGC_env.sh
Changed:
<
<
    • move to the following directory;
>
>
  1. Move to the following directory;
 
cd /det/muon/TGCFE/installed/bin/oracle/
Changed:
<
<
    • run a wrapper script;
>
>
  1. Run a wrapper script;
 
auto_upload.sh 
Changed:
<
<
    • type yes and enter # of trial (if you don't try to upload yet, please input 0 as the number)
    • Then, the following processes will be carried out;
      1. start reading text file (stored in /det/muon/TGCFE/config/Frontend/)
      2. uploading parameters to ORACLE
      3. compare parameters in between text file and ORACLE
    • rule of DB tag (generated automatically):
>
>
  1. Type yes and enter # of trial (if you don't try to upload yet, please input 0 as the number)
  2. Then, the following processes will be carried out;
    1. start reading text file (stored in /det/muon/TGCFE/config/Frontend/)
    2. uploading parameters to ORACLE
    3. compare parameters in between text file and ORACLE
  3. rule of DB tag (generated automatically):
 
      • Physics_[date]_normal_[# of trial] (3 out-of 4)
      • Physics_[date]_l67_[# of trial] (2 out-of 2)
      • Example: Physics_100301_normal_0, Physics_100301_l67_0
Changed:
<
<
    • Finally, the result of the comparison is shown in the terminal. If there is no inconsistent parameter, please post the message to e-log.
    • After it finishes, upload parameters to OKS. see "Change OKS xml files for the global partition" in this page.
>
>
  1. Finally, the result of the comparison is shown in the terminal. If there is no inconsistent parameter, please post the message to e-log.
  2. After it finishes, upload parameters to OKS. see "Change OKS xml files for the global partition" in this page.
 
Changed:
<
<

Change OKS xml files for the global partition

  • Do not perform the following operation if you do not understand what you are doing
    • login to the TGC machine, which SLC5 is running (last update; 2010.6.4).
      pc-tgc-daq-ecc-01   or   pc-tgc-mon-rod-01 
    • source the setup script (if not yet)
>
>

step 3: Change OKS xml files for the global partition

ALERT! Do not perform the following operation if you do not understand what you are doing
<---* login to the TGC machine, which SLC5 is running (last update; 2010.6.4).
     
pc-tgc-daq-eca-01, pc-tgc-daq-ecc-01 or  pc-tgc-mon-rod-01 
-->
  1. source the setup script (if not yet)
 
/det/muon/TGCFE/installed/bin/TGC_env.sh
Changed:
<
<
    • move to the following directory and source the script;
>
>
  1. move to the following directory and source the script;
 
cd /det/tgc/db/
source mycheckout.sh
Changed:
<
<
    • Then, the oks_dsata_editor GUI pannel will be appeared in your terminal automatically.
    • Please change the attribute which you want.
>
>
  1. Then, the oks_dsata_editor GUI pannel will be appeared in your terminal automatically.
  2. Please change the attribute which you want.
 
      • Example: change Oracle DB tag for Frontend configuration
Changed:
<
<
        1. search TGCFE_DBSetting class in the list (enter the class name in "Matching names of classes" box)
        2. double click the class and open it (new window will be shown)
        3. sort the list by FE_Trigger (or FE_Mask or FE_Config), and then you can find some objects with "Physics_xxxx_yyyy_zzzz".
        4. double click these objects, and right click the following attribute to change the DB tag;
>
>
      1. search TGCFE_DBSetting class in the list (enter the class name in "Matching names of classes" box)
      2. double click the class and open it (new window will be shown)
      3. sort the list by FE_Trigger (or FE_Mask or FE_Config), and then you can find some objects with "Physics_xxxx_yyyy_zzzz".
      4. double click these objects, and right click the following attribute to change the DB tag;
 
          • FE_Trigger
          • FE_Mask
          • FE_Config
          • (Please note that you should change all of them one-by-one. More easy way will be implemented soon.)
Changed:
<
<
        1. check the all attributes in the list are correct or not.
    • Please execute "FIle --> Save All Updated" to save all changes.
>
>
      1. check the all attributes in the list are correct or not.
  1. Please execute "FIle --> Save All Updated" to save all changes.
 
      • PLEASE input some comments to be able to identify the modification.
Changed:
<
<
    • Please execute "File --> Commit User Repository" to commit all updated xml files to CVS server.
      • The same comments which you input above will be shown in the window.
      • Please click commit button to upload files.
    • If no error message is shown, please post message to the e-log.
    • For avoiding mis-understanding, Announce Shiftleader and Run Control Shifter, what you changed,why you changed.
      • What you changed (/atlas/oks/tdaq-02-00-03/muons/segments/TGC/FE/TGCFE-A(&C)_Segment.data.xml)
>
>
  1. NEW Dump the TGCFE parametars by useing local xml file as a test.
    dumpTgcFEParameters -f /det/tgc/db/tdaq-04-00-01
    • If correct parameter dumped, go to next step.
    • ALERT! If NOT correct parametrs dumped, please do follwoing two things. DON'T commit the xml files.
      1. clean up /det/muon/TGCFE/config/FrontEnd/oncall/dump and try to perfome dumpTgcFEParameters.
      2. If you get not correct parameters again, please go back to step 2 and make parameters again.
  2. Please execute "File --> Commit User Repository" to commit all updated xml files to CVS server.
    1. The same comments which you input above will be shown in the window.
    2. Please click commit button to upload files.
  3. If no error message is shown, please post message to the e-log.
  4. For avoiding mis-understanding, Announce Shiftleader and Run Control Shifter, what you changed,why you changed.
    • What you changed (/atlas/oks/tdaq-04-00-01/muons/segments/TGC/FE/TGCFE-A(&C)_Segment.data.xml)
 
      • Why you changed (updating mask parameter)

Chcek eLMB Internal mode at EIFI

Revision 332012-06-08 - wakajun

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"

TGC FE expert guide

Line: 28 to 28
 
  • You can open TGC Rod status panel alone without TDAQ panel.
    • First, you long in to ATLAS point 1 computer via "atlasgw" from your computer.
       ssh -Y atlasgw 
Changed:
<
<
    • pc-tgc-daq-ecc-01 is one of good computers to login for this purpose.
>
>
    • pc-tgc-daq-eca-01 or pc-tgc-daq-ecc-01 is one of good computers to login for this purpose.
 
    • You source a set-up file and run a command.
       source  /det/muon/TGC/scripts/setupGlobal.sh 
       TGCpanel 
    • Thne, the panel will appear.
Added:
>
>
 

Reboot all cci sbcs

  • procedure
Line: 79 to 81
 
  • In case "semaphore" is locked, you will see following messages

How to find ERROR LOG ?? (for further investigation of problems reported in MRS)

Changed:
<
<
  • location of log-file ... atlasgw:/clients/scratch/logs/tdaq-02-00-03/ATLAS/
>
>
  • location of log-file ... atlasgw:/clients/scratch/logs/tdaq-04-00-01/ATLAS/
 
side & cratefile name
A-Side, TTCTGCTTC-A_RCD_PhysicsMode_sbc-tgc-tcc-eca-01.cern.ch_[UTC].out/err
C-Side, TTCTGCTTC-C_RCD_PhysicsMode_sbc-tgc-tcc-ecc-01.cern.ch_[UTC].out/err
A-Side, FETGCFE-RCD_ECA[01-04]_Physics_sbc-tgc-cci-eca-[01-04].cern.ch_[UTC].out/err
C-Side, FETGCFE-RCD_ECC[01-04]_Physics_sbc-tgc-cci-ecc-[01-04].cern.ch_[UTC].out/err
A-Side, SLTGCSL_ReadoutApplication-CSL[04-06]_sbc-tgc-csl-lvl1-[04-06].cern.ch_[UTC].out/err
C-Side, SLTGCSL_ReadoutApplication-CSL[01-03]_sbc-tgc-csl-lvl1-[01-03].cern.ch_[UTC].out/err
Deleted:
<
<
 

Analyze Calibration DATA and update parameter and OKS : 3-STEPS (EXPERT ONLY)

Analysis of Calibration data

  • preparation : login, go to working space, set environment (the computer OUTSIDE of Point1.)

Revision 322011-08-30 - satoshi

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"

TGC FE expert guide

Line: 240 to 240
 
    • feed buck timing
      • under construction
Added:
>
>

Standalone cosmic run

Use part_TGC2. Setup partition as figures show.

Cosmic_TGC_A.png Cosmic_TGC_C.png

 

TgcExpertOperationObsoletes

META FILEATTACHMENT attachment="DAQPanel_DelayScan.png" attr="" comment="" date="1271512656" name="DAQPanel_DelayScan.png" path="DAQPanel_DelayScan.png" size="226232" stream="DAQPanel_DelayScan.png" tmpFilename="/usr/tmp/CGItemp33894" user="ysuzuki" version="1"
META FILEATTACHMENT attachment="RDAQPanel_DelayScan.png" attr="" comment="" date="1271512688" name="RDAQPanel_DelayScan.png" path="RDAQPanel_DelayScan.png" size="83809" stream="RDAQPanel_DelayScan.png" tmpFilename="/usr/tmp/CGItemp33898" user="ysuzuki" version="1"
Added:
>
>
META FILEATTACHMENT attachment="Cosmic_TGC_A.png" attr="" comment="" date="1314706360" name="Cosmic_TGC_A.png" path="Cosmic_TGC_A.png" size="25549" stream="Cosmic_TGC_A.png" tmpFilename="/usr/tmp/CGItemp6963" user="satoshi" version="1"
META FILEATTACHMENT attachment="Cosmic_TGC_C.png" attr="" comment="" date="1314706377" name="Cosmic_TGC_C.png" path="Cosmic_TGC_C.png" size="20327" stream="Cosmic_TGC_C.png" tmpFilename="/usr/tmp/CGItemp7044" user="satoshi" version="1"

Revision 312011-07-17 - lellouch

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Changed:
<
<
>
>

TGC FE expert guide

 

PS Reset / DCS Reset : ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing

Revision 302011-06-03 - okumura

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 61 to 61
 
        • It is OK if you see the message shown in bottom right figure
Status of LTPi Status of LTP
Added:
>
>

Reboot all cci sbcs

  • procedure
    1. login to a machine in Point1. (The script includes SSH command inside it.) and run followings:
      souce /det/muon/TGCFE/installed/bin/TGC_env.sh
      oncall_allccisbc_reboot.sh
  • You will be asked twice and please type "Y" (capital y) to confirm to reboot the SBCs.
 

Reset Semaphore

  • procedure
Changed:
<
<
    1. login to the machine to reset, and run the following
>
>
    1. login to a machine in Point1. (The script includes SSH command inside it.) and run followings:
 
souce /det/muon/TGCFE/installed/bin/TGC_env.sh
oncall_allsbc_resetSemaphore.sh
  • In case "semaphore" is locked, you will see following messages

Revision 282010-12-02 - hayakawa

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 121 to 121
 
        • [new!!]The program will ask you to check the new parameter showing the parameter contents. Please compare it to last on-call shift summary and confirmed the difference is reasonable.
          • Hint : Did you miss-type "yes" ? You don't have to wait for preparing parameters again. try below.
          •  (this is a command to restart the process.) $ cd /det/tgc/FEtest/scripts/expert/ ; sh put_psb_DetMuonTgcfe.sh
Changed:
<
<
        • After it finishes, upload parameters to OKS. see "hange OKS xml files for the global partition" in this page.
>
>
        • After it finishes, upload parameters to OKS. see "Upload parameters (text-base) to ORACLE" in this page.
 
    • Case : Track
      • (1) Open a gui tool.
      • sh setup.sh
Line: 149 to 149
 
      • Physics_[date]_l67_[# of trial] (2 out-of 2)
      • Example: Physics_100301_normal_0, Physics_100301_l67_0
    • Finally, the result of the comparison is shown in the terminal. If there is no inconsistent parameter, please post the message to e-log.
Added:
>
>
    • After it finishes, upload parameters to OKS. see "Change OKS xml files for the global partition" in this page.
 

Change OKS xml files for the global partition

  • Do not perform the following operation if you do not understand what you are doing

Revision 262010-08-06 - satoshi

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 23 to 23
 

open TGC ROD Status panel

  • You can open TGC Rod status panel alone without TDAQ panel.
Added:
>
>
    • First, you long in to ATLAS point 1 computer via "atlasgw" from your computer.
       ssh -Y atlasgw 
    • pc-tgc-daq-ecc-01 is one of good computers to login for this purpose.
    • You source a set-up file and run a command.
 
 source  /det/muon/TGC/scripts/setupGlobal.sh 
Changed:
<
<
 TGCstatusPanel 
>
>
 TGCpanel 
    • Thne, the panel will appear.
 

Initialize LTPi after power cut (EXPERT ONLY)

  • THESE PROCESSES CAN DESTROY THE GLOBAL RUN!!!!
    PLEASE RUN THEM VERY CAREFULLY!!!!

Revision 252010-08-06 - satoshi

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 20 to 20
 
TgcTtcvi -c DcsReset 
    1. type yes if you are sure to send the signal.
Added:
>
>

open TGC ROD Status panel

  • You can open TGC Rod status panel alone without TDAQ panel.
     source  /det/muon/TGC/scripts/setupGlobal.sh 
     TGCstatusPanel 
 

Initialize LTPi after power cut (EXPERT ONLY)

  • THESE PROCESSES CAN DESTROY THE GLOBAL RUN!!!!
    PLEASE RUN THEM VERY CAREFULLY!!!!

Revision 242010-07-15 - mishino

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 68 to 68
 

Analyze Calibration DATA and update parameter and OKS : 3-STEPS (EXPERT ONLY)

Analysis of Calibration data

  • preparation : login, go to working space, set environment (the computer OUTSIDE of Point1.)
Changed:
<
<
    • ssh -X pc-tgc-calsrv-01.cern.ch
    • cd /det/tgc/Monitoring/hist ;
    • source   /det/muon/TGCFE/installed/bin/TGC_env.sh; 
>
>
    • $ ssh -X pc-tgc-calsrv-01.cern.ch;
    • $ cd /det/tgc/Monitoring/hist ;
    • $ source /det/muon/TGCFE/installed/bin/TGC_env.sh;
 
  • Then, get rod files from Point 1
    • Has the TGC shifter already copied data to shared disk?
Changed:
<
<
      • If data transfer has been completed by shifter, it is found under "/det/tgc/data/runs/"
>
>
      • If data transfer has been completed by shifter, it is found under /det/tgc/data/runs/
 
      • If it is not the case, you should copy them by yourself with following procedure.
    • Get files from Point 1 (replace "runumber")
Changed:
<
<
      • sh OncallTool_GetFilesFromPoint1.sh runnumber
        (copy data with SCP, your passswd @P1 is required)
>
>
      • $ sh OncallTool_GetFilesFromPoint1.sh runnumber; (copy data with SCP, your passswd @P1 is required)
 
  • Next, decode data
Changed:
<
<
    • do_Decoding_pararel.sh runnumber 100000
      (decode 100000 events : for Random)
    • do_Decoding_pararel.sh runnumber -1
      (decode all data : for asd and track)
>
>
    • $ do_Decoding_pararel.sh runnumber 100000 (decode 100k events : for Random)
    • $ do_Decoding_pararel.sh runnumber -1 (decode all data : for asd and track)
 
  • Next, run analysis program.
    • Case : ASD
      • (1) run the analysis code and check the result.

Revision 232010-07-15 - mishino

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 67 to 67
 

Analyze Calibration DATA and update parameter and OKS : 3-STEPS (EXPERT ONLY)

Analysis of Calibration data

Changed:
<
<
  • First, you log in to the pc-tgc-calsrv-01(the computer OUTSIDE of Point1.
    • ssh pc-tgc-calsrv-01
    • After login, move to work directory
    • cd /det/tgc/Monitoring/hist
    • Set Environment
    • source   /det/muon/TGCFE/installed/bin/TGC_env.sh 
>
>
  • preparation : login, go to working space, set environment (the computer OUTSIDE of Point1.)
    • ssh -X pc-tgc-calsrv-01.cern.ch
    • cd /det/tgc/Monitoring/hist ;
    • source   /det/muon/TGCFE/installed/bin/TGC_env.sh; 
 
  • Then, get rod files from Point 1
    • Has the TGC shifter already copied data to shared disk?
Changed:
<
<
      • He/she can do that on "FE test panel", and how-to is mentioned on shift manual.
      • (Technically, the panel just copy the rod files to /shared/data/crmuon/ so that we can get files from outside.)
    • Get files from Point 1 as (replace "runumber")
      • sh OncallTool_GetFilesFromPoint1.sh runnumber
      • It will try scp and ask you the password for Point1.
    • decode it.
      • do_Decoding_pararel.sh runnumber 100000
        (decode 100000 events : for random)
>
>
      • If data transfer has been completed by shifter, it is found under "/det/tgc/data/runs/"
      • If it is not the case, you should copy them by yourself with following procedure.
    • Get files from Point 1 (replace "runumber")
      • sh OncallTool_GetFilesFromPoint1.sh runnumber
        (copy data with SCP, your passswd @P1 is required)
  • Next, decode data
    • do_Decoding_pararel.sh runnumber 100000
      (decode 100000 events : for Random)
 
      • do_Decoding_pararel.sh runnumber -1
        (decode all data : for asd and track)
  • Next, run analysis program.
    • Case : ASD

Revision 222010-07-04 - ysuzuki

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 169 to 169
 
      • The same comments which you input above will be shown in the window.
      • Please click commit button to upload files.
    • If no error message is shown, please post message to the e-log.
Added:
>
>
    • For avoiding mis-understanding, Announce Shiftleader and Run Control Shifter, what you changed,why you changed.
      • What you changed (/atlas/oks/tdaq-02-00-03/muons/segments/TGC/FE/TGCFE-A(&C)_Segment.data.xml)
      • Why you changed (updating mask parameter)
 

Chcek eLMB Internal mode at EIFI

When there is [1] power glitch or [2] LV power-cycle, it can be that wrong eLMB modes are configured into eLMB at EIFI.

Revision 212010-06-19 - ysuzuki

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 106 to 106
 
        • scp /det/tgc/Monitoring/hist/noisylist/run${runnum}_bcidmasklist.txt atlasgw:/shared/data/crmuon/
        • (2-2) Log in to Point 1 machine.
        •  ssh atlasgw 
Added:
>
>
        •  cp    /shared/data/crmuon/run${runnum}_bcidmasklist.txt  /det/muon/TGCFE/src/tgc_hw/scripts/noisy_channels/
 
        • (2-3) run a update command. I recommend to use "screen" command before do followings.
        •  screen  
        •  cd /det/tgc/FEtest/scripts/expert/ ; sh update_psb_parameters.sh

Revision 202010-06-04 - sugimoto

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"

PS Reset / DCS Reset : ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing
Changed:
<
<
  • PS Board Reset
>
>
  • PS Board Reset
 
    1. login to SBC for TTC crate
      • A-Side: sbc-tgc-tcc-eca-01.cern.ch
      • C-Side: sbc-tgc-tcc-ecc-01.cern.ch
Line: 14 to 14
 
TgcTtcvi -c !PsReset 
    1. type yes if you are sure to send the signal.
Changed:
<
<
  • DCS Reset
>
>
  • DCS Reset
 
    1. loguin to SBC and source the setup script (same as PsReset)
    2. run the following command
      TgcTtcvi -c DcsReset 
    3. type yes if you are sure to send the signal.

Initialize LTPi after power cut (EXPERT ONLY)

Deleted:
<
<
  • Do not perform the following operation if you do not understand what you are doing
 
  • THESE PROCESSES CAN DESTROY THE GLOBAL RUN!!!!
    PLEASE RUN THEM VERY CAREFULLY!!!!
Changed:
<
<
  • LTPi does NOT distribute any signals from CTP (i.e. clock, BCR, ECR, etc.) at power-on reset state.
  • Run a script to enable these signals;
>
>
  • Experts need to run this script when the TTC crate is turned off because LTPi does NOT distribute any signals coming from CTP (i.e. clock, BCR, ECR, etc.) after power-on reset.
  • How to enable these signals?
 
    1. login to SBC for TTC crate (This module is installed on TTC-A crate)
      ssh sbc-tgc-tcc-eca-01.cern.ch 
    2. source the setup script for standalone
       source /det/muon/TGCFE/installed/bin/TGC_env.sh 
    3. run the following script
       do_LtpiCtpSlave.sh 
Changed:
<
<
  • How to confirm this script worked fine or not?
    • BC Status of LTPi
>
>
  • How to confirm this script worked fine or not?
    • BC Status of LTPi
 
      1. Login to TTC-A (sbc-tgc-tcc-eca-01.cern.ch)
      2. source the setup script (TGC_env.sh, if not yet)
      3. run the following command;
        menuRCDLtpi -a ee1000 
        • Enter Number: 3 (Bunch Clock)
        • Enter Number: 1 (BC Status)
Changed:
<
<
        • It is OK if you see the message shown in bottom left figure
    • BC Status of LTP
>
>
        • It is OK if you see the message shown in bottom left figure
    • BC Status of LTP
 
      1. Login to TTC crate (A-Side:sbc-tgc-tcc-eca-01, C-Side:sbc-tgc-tcc-ecc-01)
      2. source the setup script (TGC_env.sh, if not yet)
      3. run the following command;
         menuRCDLtp -a ff4000 
        • Enter Number:2 (Bunch Clock)
        • Enter Number:1 (BC Status)
Changed:
<
<
        • It is OK if you see the message shown in bottom right figure
>
>
        • It is OK if you see the message shown in bottom right figure
 
Status of LTPi Status of LTP
Line: 56 to 56
 
    1. login to the machine to reset, and run the following
      souce /det/muon/TGCFE/installed/bin/TGC_env.sh
      reset-semaphore.sh
Changed:
<
<
  • In case "semaphore" is locked, you will see following messages ...
    • inf 2010/04/07 18:29:29 start reset-semaphore.sh
    • err> /tmp/tgc_vme_tm_semaphore-02000000 is locked by zombie [15799]
    • inf> /tmp/tgc_vme_tm_semaphore-02000000 has been unlocked
    • inf> /tmp/tgc_vme_tm_semaphore-02000000 value=1 pid=21748
    • inf> 2010/04/07 18:29:29 reset-semaphore.sh done
>
>
  • In case "semaphore" is locked, you will see following messages
 

How to find ERROR LOG ?? (for further investigation of problems reported in MRS)

  • location of log-file ... atlasgw:/clients/scratch/logs/tdaq-02-00-03/ATLAS/
Added:
>
>
side & cratefile name
A-Side, TTCTGCTTC-A_RCD_PhysicsMode_sbc-tgc-tcc-eca-01.cern.ch_[UTC].out/err
C-Side, TTCTGCTTC-C_RCD_PhysicsMode_sbc-tgc-tcc-ecc-01.cern.ch_[UTC].out/err
A-Side, FETGCFE-RCD_ECA[01-04]_Physics_sbc-tgc-cci-eca-[01-04].cern.ch_[UTC].out/err
C-Side, FETGCFE-RCD_ECC[01-04]_Physics_sbc-tgc-cci-ecc-[01-04].cern.ch_[UTC].out/err
A-Side, SLTGCSL_ReadoutApplication-CSL[04-06]_sbc-tgc-csl-lvl1-[04-06].cern.ch_[UTC].out/err
C-Side, SLTGCSL_ReadoutApplication-CSL[01-03]_sbc-tgc-csl-lvl1-[01-03].cern.ch_[UTC].out/err
 

Analyze Calibration DATA and update parameter and OKS : 3-STEPS (EXPERT ONLY)

Line: 123 to 121
 
  • Finally, report the results.

Upload parameters (text-base) to ORACLE

Changed:
<
<
    1. generate new parameter files according to the result of the test during the daily calibration hour (see below).

    1. login to the TGC machine;
    • pc-tgc-daq-eca-01
    • pc-tgc-daq-ecc-01
    • pc-tgc-mon-rod-01

    1. source the setup script (if not yet)
    • $> /det/muon/TGCFE/installed/bin/TGC_env.sh

    1. run a wrapper script;
    • $> auto_upload.sh

    1. type yes and enter # of trial (if you don't try to upload yet, please input 0 as the number)
>
>
  • generate new parameter files according to the result of the test during the daily calibration hour (see below).
    • login to the TGC machine;
      pc-tgc-daq-ecc-01   or   pc-tgc-mon-rod-01 
    • source the setup script (if not yet)
      /det/muon/TGCFE/installed/bin/TGC_env.sh
    • move to the following directory;
      cd /det/muon/TGCFE/installed/bin/oracle/
    • run a wrapper script;
      auto_upload.sh 
    • type yes and enter # of trial (if you don't try to upload yet, please input 0 as the number)
 
    • Then, the following processes will be carried out;
Changed:
<
<
      1. start reading text file
>
>
      1. start reading text file (stored in /det/muon/TGCFE/config/Frontend/)
 
      1. uploading parameters to ORACLE
      2. compare parameters in between text file and ORACLE
    • rule of DB tag (generated automatically):
      • Physics_[date]_normal_[# of trial] (3 out-of 4)
      • Physics_[date]_l67_[# of trial] (2 out-of 2)
      • Example: Physics_100301_normal_0, Physics_100301_l67_0
Changed:
<
<
    1. Finally, the result of the comparison is shown in the terminal. If there is no inconsistent parameter, please post the message to e-log.
>
>
    • Finally, the result of the comparison is shown in the terminal. If there is no inconsistent parameter, please post the message to e-log.
 

Change OKS xml files for the global partition

  • Do not perform the following operation if you do not understand what you are doing
Changed:
<
<
    1. login to the TGC machine, which SLC5 is running (last update; 2010.3.2).
      • pc-tgc-daq-eca-01
      • pc-tgc-daq-ecc-01

    1. source the setup script (if not yet)
      • $> /det/muon/TGC/scripts/setupStandalone.sh

    1. move to the following directory and source the script;
      • $> cd /det/tgc/db/
      • $> source mycheckout.sh

    1. Then, the oks_dsata_editor will be shown in your terminal automatically.

    1. Please change the attribute which you want.
>
>
    • login to the TGC machine, which SLC5 is running (last update; 2010.6.4).
      pc-tgc-daq-ecc-01   or   pc-tgc-mon-rod-01 
    • source the setup script (if not yet)
      /det/muon/TGCFE/installed/bin/TGC_env.sh
    • move to the following directory and source the script;
      cd /det/tgc/db/
      source mycheckout.sh
    • Then, the oks_dsata_editor GUI pannel will be appeared in your terminal automatically.
    • Please change the attribute which you want.
 
      • Example: change Oracle DB tag for Frontend configuration
        1. search TGCFE_DBSetting class in the list (enter the class name in "Matching names of classes" box)
        2. double click the class and open it (new window will be shown)
Line: 175 to 162
 
          • FE_Config
          • (Please note that you should change all of them one-by-one. More easy way will be implemented soon.)
        1. check the all attributes in the list are correct or not.
Changed:
<
<
    1. Please execute "FIle --> Save All Updated" to save all changes.
>
>
    • Please execute "FIle --> Save All Updated" to save all changes.
 
      • PLEASE input some comments to be able to identify the modification.
Changed:
<
<
    1. Please execute "File --> Commit User Repository" to commit all updated xml files to CVS server.
>
>
    • Please execute "File --> Commit User Repository" to commit all updated xml files to CVS server.
 
      • The same comments which you input above will be shown in the window.
      • Please click commit button to upload files.
Changed:
<
<
    1. If no error message is shown, please post message to the e-log.
>
>
    • If no error message is shown, please post message to the e-log.
 

Chcek eLMB Internal mode at EIFI

When there is [1] power glitch or [2] LV power-cycle, it can be that wrong eLMB modes are configured into eLMB at EIFI.

Revision 192010-06-04 - sugimoto

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 8 to 8
 
    1. login to SBC for TTC crate
      • A-Side: sbc-tgc-tcc-eca-01.cern.ch
      • C-Side: sbc-tgc-tcc-ecc-01.cern.ch
Changed:
<
<
    1. source the setup script for standalone
      • $> source /det/muon/TGC/scripts/setupStandalone.sh
>
>
    1. source the setup script for TGC Frontend environment
      source /det/muon/TGCFE/installed/bin/TGC_env.sh
 
    1. run the following command
Changed:
<
<
      • $> TgcTtcvi -c PsReset
>
>
TgcTtcvi -c !PsReset 
 
    1. type yes if you are sure to send the signal.

  • DCS Reset
    1. loguin to SBC and source the setup script (same as PsReset)
    2. run the following command
Changed:
<
<
      • $> TgcTtcvi -c DcsReset
>
>
TgcTtcvi -c DcsReset 
 
    1. type yes if you are sure to send the signal.
Added:
>
>

Initialize LTPi after power cut (EXPERT ONLY)

  • Do not perform the following operation if you do not understand what you are doing
  • THESE PROCESSES CAN DESTROY THE GLOBAL RUN!!!!
    PLEASE RUN THEM VERY CAREFULLY!!!!
  • LTPi does NOT distribute any signals from CTP (i.e. clock, BCR, ECR, etc.) at power-on reset state.
  • Run a script to enable these signals;
    1. login to SBC for TTC crate (This module is installed on TTC-A crate)
      ssh sbc-tgc-tcc-eca-01.cern.ch 
    2. source the setup script for standalone
       source /det/muon/TGCFE/installed/bin/TGC_env.sh 
    3. run the following script
       do_LtpiCtpSlave.sh 
  • How to confirm this script worked fine or not?
    • BC Status of LTPi
      1. Login to TTC-A (sbc-tgc-tcc-eca-01.cern.ch)
      2. source the setup script (TGC_env.sh, if not yet)
      3. run the following command;
        menuRCDLtpi -a ee1000 
        • Enter Number: 3 (Bunch Clock)
        • Enter Number: 1 (BC Status)
        • It is OK if you see the message shown in bottom left figure
    • BC Status of LTP
      1. Login to TTC crate (A-Side:sbc-tgc-tcc-eca-01, C-Side:sbc-tgc-tcc-ecc-01)
      2. source the setup script (TGC_env.sh, if not yet)
      3. run the following command;
         menuRCDLtp -a ff4000 
        • Enter Number:2 (Bunch Clock)
        • Enter Number:1 (BC Status)
        • It is OK if you see the message shown in bottom right figure
Status of LTPi Status of LTP
 

Reset Semaphore

  • procedure
Changed:
<
<
    1. login to the machine to reset
    2. souce /det/muon/TGCFE/installed/bin/TGC_env.sh
    3. reset-semaphore.sh
>
>
    1. login to the machine to reset, and run the following
      souce /det/muon/TGCFE/installed/bin/TGC_env.sh
      reset-semaphore.sh
 
  • In case "semaphore" is locked, you will see following messages ...
    • inf 2010/04/07 18:29:29 start reset-semaphore.sh
    • err> /tmp/tgc_vme_tm_semaphore-02000000 is locked by zombie [15799]
Line: 32 to 63
 
    • inf> /tmp/tgc_vme_tm_semaphore-02000000 value=1 pid=21748
    • inf> 2010/04/07 18:29:29 reset-semaphore.sh done
Changed:
<
<

see ERROR LOG (for further investigation of problems reported in MRS)

  • location of log-file ... atlasgw:/clients/scratch/logs/tdaq-02-00-03/ATLAS/TGCFE-RCD_EC...
>
>

How to find ERROR LOG ?? (for further investigation of problems reported in MRS)

  • location of log-file ... atlasgw:/clients/scratch/logs/tdaq-02-00-03/ATLAS/
 

Analyze Calibration DATA and update parameter and OKS : 3-STEPS (EXPERT ONLY)

Analysis of Calibration data

Revision 182010-05-17 - okumura

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 70 to 70
 
      • (1) run the analysis code and check the result.
      • sh OncallTool_NoisyChannelList.sh   runnumber
      • (2) If noisy channel(s) was found, prepare configuration parameter. Following instruction will be shown with appropriate parameter so that you can just copy & paset smile
Added:
>
>
        • (2-0) check which channel is found a new noisy channel.
        • EXCEPTION It is known that we cannot kill 1 single noisy channel
          C       05      0       E       W       2       2       41 
          . In case only this channel is listed, it is not needed to update parameters.
 
        • (2-1) send noisy channel list to point 1.
        • scp /det/tgc/Monitoring/hist/noisylist/run${runnum}_bcidmasklist.txt atlasgw:/shared/data/crmuon/
        • (2-2) Log in to Point 1 machine.

Revision 162010-05-16 - satoshi

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 78 to 78
 
        •  screen  
        •  cd /det/tgc/FEtest/scripts/expert/ ; sh update_psb_parameters.sh
        • [new!!]The program will ask you to check the new parameter showing the parameter contents. Please compare it to last on-call shift summary and confirmed the difference is reasonable.
Added:
>
>
          • Hint : Did you miss-type "yes" ? You don't have to wait for preparing parameters again. try below.
          •  (this is a command to restart the process.) $ cd /det/tgc/FEtest/scripts/expert/ ; sh put_psb_DetMuonTgcfe.sh
 
        • After it finishes, upload parameters to OKS. see "hange OKS xml files for the global partition" in this page.
    • Case : Track
      • (1) Open a gui tool.

Revision 152010-05-15 - satoshi

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 77 to 77
 
        • (2-3) run a update command. I recommend to use "screen" command before do followings.
        •  screen  
        •  cd /det/tgc/FEtest/scripts/expert/ ; sh update_psb_parameters.sh
Added:
>
>
        • [new!!]The program will ask you to check the new parameter showing the parameter contents. Please compare it to last on-call shift summary and confirmed the difference is reasonable.
 
        • After it finishes, upload parameters to OKS. see "hange OKS xml files for the global partition" in this page.
    • Case : Track
      • (1) Open a gui tool.

Revision 142010-05-10 - mishino

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 21 to 20
 
      • $> TgcTtcvi -c DcsReset
    1. type yes if you are sure to send the signal.
Changed:
<
<

Trigger rate viewer : ( EXPERT ONLY )

  • Trigger rate history recorded by the FE Monitor can be easily viewed. Please follow the procedure below.
  • (1) ssh username@pc-tgc-calsrv-01
  • (2) cd /det/tgc/Monitoring/rateHistory
  • (3) sh showRateHistory.sh
    • no argument -> full time window from 19, Feb, 2010
    • if you want to specify time window, do "sh showRateHistory.sh 2010/02/19 2010/02/23", start time should be from 2010/02/19.

To configure Sector Logic FPGAs manually : ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing
>
>

Reset Semaphore

  • procedure
    1. login to the machine to reset
    2. souce /det/muon/TGCFE/installed/bin/TGC_env.sh
    3. reset-semaphore.sh
  • In case "semaphore" is locked, you will see following messages ...
    • inf 2010/04/07 18:29:29 start reset-semaphore.sh
    • err> /tmp/tgc_vme_tm_semaphore-02000000 is locked by zombie [15799]
    • inf> /tmp/tgc_vme_tm_semaphore-02000000 has been unlocked
    • inf> /tmp/tgc_vme_tm_semaphore-02000000 value=1 pid=21748
    • inf> 2010/04/07 18:29:29 reset-semaphore.sh done
 
Changed:
<
<
  • SBCs for sector logic
    • sbc-tgc-csl-lvl1-01 for C01 - C04
    • sbc-tgc-csl-lvl1-02 for C05 - C08
    • sbc-tgc-csl-lvl1-03 for C09 - C12
    • sbc-tgc-csl-lvl1-04 for A01- A04
    • sbc-tgc-csl-lvl1-05 for A05 - A08
    • sbc-tgc-csl-lvl1-06 for A09 - A12

  • login to SBC
    • change directory to /atlas-home/0/takashi/dev/RCD.dev/detectors/muons/TgcVmeTm/scripts
    • execute one of the following commands depending on the SBC's name you are working on
      • "python csl01.py >& /tmp/csl01.log &" for sbc-tgc-csl-lvl1-01
      • "python csl02.py >& /tmp/csl02.log &" for sbc-tgc-csl-lvl1-02
      • "python csl03.py >& /tmp/csl03.log &" for sbc-tgc-csl-lvl1-03
      • "python csl04.py >& /tmp/csl04.log &" for sbc-tgc-csl-lvl1-04
      • "python csl05.py >& /tmp/csl05.log &" for sbc-tgc-csl-lvl1-05
      • "python csl06.py >& /tmp/csl06.log &" for sbc-tgc-csl-lvl1-06
    • you can monitor the progress of the configuration with the command: "tail -f /tmp/csl01.log" etc.

  • remarks
    • current maximum number of try for configuration is specified as 1000 in line 13 of the csl01.py ... csl06.py, increase the number if the configuration did not finish during the specified range.
    • mapping between bitfile and FPGAs are specified in the sbc-tgc-csl-lvl1-01.py ... sbc-tgc-csl-lvl1-06.py, edit the file when you need to configure different bitfile set
    • contact Takashi Matsushita for any problem: 16-5677
>
>

see ERROR LOG (for further investigation of problems reported in MRS)

  • location of log-file ... atlasgw:/clients/scratch/logs/tdaq-02-00-03/ATLAS/TGCFE-RCD_EC...
 
Changed:
<
<

Analysis of Calibration data.( EXPERT ONLY )

>
>

Analyze Calibration DATA and update parameter and OKS : 3-STEPS (EXPERT ONLY)

Analysis of Calibration data

 
  • First, you log in to the pc-tgc-calsrv-01(the computer OUTSIDE of Point1.
    • ssh pc-tgc-calsrv-01
    • After login, move to work directory
Line: 108 to 85
 
      • (3)histogram will be produces in "hist" directory. Check it.
  • Finally, report the results.
Changed:
<
<

Upload parameters (text-base) to ORACLE : ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing
>
>

Upload parameters (text-base) to ORACLE

 
    1. generate new parameter files according to the result of the test during the daily calibration hour (see below).

    1. login to the TGC machine;
Line: 136 to 111
 
    1. Finally, the result of the comparison is shown in the terminal. If there is no inconsistent parameter, please post the message to e-log.
Changed:
<
<

Change OKS xml files for the global partition: ( EXPERT ONLY )

>
>

Change OKS xml files for the global partition

 
  • Do not perform the following operation if you do not understand what you are doing

    1. login to the TGC machine, which SLC5 is running (last update; 2010.3.2).
Line: 222 to 197
 
    • feed buck timing
      • under construction
Changed:
<
<
-- Main.mishinoCERNCH - 2009-11-30
>
>

TgcExpertOperationObsoletes

 
META FILEATTACHMENT attachment="DAQPanel_DelayScan.png" attr="" comment="" date="1271512656" name="DAQPanel_DelayScan.png" path="DAQPanel_DelayScan.png" size="226232" stream="DAQPanel_DelayScan.png" tmpFilename="/usr/tmp/CGItemp33894" user="ysuzuki" version="1"
META FILEATTACHMENT attachment="RDAQPanel_DelayScan.png" attr="" comment="" date="1271512688" name="RDAQPanel_DelayScan.png" path="RDAQPanel_DelayScan.png" size="83809" stream="RDAQPanel_DelayScan.png" tmpFilename="/usr/tmp/CGItemp33898" user="ysuzuki" version="1"

Revision 132010-05-09 - satoshi

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 61 to 61
 

Analysis of Calibration data.( EXPERT ONLY )

  • First, you log in to the pc-tgc-calsrv-01(the computer OUTSIDE of Point1.
Added:
>
>
    • ssh pc-tgc-calsrv-01
 
    • After login, move to work directory
Changed:
<
<
    • $ cd /det/tgc/Monitoring/hist
>
>
    • cd /det/tgc/Monitoring/hist
 
    • Set Environment
Changed:
<
<
    • $ source /det/muon/TGCFE/installed/bin/TGC_env.sh
>
>
    • source   /det/muon/TGCFE/installed/bin/TGC_env.sh 
 
  • Then, get rod files from Point 1
    • Has the TGC shifter already copied data to shared disk?
      • He/she can do that on "FE test panel", and how-to is mentioned on shift manual.
      • (Technically, the panel just copy the rod files to /shared/data/crmuon/ so that we can get files from outside.)
    • Get files from Point 1 as (replace "runumber")
Changed:
<
<
>
>
      • sh OncallTool_GetFilesFromPoint1.sh runnumber
 
      • It will try scp and ask you the password for Point1.
    • decode it.
Changed:
<
<
      • $ do_Decoding_pararel.sh runnumber 100000 (decode 100000 events : for random)
      • $ do_Decoding_pararel.sh runnumber -1 (decode all data : for asd and track)
>
>
      • do_Decoding_pararel.sh runnumber 100000
        (decode 100000 events : for random)
      • do_Decoding_pararel.sh runnumber -1
        (decode all data : for asd and track)
 
  • Next, run analysis program.
    • Case : ASD
Changed:
<
<
      • $ sh OncallTool_MissingChannelCheck.sh runnumber
      • It will show the summary table.
>
>
      • (1) run the analysis code and check the result.
      • sh OncallTool_MissingChannelCheck.sh runnumber
 
      • Check the number and comper them to the reference in parenthesis "()"
Changed:
<
<
        • If it looks strange, check histogram with
>
>
      • (2) If it looks strange, check histogram with
 
        • sh setup.sh (will open familiar GUI tool)
Changed:
<
<
      • Finally send it to USA 15 in Point1. Follow the instruction shown.
        • transfer the missing channels list to computer in the Point1 as below.
        • $ scp /det/tgc/Monitoring/hist/missinglist/run${runnum}_missing.txt atlasgw:/shared/data/crmuon/
        • after that, login to atlasgw, and do this.
        • $ mv /shared/data/crmuon/run${runnum}_missing.txt /det/tgc/Monitoring/hist/missinglist
>
>
      • (3)Finally send it to USA 15 in Point1. Following instruction will be shown with appropriate parameter so that you can just copy & paset smile
        • (3-1)transfer the missing channels list to computer in the Point1 as below.
        • scp /det/tgc/Monitoring/hist/missinglist/run${runnum}_missing.txt  atlasgw:/shared/data/crmuon/
        • (3-2)after that, login to atlasgw, and do this.
        • ssh atlasgw
        • mv /shared/data/crmuon/run${runnum}_missing.txt  /det/tgc/Monitoring/hist/missinglist
 
    • Case : Random
Changed:
<
<
      • $ sh OncallTool_NoisyChannelList.sh runnumber
      • The result (and instruction to update parameter) will be show.
      • If noisy channel(s) was found, prepare configuration parameter as below.
        • send noisy channel list to point 1.
        • $ scp /det/tgc/Monitoring/hist/noisylist/run${runnum}_bcidmasklist.txt atlasgw:/shared/data/crmuon/
        • Log in to Point 1 machine.
        • I recommend to use "screen" command before do followings.
        • $ screen
        • $ cd /det/tgc/FEtest/scripts/expert/ ; sh update_psb_parameters.sh
>
>
      • (1) run the analysis code and check the result.
      • sh OncallTool_NoisyChannelList.sh   runnumber
      • (2) If noisy channel(s) was found, prepare configuration parameter. Following instruction will be shown with appropriate parameter so that you can just copy & paset smile
        • (2-1) send noisy channel list to point 1.
        • scp /det/tgc/Monitoring/hist/noisylist/run${runnum}_bcidmasklist.txt atlasgw:/shared/data/crmuon/
        • (2-2) Log in to Point 1 machine.
        •  ssh atlasgw 
        • (2-3) run a update command. I recommend to use "screen" command before do followings.
        •  screen  
        •  cd /det/tgc/FEtest/scripts/expert/ ; sh update_psb_parameters.sh
 
        • After it finishes, upload parameters to OKS. see "hange OKS xml files for the global partition" in this page.
    • Case : Track
Changed:
<
<
      • $ sh setup.sh
      • do "Trigger/Readout cor" with "all BW" option.
      • histogram will be produces in "hist" directory. Check it.
>
>
      • (1) Open a gui tool.
      • sh setup.sh
      • (2)do "Trigger/Readout cor" with "all BW" option.
      • (3)histogram will be produces in "hist" directory. Check it.
 
  • Finally, report the results.

Upload parameters (text-base) to ORACLE : ( EXPERT ONLY )

Revision 122010-05-07 - mishino

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 59 to 59
  edit the file when you need to configure different bitfile set
    • contact Takashi Matsushita for any problem: 16-5677
Deleted:
<
<

Upload parameters (text-base) to ORACLE : ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing

    1. generate new parameter files according to the result of the test during the daily calibration hour (see below).

    1. login to the TGC machine;
    • pc-tgc-daq-eca-01
    • pc-tgc-daq-ecc-01
    • pc-tgc-mon-rod-01

    1. source the setup script (if not yet)
    • $> /det/muon/TGCFE/installed/bin/TGC_env.sh

    1. run a wrapper script;
    • $> auto_upload.sh (should be included in the PATH)

    1. type yes and enter # of trial (if you don't try to upload yet, please input 0 as the number)
    • Then, the following processes will be carried out;
      1. start reading text file
      2. uploading parameters to ORACLE
      3. compare parameters in between text file and ORACLE
    • rule of DB tag (generated automatically):
      • Physics_[date]_normal_[# of trial] (3 out-of 4)
      • Physics_[date]_l67_[# of trial] (2 out-of 2)
      • Example: Physics_100301_normal_0, Physics_100301_l67_0

    1. Finally, the result of the comparison is shown in the terminal. If there is no inconsistent parameter, please post the message to e-log.
 

Analysis of Calibration data.( EXPERT ONLY )

  • First, you log in to the pc-tgc-calsrv-01(the computer OUTSIDE of Point1.
    • After login, move to work directory
Line: 132 to 104
 
      • histogram will be produces in "hist" directory. Check it.
  • Finally, report the results.
Added:
>
>

Upload parameters (text-base) to ORACLE : ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing

    1. generate new parameter files according to the result of the test during the daily calibration hour (see below).

    1. login to the TGC machine;
    • pc-tgc-daq-eca-01
    • pc-tgc-daq-ecc-01
    • pc-tgc-mon-rod-01

    1. source the setup script (if not yet)
    • $> /det/muon/TGCFE/installed/bin/TGC_env.sh

    1. run a wrapper script;
    • $> auto_upload.sh (should be included in the PATH)

    1. type yes and enter # of trial (if you don't try to upload yet, please input 0 as the number)
    • Then, the following processes will be carried out;
      1. start reading text file
      2. uploading parameters to ORACLE
      3. compare parameters in between text file and ORACLE
    • rule of DB tag (generated automatically):
      • Physics_[date]_normal_[# of trial] (3 out-of 4)
      • Physics_[date]_l67_[# of trial] (2 out-of 2)
      • Example: Physics_100301_normal_0, Physics_100301_l67_0

    1. Finally, the result of the comparison is shown in the terminal. If there is no inconsistent parameter, please post the message to e-log.
 

Change OKS xml files for the global partition: ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing

Revision 102010-04-26 - satoshi

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 87 to 87
 
    1. Finally, the result of the comparison is shown in the terminal. If there is no inconsistent parameter, please post the message to e-log.
Added:
>
>

Analysis of Calibration data.( EXPERT ONLY )

  • First, you log in to the pc-tgc-calsrv-01(the computer OUTSIDE of Point1.
    • After login, move to work directory
    • $ cd /det/tgc/Monitoring/hist
    • Set Environment
    • $ source /det/muon/TGCFE/installed/bin/TGC_env.sh
  • Then, get rod files from Point 1
    • Has the TGC shifter already copied data to shared disk?
      • He/she can do that on "FE test panel", and how-to is mentioned on shift manual.
      • (Technically, the panel just copy the rod files to /shared/data/crmuon/ so that we can get files from outside.)
    • Get files from Point 1 as (replace "runumber")
      • $ sh OncallTool_GetFilesFromPoint1.sh runnumber
      • It will try scp and ask you the password for Point1.
    • decode it.
      • $ do_Decoding_pararel.sh runnumber 100000 (decode 100000 events : for random)
      • $ do_Decoding_pararel.sh runnumber -1 (decode all data : for asd and track)
  • Next, run analysis program.
    • Case : ASD
      • $ sh OncallTool_MissingChannelCheck.sh runnumber
      • It will show the summary table.
      • Check the number and comper them to the reference in parenthesis "()"
        • If it looks strange, check histogram with
        • sh setup.sh (will open familiar GUI tool)
      • Finally send it to USA 15 in Point1. Follow the instruction shown.
        • transfer the missing channels list to computer in the Point1 as below.
        • $ scp /det/tgc/Monitoring/hist/missinglist/run${runnum}_missing.txt atlasgw:/shared/data/crmuon/
        • after that, login to atlasgw, and do this.
        • $ mv /shared/data/crmuon/run${runnum}_missing.txt /det/tgc/Monitoring/hist/missinglist
    • Case : Random
      • $ sh OncallTool_NoisyChannelList.sh runnumber
      • The result (and instruction to update parameter) will be show.
      • If noisy channel(s) was found, prepare configuration parameter as below.
        • send noisy channel list to point 1.
        • $ scp /det/tgc/Monitoring/hist/noisylist/run${runnum}_bcidmasklist.txt atlasgw:/shared/data/crmuon/
        • Log in to Point 1 machine.
        • I recommend to use "screen" command before do followings.
        • $ screen
        • $ cd /det/tgc/FEtest/scripts/expert/ ; sh update_psb_parameters.sh
        • After it finishes, upload parameters to OKS. see "hange OKS xml files for the global partition" in this page.
    • Case : Track
      • $ sh setup.sh
      • do "Trigger/Readout cor" with "all BW" option.
      • histogram will be produces in "hist" directory. Check it.
  • Finally, report the results.
 

Change OKS xml files for the global partition: ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing

Revision 92010-04-17 - ysuzuki

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 140 to 140
 
  1. launching DAQ_Panel
    • TDAQ ->DAQPanel
Added:
>
>
 
      • Setup Script: /det/muon/TGCFE/installed/bin/setup_partTGC_DelayScan.sh
      • Part Name: partTGC_DelayScan
      • Database File: /det/muon/standalone/databases/tdaq-02-00-03/muons/partitions/part_TGC_DelayScan.data.xml
Line: 155 to 156
 
  1. executing the script for DelayScan
    • $> cd /det/muon/TGCFE/TGCFeOperation/DelayScan/script
    • $> sh DelayScan.sh
Changed:
<
<
      • Delayscan will start and the DAQ panel will transit automatically. You need to wait about 30 minutes for finishing the data taking.
>
>
      • Delayscan will start. It will take about 30 minutes until finish.
 
  1. transporting raw data to out of P1 machine
Changed:
<
<
    • Raw data of DelayScan are put in "/det/muon/TGCFE/TGCFeOperation/DelayScan/script/rootfile/". you need to move this files to TGC local machine (pc-tgc-calsrv-01).
>
>
    • Raw data of DelayScan are put in "/det/muon/TGCFE/TGCFeOperation/DelayScan/script/rootfile/". you need to copy this files to TGC local machine (pc-tgc-calsrv-01). Please use the GUI for TgcCalibration.("https://pc-atlas-www.cern.ch/twiki/pub/Main/HowToRunTgcCalibration").
 
Changed:
<
<
  1. data analysis (under construction)
  • Decoding data and making timing histograms are held in pc-tgc-calsrv-01
>
>
  1. data analysis
  • Decoding data and making timing histograms. Doing at pc-tgc-calsrv-01. *setup *sourse /det/muon/TGCFE/installed/bin/TGC_env.sh
 
    • data decoding
      • do_DecodingDelayscan.sh [runnum]
    • data analysis
Line: 171 to 174
 
      • under construction

-- Main.mishinoCERNCH - 2009-11-30

Added:
>
>
META FILEATTACHMENT attachment="DAQPanel_DelayScan.png" attr="" comment="" date="1271512656" name="DAQPanel_DelayScan.png" path="DAQPanel_DelayScan.png" size="226232" stream="DAQPanel_DelayScan.png" tmpFilename="/usr/tmp/CGItemp33894" user="ysuzuki" version="1"
META FILEATTACHMENT attachment="RDAQPanel_DelayScan.png" attr="" comment="" date="1271512688" name="RDAQPanel_DelayScan.png" path="RDAQPanel_DelayScan.png" size="83809" stream="RDAQPanel_DelayScan.png" tmpFilename="/usr/tmp/CGItemp33898" user="ysuzuki" version="1"

Revision 82010-04-09 - ysuzuki

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 138 to 138
 

Delay Scan

Changed:
<
<
  1. launch DAQ_Panel
>
>
  1. launching DAQ_Panel
 
    • TDAQ ->DAQPanel
      • Setup Script: /det/muon/TGCFE/installed/bin/setup_partTGC_DelayScan.sh
      • Part Name: partTGC_DelayScan
Line: 152 to 152
 
      • TriP Opt: * Click "Read Info" button
Changed:
<
<
  1. execute the script of delay scan
>
>
  1. executing the script for DelayScan
 
    • $> cd /det/muon/TGCFE/TGCFeOperation/DelayScan/script
    • $> sh DelayScan.sh
      • Delayscan will start and the DAQ panel will transit automatically. You need to wait about 30 minutes for finishing the data taking.
Changed:
<
<
  1. move data to out of P1 machine
    • the data of delay scan are put in /det/muon/TGCFE/TGCFeOperation/DelayScan/script/rootfile. you need to move this file to TGC local machine (pc-tgc-calsrv-01).
>
>
  1. transporting raw data to out of P1 machine
    • Raw data of DelayScan are put in "/det/muon/TGCFE/TGCFeOperation/DelayScan/script/rootfile/". you need to move this files to TGC local machine (pc-tgc-calsrv-01).
 
Changed:
<
<
  1. analysis data and feedback (under construction)
  • the data decoding and making timing plots are held in pc-tgc-calsrv-01
>
>
  1. data analysis (under construction)
  • Decoding data and making timing histograms are held in pc-tgc-calsrv-01
 
    • data decoding
      • do_DecodingDelayscan.sh [runnum]
    • data analysis

Revision 72010-04-09 - ysuzuki

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 161 to 161
 
    • the data of delay scan are put in /det/muon/TGCFE/TGCFeOperation/DelayScan/script/rootfile. you need to move this file to TGC local machine (pc-tgc-calsrv-01).

  1. analysis data and feedback (under construction)
Changed:
<
<
the data decoding and making timing plots are held in pc-tgc-calsrv
>
>
  • the data decoding and making timing plots are held in pc-tgc-calsrv-01
 
    • data decoding
Changed:
<
<
      • the way for decoding is not fixed and considered.(the data name of DelayScan is a not same as usual (delay1_152687.RodA01_00.run, delay2_152687.RodA01_00.run.... ) )
>
>
      • do_DecodingDelayscan.sh [runnum]
 
    • data analysis
      • $> cd /det/muon/TGCFE/TGCFeOperation/DelayScan/script
Changed:
<
<
      • $> emacs input.list.allsector (change the file name properly, the easy way for edit is considered)
      • $> sh cable_ASDall.sh
>
>
      • $> sh cable_ASDall.sh [runnum]
 
    • feed buck timing
Changed:
<
<
>
>
*under construction
  -- Main.mishinoCERNCH - 2009-11-30

Revision 62010-04-09 - ysuzuki

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 136 to 136
 
  1. If there is inconsistency found, please fixed them by left click on the name of eLMB. (the value in leftmost column)
Added:
>
>

Delay Scan

  1. launch DAQ_Panel
    • TDAQ ->DAQPanel
      • Setup Script: /det/muon/TGCFE/installed/bin/setup_partTGC_DelayScan.sh
      • Part Name: partTGC_DelayScan
      • Database File: /det/muon/standalone/databases/tdaq-02-00-03/muons/partitions/part_TGC_DelayScan.data.xml
      • Setup Opt: -newgui
      • Oks Opt:
      • MRS Filter: TGC
      • OHP opt:
      • BUSY Opt:
      • OMD Opt :
      • TriP Opt: * Click "Read Info" button

  1. execute the script of delay scan
    • $> cd /det/muon/TGCFE/TGCFeOperation/DelayScan/script
    • $> sh DelayScan.sh
      • Delayscan will start and the DAQ panel will transit automatically. You need to wait about 30 minutes for finishing the data taking.

  1. move data to out of P1 machine
    • the data of delay scan are put in /det/muon/TGCFE/TGCFeOperation/DelayScan/script/rootfile. you need to move this file to TGC local machine (pc-tgc-calsrv-01).

  1. analysis data and feedback (under construction) the data decoding and making timing plots are held in pc-tgc-calsrv
    • data decoding
      • the way for decoding is not fixed and considered.(the data name of DelayScan is a not same as usual (delay1_152687.RodA01_00.run, delay2_152687.RodA01_00.run.... ) )
    • data analysis
      • $> cd /det/muon/TGCFE/TGCFeOperation/DelayScan/script
      • $> emacs input.list.allsector (change the file name properly, the easy way for edit is considered)
      • $> sh cable_ASDall.sh
    • feed buck timing

 -- Main.mishinoCERNCH - 2009-11-30

Revision 52010-04-08 - okumura

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 124 to 124
 
  1. If no error message is shown, please post message to the e-log.
Added:
>
>

Chcek eLMB Internal mode at EIFI

When there is [1] power glitch or [2] LV power-cycle, it can be that wrong eLMB modes are configured into eLMB at EIFI. In such a case, please check internal modes of eLMB, following the instruction.

  1. navigate down the FSM tree:
    • TGC -> SIDE -> DCS -> Driver -> DCS EIFI -> ELMB EIFI
    • Note that the FSM node itself is disabled. This is done on purpose and has nothing with this action.

  1. compare values between "Image" and "Current".

  1. If there is inconsistency found, please fixed them by left click on the name of eLMB. (the value in leftmost column)
 -- Main.mishinoCERNCH - 2009-11-30 \ No newline at end of file

Revision 42010-03-02 - sugimoto

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 104 to 104
 
  1. Then, the oks_dsata_editor will be shown in your terminal automatically.

  1. Please change the attribute which you want.
Added:
>
>
    • Example: change Oracle DB tag for Frontend configuration
      1. search TGCFE_DBSetting class in the list (enter the class name in "Matching names of classes" box)
      2. double click the class and open it (new window will be shown)
      3. sort the list by FE_Trigger (or FE_Mask or FE_Config), and then you can find some objects with "Physics_xxxx_yyyy_zzzz".
      4. double click these objects, and right click the following attribute to change the DB tag;
        • FE_Trigger
        • FE_Mask
        • FE_Config
          • (Please note that you should change all of them one-by-one. More easy way will be implemented soon.)
      5. check the all attributes in the list are correct or not.
 
  1. Please execute "FIle --> Save All Updated" to save all changes.
    • PLEASE input some comments to be able to identify the modification.

Revision 32010-03-02 - sugimoto

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 59 to 59
  edit the file when you need to configure different bitfile set
    • contact Takashi Matsushita for any problem: 16-5677
Added:
>
>

Upload parameters (text-base) to ORACLE : ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing

  1. generate new parameter files according to the result of the test during the daily calibration hour (see below).

  1. login to the TGC machine;
    • pc-tgc-daq-eca-01
    • pc-tgc-daq-ecc-01
    • pc-tgc-mon-rod-01

  1. source the setup script (if not yet)
    • $> /det/muon/TGCFE/installed/bin/TGC_env.sh

  1. run a wrapper script;
    • $> auto_upload.sh (should be included in the PATH)

  1. type yes and enter # of trial (if you don't try to upload yet, please input 0 as the number)
    • Then, the following processes will be carried out;
      1. start reading text file
      2. uploading parameters to ORACLE
      3. compare parameters in between text file and ORACLE
    • rule of DB tag (generated automatically):
      • Physics_[date]_normal_[# of trial] (3 out-of 4)
      • Physics_[date]_l67_[# of trial] (2 out-of 2)
      • Example: Physics_100301_normal_0, Physics_100301_l67_0

  1. Finally, the result of the comparison is shown in the terminal. If there is no inconsistent parameter, please post the message to e-log.

Change OKS xml files for the global partition: ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing

  1. login to the TGC machine, which SLC5 is running (last update; 2010.3.2).
    • pc-tgc-daq-eca-01
    • pc-tgc-daq-ecc-01

  1. source the setup script (if not yet)
    • $> /det/muon/TGC/scripts/setupStandalone.sh

  1. move to the following directory and source the script;
    • $> cd /det/tgc/db/
    • $> source mysetup.sh

  1. Then, the oks_dsata_editor will be shown in your terminal automatically.

  1. Please change the attribute which you want.

  1. Please execute "FIle --> Save All Updated" to save all changes.
    • PLEASE input some comments to be able to identify the modification.
 
Added:
>
>
  1. Please execute "File --> Commit User Repository" to commit all updated xml files to CVS server.
    • The same comments which you input above will be shown in the window.
    • Please click commit button to upload files.
 
Added:
>
>
  1. If no error message is shown, please post message to the e-log.
  -- Main.mishinoCERNCH - 2009-11-30

Revision 22010-02-26 - ytakahas

Line: 1 to 1
 
META TOPICPARENT name="TgcOperationManual"
Line: 21 to 21
 
      • $> TgcTtcvi -c DcsReset
    1. type yes if you are sure to send the signal.
Added:
>
>

Trigger rate viewer : ( EXPERT ONLY )

  • Trigger rate history recorded by the FE Monitor can be easily viewed. Please follow the procedure below.
  • (1) ssh username@pc-tgc-calsrv-01
  • (2) cd /det/tgc/Monitoring/rateHistory
  • (3) sh showRateHistory.sh
    • no argument -> full time window from 19, Feb, 2010
    • if you want to specify time window, do "sh showRateHistory.sh 2010/02/19 2010/02/23", start time should be from 2010/02/19.
 

To configure Sector Logic FPGAs manually : ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing

Revision 12009-11-30 - mishino_40CERN_2eCH

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="TgcOperationManual"

PS Reset / DCS Reset : ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing

  • PS Board Reset
    1. login to SBC for TTC crate
      • A-Side: sbc-tgc-tcc-eca-01.cern.ch
      • C-Side: sbc-tgc-tcc-ecc-01.cern.ch
    2. source the setup script for standalone
      • $> source /det/muon/TGC/scripts/setupStandalone.sh
    3. run the following command
      • $> TgcTtcvi -c PsReset
    4. type yes if you are sure to send the signal.

  • DCS Reset
    1. loguin to SBC and source the setup script (same as PsReset)
    2. run the following command
      • $> TgcTtcvi -c DcsReset
    3. type yes if you are sure to send the signal.

To configure Sector Logic FPGAs manually : ( EXPERT ONLY )

  • Do not perform the following operation if you do not understand what you are doing

  • SBCs for sector logic
    • sbc-tgc-csl-lvl1-01 for C01 - C04
    • sbc-tgc-csl-lvl1-02 for C05 - C08
    • sbc-tgc-csl-lvl1-03 for C09 - C12
    • sbc-tgc-csl-lvl1-04 for A01- A04
    • sbc-tgc-csl-lvl1-05 for A05 - A08
    • sbc-tgc-csl-lvl1-06 for A09 - A12

  • login to SBC
    • change directory to /atlas-home/0/takashi/dev/RCD.dev/detectors/muons/TgcVmeTm/scripts
    • execute one of the following commands depending on the SBC's name you are working on
      • "python csl01.py >& /tmp/csl01.log &" for sbc-tgc-csl-lvl1-01
      • "python csl02.py >& /tmp/csl02.log &" for sbc-tgc-csl-lvl1-02
      • "python csl03.py >& /tmp/csl03.log &" for sbc-tgc-csl-lvl1-03
      • "python csl04.py >& /tmp/csl04.log &" for sbc-tgc-csl-lvl1-04
      • "python csl05.py >& /tmp/csl05.log &" for sbc-tgc-csl-lvl1-05
      • "python csl06.py >& /tmp/csl06.log &" for sbc-tgc-csl-lvl1-06
    • you can monitor the progress of the configuration with the command: "tail -f /tmp/csl01.log" etc.

  • remarks
    • current maximum number of try for configuration is specified as 1000 in line 13 of the csl01.py ... csl06.py, increase the number if the configuration did not finish during the specified range.
    • mapping between bitfile and FPGAs are specified in the sbc-tgc-csl-lvl1-01.py ... sbc-tgc-csl-lvl1-06.py, edit the file when you need to configure different bitfile set
    • contact Takashi Matsushita for any problem: 16-5677

-- Main.mishinoCERNCH - 2009-11-30

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding ATLAS?Please contact the page author (see Topic revision above) or the Run Coordinator of the specific system.
Contact SysAdmins support only for technical issues