Difference: AtlasFPLinksLBCFFAQ (24 vs. 25)

Revision 252010-03-10 - KurtBrendlinger

Line: 1 to 1
 
META TOPICPARENT name="AnAst"
<!-- Header + table of content !-->

LBCF Shift_FAQ

Line: 6 to 6
 
Added:
>
>

Take note!

This is an old version of the LBCF FAQ page. The new version lives on the Point 1 network: https://atlasop.cern.ch/atlas-point1/twiki/bin/view/Main/BeamConditionsFAQ

 

Silly shifter questions & regulations

Before shifts: what to do ?

Changed:
<
<
Before the shifts start:
  1. check your access rights to ATL_CR (Atlas Control Room)
  2. look througt the most recent LBCF, LUCID, ZDC, BCM instructrions:
    http://pcatdwww.cern.ch/twiki/bin/view/Main/BeamConditionsOperationManualShifter
    http://pcatdwww.cern.ch/twiki/bin/view/Main/LUCIDOperationManualShifter
    https://twiki.cern.ch/twiki/bin/view/Atlas/ZDCShifter
>
>
Before the shifts start:
  1. check your access rights to ATL_CR (Atlas Control Room)
  2. look through the most recent LBCF, LUCID, ZDC, BCM instructions:
  If need to contact the LBCF shifts coordinator in a harry, look for the phone here.

Atlas Control Room (ACR): How to find it?

Changed:
<
<
  1. Building Location
  2. Web cams
>
>
  1. Building Location
  2. Web cams
 

IMPORTANT: try to speak in a low voice !

Please try to speak in a low voice with your desk(s)-colleagues so long you are in the control room !
Line: 41 to 39
 

Computing questions & problems

Computer on shift: pc-atlas-cr-03

Changed:
<
<

pc-atlas-cr-03.cern.ch; (IP: 10.144.36.252)

>
>
pc-atlas-cr-03.cern.ch; (IP: 10.144.36.252)
 This computer has many restrictions to use the web and not allows to arrange the bookmarks. frown

Proxy configuration for the firefox

Changed:
<
<

In Mozilla-firefox window open "Edit" -->

"Preferences".
In the "Firefox Preferences" pop-up window go to the "Network" folder and press "Settings..." button.
In poped-up "Connection settings" window select "Automatic proxy configuration URL"
and fill there: http://atlasgw-exp.cern.ch/proxy.pac
>
>
In Mozilla-firefox window open "Edit" -->
"Preferences".

In the "Firefox Preferences" pop-up window go to the "Network" folder and press "Settings..." button.

In poped-up "Connection settings" window select "Automatic proxy configuration URL" and fill there: http://atlasgw-exp.cern.ch/proxy.pac

 
Line: 68 to 65
  You could have a look in Atlas Poit1 FAQ page, but better just follow this simple and clear examples:
Changed:
<
<

From point-1 computer to lxplus.cern.ch:
[lxplus]$ scp -p user_name@atlasgw:/atlas-home/1/user_name/file_to_copy
From lxplus.cern.ch to point-1 computer:
[pc-atlas-cr-03]$ scp -p file_to_copy user_name@atlasgw:/atlas-home/1/user_name/.
The atlasgw is a cluster of gateway computers. (You can check with: ping atlasgw.cern.ch)

>
>
  • From point-1 computer to lxplus.cern.ch:
  • From lxplus.cern.ch to point-1 computer:
    • [pc-atlas-cr-03]$ scp -p file_to_copy user_name@atlasgw:/atlas-home/1/user_name/.
    • The atlasgw is a cluster of gateway computers. (You can check with: ping atlasgw.cern.ch)
 

Control Plots: at the beginning of your shift!

Changed:
<
<
Starting the shift please make once the snapshots with the following plots of 8 hours history and upload these snapshots into the Logbook.

>
>
Starting the shift please make once the snapshots with the following plots of 8 hours history and upload these snapshots into the Logbook.
 

ATLAS - control plots

1) DCS: ATLAS Backgrounds
fig1

Changed:
<
<

>
>
 2) DCS: ATLAS Hit rates
fig2
Deleted:
<
<

 
3) OHP:  Histograms --> Luminosity -->
"LumiAlgoHit" --> PMT_Counts_Hit
fig3
Changed:
<
<

>
>
 
4) DCS:  ATLAS --> LHC -->
Instantaneous Luminosity -->
fig4
Line: 104 to 92
  5) OP Vistars: LHC performance
fig5
Changed:
<
<

>
>
 
6) DCS: ATLAS -->
LHC --> LHC intensities & ATLAS BPTX intensities
fig6
Deleted:
<
<

 

Rate of L1 and L2 - control plots

7) DAQ Panel -->

Trigger Presenter --> Global Plots
fig7
Deleted:
<
<

 
8) DAQ Panel --> Monitor Partition -->
Load Panel --> "IguiPanels.DFPanel.DFPanel"
This plot is not archived, but points starts to appear when you open the page and select L1 and L2
fig8
Deleted:
<
<

 

Beam Position Monitors - control plots : angle and position

Line: 128 to 111
 
To zoom the plots and adjust the scales, click on "Other"  -->
"Zoomed Window" fig9 fig10
Deleted:
<
<

 

Early shift-beginner questions

DAQ Panel: How to load on the screen?

Changed:
<
<
Left-bottom corner on the main LBCF desktop:


>
>
Left-bottom corner on the main LBCF desktop:
  LBC FWD General
Line: 143 to 125
  Monitoring Tier0 Sys.Admin
Deleted:
<
<


 
Changed:
<
<
Click on:  
>
>
Click on:
  TDAQ   ⇒   "DAQPanel"
Deleted:
<
<


 

RUN Number & Status: How to load on the screen?

Switch to   "DAQPanel"
Line: 205 to 183
  General   and click on the   "ATLAS Operation".
Deleted:
<
<

  Under "AtlasOperation" twiki page find "Luminosity and Beam Conditions"   →   "Manual: shifter"
Line: 233 to 210
 Look in :
http://pcatdwww.cern.ch/atlas-point1/operRef.php?subs=magnets/
and click on "Magnet system overview" there.
Deleted:
<
<

 To find out the current magnets status: open web page https://pc-atlas-www.cern.ch/operation.php and click on Magnets in the Infrastructure column or walk to the DCS desk and ask the DCS shift person there.
Line: 372 to 345
 Be ready to report the LBCF desk PC name: pc-atlas-cr-03 which you find also typed on the keyboard.
Deleted:
<
<

LUCID pedestals & calibration

Some suggestions for existing instructions from Carla Sbarra

Pedestal and Calibration runs
To be done daily, during inter-fill time (if any)

Actions order:

  1. preparation for standalone pedestals&calibration;
  2. pedestals run;
  3. calibration run (IMPORTANT: first pedestals run, then calibration);
Time needed: ~45-60 minutes ! (~ 15-20 min. for pedestals + ~30-40 min for calibration)


Before taking Pedestals & Calibration run:

  1. There is no need to check Lucid HV settings being on shift.
    The HV settings which must be appropriate to the current B-field configuration are set AUTOMATICALLY under the experts care.

  2. make sure LUCID is disabled from the ATLAS partition
    If RUN is stopped, all subsystems must be marked in grey color on the DAQ monitor. If you are not sure that LUCID is disabled then ask the DAQ shifters.

  3. Setup the DAQPanel as follows:

    • Setup script :   /det/lucid/tdaq-02-00-03/setup_calib.sh
    • Partition Name :   lucid_calib
    • 'DataBase' file :   /det/lucid/tdaq-02-00-03/oks/tdaq-02-00-03/lucid/partititons/lucid_calib.data.xml
    • OHP configuration file :   -c /det/lucid/ohp_calib.conf.xml

  4. Click on Read Info button.
    The tabs on the right side of the DAQPanel will be activated and colored.

  5. Wait a bit these tabs are activated.

  6. Click on tab StartPartition

  7. Wait for the pop up "RunControl GUI" window to be displayed. (This should take around 10-20 seconds)

Take the pedestals run:

  1. In the pop up "RunControl GUI" window look for the Run Information & Settings panel (left, middle)

  2. Click there on the Settings tab at the bottom of the Run Information & Settings panel
    to set parameters for the pedestals run:

    • Set "MaxEvent" to 300 000; (the run will stop by itself when done)
    • Select "RunType": Pedestals;
    • Beam type: "No beam" or "Protons";
    • Beam energy: put value in "GeV" if any;
    • Tier0 Project Name: data09_calib
    • "File Name Tag": write pedestals; (DO NOT USE dots, blanks and other special symbols)
    • Recording: mark "Enable writing of the output file";

    • Click on the Set Value red box to commit changes;

  3. Follow the   BOOT   →   INITIALIZE   →   CONFIG   →   START procedure carefuly
    from the Run Control Commands panel (top left) of the "RunControl GUI" to start the pedestals run.

  4. when the run actually starts, a pop-up window will appear asking you to enter details about the run in the E-LOG.

  5. Write the details of the run here like: "pedestals". Put extension information if needed.

  6. Check the pedestals run progress
    under the Counters tab of the Run Information & Settings panel inside the "Run Control GUI".

  7. press OHP button on the DAQPanel
    to check everything is fine looking at the histograms. Pedestal histograms should show gaussian-shaped distributions. Beware that different histograms are filled at different time, so that at least 5 minutes MUST elapse before you can see ALL histograms.

  8. Wait untill pedestals run will be finished collecting ~300 000 events.

Take the calibration run:

  1. In the "RunControl GUI" window look for the Run Information & Settings panel (left, middle)

  2. Click there on the Settings tab at the bottom of the Run Information & Settings panel
    to set parameters for the calibration run:

    • Max Events: put zero-value: 0. This "0" means, there is no max. number of events to collect and you must control the collected statistics by yourself.
    • Run Type: Select CalQDC.
    • Beam type: "No beam" or "Protons";
    • Beam energy: put value in GeV if any;
    • Tier0 Project Name: data09_calib
    • File Name Tag: type in: "calibration", or something like this. AVOID dots, blanks and other special symbols !
    • Recording: mark "Enable writing of the output file"
    • Click on the Set Value red box to commit your changes

  3. Let calibration running for 30 minutes or so to collect enough statistics. You'll have to stop the run: either once all histograms have at least 150000 entries , or when you can see new points in the DCS trending plots.

  4. Calibration histograms should show single photo-electron spectra.
    Beware that different histograms are filled at different time, so that at least 5 minutes MUST elapse before you can see ALL histograms.

  5. At the end of each run, results are sent to DCS.
  6. Look at the corresponding trending plots in the LUCID DCS display to make sure nor the pedestal MEANS or the pedestal RMS changed significantly from previous runs. If so, please WARN the TDAQ-Expert (16 2443). Calibration values ought to be around 15. If not, check the fit chi2 and WARN LUCID TDAQ on-call expert (16-2443)

When both pedestals and calibration runs done (before data taking):

  1. perform the UNCONFIGURE, TERMINATE and SHUTDOWN transitions

  2. close the GUI.
    (IMPORTANT: to close the GUI before further actions !)

  3. Answer YES when asked if you also want to shutdown the partition infrastructure.
    (IMPORTANT: to shutdown the partition infrastructure).

  4. Reset the DAQPanel for Combined ATLAS run

  5. Tell the ATLAS DAQ shifter to RECONFIGURE ALL LUCID branches
    ( IMPORTANT: ALL LUCID branches must be not only included but RECONFIGURED )

  6. Check L1 Trigger prescales are set for the appropriate data taking.

 
-- AnAst - 21-Oct-2009

META FILEATTACHMENT attachment="firefox_pref_network.png" attr="" comment="Snapshot: Firefox %22Edit%22-->%22Preference%22 pop-up window" date="1259336152" name="firefox_pref_network.png" path="firefox_pref_network.png" size="48478" stream="firefox_pref_network.png" tmpFilename="/usr/tmp/CGItemp36241" user="anatoli_2eastvatsatourov_40cern_2ech" version="1"
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback