TRT Shift Trainer Help

This area is intended to explain the shift Trainer's duties and to answer frequently asked questions.

TRT Shift Trainer Duties

The TRT TTP are the TRT shift Training Personnel. There is a week-long shift equivalent to one shift credit (if you think this needs to be increased, feel free to ask). Most of the work currently is for supervising the practical sessions. To sign up, use OTP task 529095.

  • Supervise Practical Sessions with Trainee Shifters. Sessions are currently held every Wednesday from 14:00 to 17:00 in the ID Satellite Control Room (building 3159). Trainee shifters sign up to OTP task ID 30910. There are only four slots open per session, but others may arrive without signing up. Please be flexible when this happens. Make sure everyone has a chance to try out all of the shifter tools. The goal is not to make them experts, just to make them competent shifters. Also make sure that the new shifters enter their name in the table at TrtAcrShifterCertificationRecords.
  • Answer questions that the trainees have. New shifters may ask questions on the email list ( or at the practical sessions. Answer the questions to the best of your ability. If you encounter a question (or suggestion) that you cannot answer please post it the FAQs below and/or send an email to the TTP email list.
  • To try to schedule special sessions for shifters who cannot attend a regular session before their first shift. The extra sessions should be scheduled with the TTP who is on shift during the week if possible. If the on shift TTP cannot schedule a special session then they need to inform the other TTPs by emailing the TTP list and asking for a volunteer.
  • Make sure that documentation is up-to date and sufficient for training new shifters. If it is not then the responsible expert needs to be informed. All of the documentation is available at NewTRTShifters, including the Shifter Training Checklist, Introductory presentations, and new shifter orientation.
  • Brand new shifters may also require an orientation session. This should be scheduled between the TTP on shift and the brand new shifter.

TRT Shift Trainer FAQs

Date QuestionSorted ascending Answer
15 Oct 2009 How to get the trigger configuration of the current run? The easiest way is to ask the trigger shifter.
15 Oct 2009 How to insert a DCS alarm into the e-log? Right-click on the alarm, select "insert to elog" from the context menu.
15 Oct 2009 How to tell if some parts of the TRT have been disabled from the readout? Look at DQMD (areas flagged black), the Cobra Panel (items marked as masked), and MRS messages.
15 Oct 2009 What is the difference between the MRS Monitor and the Log Manager? The MRS Monitor presents only new messages, the Log Manager can browse through the entire archive of past MRS messages.
15 Oct 2009 What to do if there are no default parameters in the DAQ Panel? The recommended values are given on the TRT Whiteboard.

TRT Expert Monitoring

Connecting to the Point-1 Network

See the Sysadmins FAQ, section “Gateways”. In short, connect to and then hop to your destination host.

ATLAS Software at Point 1

The ATLAS software is located in the directory /sw/atlas. There you can find the latestest releases that are installed at Point 1

Database Access at Point 1

The TRT Monitoring Segment for the Combined Run

The segment for the combined run is located in the OKS subdirectory /atlas/oks/tdaq-04-00-01/trt/segments/monitoring.

Log Files

The log files of all applications are stored in /logs/tdaq-04-00-01/ on the host where each process is running. The host is shown in the “Advanced” tab of the IGUI. Log files can also be accessed through the partlogs web interface.

Running the IGUI

First source the DAQ environment with source /det/tdaq/scripts/ Then you can start the IGUI with igui_start -p or alternatively setup_daq -p ATLAS -d /atlas/oks/tdaq-04-00-01/combined/partitions/

Running the DAQ Panel

The DAQ panel lives in /etc/CRD/bin/panel. It's not on every machine, so make sure you're on one of the pc-trt-scr-* or pc-atlas-cr-* machines. When you open it, you'll need to enter some settings that are provided on the TRT Whiteboard.

Stand-Alone Partition

Running a stand-alone partition is a good way to debug the monitoring framework with the online system. The following describes how to create your own stand along partion and how to run it.

Creating a Stand-Alone Partition

  • Set up the TDAQ environment by sourcing /det/tdaq/scripts/
  • Set up a recent Athena version using AtlasSetup, which is available under /sw/atlas/AtlasSetup.
  • Get a raw data file that will serve as input for the test partition. You can use copySFO (“Copy File”) to get a get a raw data file from an SFO.
  • Run with that file to create a skeleton partition.
  • Add the missing pieces (DQM segment with DQ Agent, monitoring segment with Athena) to the partition manually.

Running a Stand-Alone Partition

The current working stand alone partition for TRT Monitoring is located at /det/trt/monitoring/test_partition/tdaq-04-00-01/ Go to that directory and start the partition by running ./start_test_partition.

Webscripts at Point 1


A number of scripts have been written to create tables or widgets with information relevant to shifters. They can be included on the Point 1 TWiki pages e.g. in an iframe as part of the Whiteboard or shifter instructions. The scripts are mostly written in Python, some might be coded in PHP. A few scripts are TRT-specific (e.g. calibcal), others can be and are used by other ATLAS subsystems (e.g. lastruns or dayprog).

Location and Access

Look at the SysAdmins/WebServers TWiki to learn more about the setup of webservers and web directories at Point 1. The responsible subsystem experts have to demand access rights. In particular you need to request the role ATLAS:www from to access the web server.

Scripts can be executed in a webbrowser from inside Point 1 via or from outside Point 1 through


It is important to adhere to P1 security requirements, a few guidelines are:

  1. Keep the number of scripts small, i.e. avoid ending up with a cluttered area
  2. Keep the number of persons small that have access to this area (ideally one per subsystem)
  3. Follow secure scripting principles to avoid hacker attacks through code injection/cross-side-scripting (TDAQ sysadmins and CERN IT Security will regularly test scripts for vulnerabilities):
    • Avoid filesystem and "power" commands like eval(), exec() etc., if possible also fopen()
    • In case you have to use text input fields make sure to disallow any tags or even all non-alphanumerical characters as input (use re.sub('[^0-9a-zA-Z]','',<string>))
  4. Do not store unused or old scripts in the cgi-executable directory. You can temporarily rename them to .py.old or .php.old (web access to .old files is denied). Ideally move them outside the webscripts area.
  5. If you are unsure about your script security do not hesitate to contact
  6. Please make sure that the script has your name/email and ATLAS detector/group in the comments at the beginning, such that it will easier for the ATLAS TDAQ sysadmins to contact the responsible person in case of problems.

How to Include Scripts in a TWiki Page

In order to include the scripts on a TWiki page you can use "inline frames". The <iframe> tag defines an inline frame that contains another document. It is supported in all major browsers. More documentation can be found at W3C. Example:

    <iframe width="600px" height="200px" scrolling="no" frameborder="0" src="/webscripts/global/">This text is displayed if a browser does not recognize the iframe tag.</iframe>
Note you should not include a hostname in the link, so the script is requested from the same host as the TWiki page itself (i. e. pc-atlas-www internally, atlasop externally).

List of Scripts

Script name Used by Description TRT The script queries the dates of various TRT calibration scans from an Oracle database and displays them in a calendar. The next foreseen scan dates are indicated. In the widget mode a small box shows the outstanding scans to the shifter or displays OK if all scans are still valid.
dayprog.php various subsystems Displays the daily ATLAS run program in a small box, so it can be included on the subsystem Whiteboard.
mdtdq.php, tiledq.php, trtdq.php respective subsystems Displays the DQ flag colors of the DQ regions of the respective subsystem. various subsystems Returns a table of the last n runs with general run information and subsystem-specific DQ results. Direct links to the flag upload website are available.
Edit | Attach | Watch | Print version | History: r21 < r20 < r19 < r18 < r17 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r21 - 2012-02-01 - vogel
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 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