Difference: TgcExpertOperation (33 vs. 34)

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

 
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