Difference: TRTDetectorOperationManualExpert (20 vs. 21)

Revision 212012-02-01 - vogel

Line: 1 to 1
 
META TOPICPARENT name="AtlasOperation"
Line: 19 to 19
 

<-- /editTable -->
Changed:
<
<
15 Oct 2009 What to do if there are no default parameters in the DAQ Panel? The recommended values can always be found on the TRT Whiteboard.
>
>
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.
 
15 Oct 2009 How to get the trigger configuration of the current run? The easiest way is to ask the trigger shifter.
Changed:
<
<
15 Oct 2009 How does one insert a DCS alarm into the elog? Right-clicking on the alarm will bring up a menu. One of the menu items is "insert to elog".
>
>
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.
Changed:
<
<
15 Oct 2009 What is the difference between the MRS Monitor and the Log Manager? The MRS Monitor presents only current messages, the Log Manager can browse through the entire archive of MRS messages from the past.
>
>
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.
 

TRT Expert Monitoring

Line: 43 to 43
 

Log Files

Changed:
<
<
  • When running the standalone partition the log files are stored in /tmp/[PartitionName] on the computer where the process is running. The host on which the process is running is shown in the “Advanced” tab of the IGUI.
  • When running with the ATLAS partition the log files are stored in /local_sw/logs/tdaq-04-00-01/ATLAS. They also appear in the partlogs web interface.
>
>
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

Line: 60 to 59
 

Creating a Stand-Alone Partition

Changed:
<
<
  • set up the TDAQ environment by sourcing /det/tdaq/scripts/setup_TDAQ.sh
  • set up a recent Athena version using AtlasSetup
  • get a raw data file that will serve as input for the test partition
  • run build_partition.sh with that file to create a skeleton partition
  • add the missing pieces (monitoring segment, DQM segment) to the partition
>
>
  • Set up the TDAQ environment by sourcing /det/tdaq/scripts/setup_TDAQ.sh.
  • 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 build_partition.sh 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

Line: 111 to 110
 
mdtdq.php, tiledq.php, trtdq.php respective subsystems Displays the DQ flag colors of the DQ regions of the respective subsystem.
lastruns.py 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.
Changed:
<
<
META PREFERENCE name="TDAQ_VERSION" title="TDAQ_VERSION" type="Set" value="tdaq-03-00-01"
>
>
META PREFERENCE name="TDAQ_VERSION" title="TDAQ_VERSION" type="Set" value="tdaq-04-00-01"
 
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