Tile Commissioning Web System

1
INTRODUCTION During the ATLAS commissioning, runs are reconstructed by scripts inside the ATHENA framework. This procedure stores data in different locations: • Parameters in the local MySQL database • Histograms and plots in the local collaboration computer • Ntuples in CASTOR Voltages, currents and temperatures provided by the Detector Control System (DCS) are also important. This is stored in the Oracle archive. Previously, the offline shifter needed to access all the data and needed to know whether the run was already reconstructed as illustrated in Figure 1. TCWS supports TileCal Commissioning activities with added advantages: Users do not have to follow scripts • Changes are transparent to users • Consistency is guaranteed Plots and results data are available • Efficient data retrieval through the web • Only a Web browser is required TILE COMMISSIONING WEB SYSTEM TILE COMMISSIONING WEB SYSTEM TCWS integrates four independent applications: Web Interface for Shifters, Tilecomm Analysis, Timeline and DCS Web System Web Interface for Shifters (WIS) In the main table, it has the information about the runs and the corresponding analysis in a test- oriented overview as represented in Figure 2. Web System to Support Analysis for Experimental Equipment Web System to Support Analysis for Experimental Equipment Commissioning Commissioning CHEP 2007 CHEP 2007 TileComm Analysis Provides an equipment-oriented view that allows the investigation and analysis of generated plots per run/module. Integrates the Data Quality Manager analysis with shifter's comments for equipment performance. The user can choose one module and/or runs to analyze it or to look one already analyzed. The Figure 3 shows how the data can be accessed. Timeline Provides visualization in chronological order of runs for a given set of modules. The summary of corresponding analysis is then displayed. The Figure 4 is one example. DCS Web System The system presents the information in three ways: Daily Monitoring – Displays Mean and RMS values for each module/brick pair in a given day. Shows 24 hours parameters plots. Monthly Analysis – Displays Mean and RMS values for each module/brick for a given month. Shows correlation and progress plots for 30 days. Real Time – Displays the current values of voltages, currents and temperatures. This data is provided by the following tools: Glance - System for retrieving and integrating data from any database http://cern.ch/atglance TileDCSDataGrabber – Framework to retrieve data from the Oracle archive and the conditions database and it produces plots. https://twiki.cern.ch/twiki/bin/view/Atlas/TileDC SDataGrabber The Figure 5 shows the daily monitoring, with the mean values, RMS values and over 24 hours plots. The Figure 6 shows the real time display. Run Athena CASTOR Ntuples CommInfo Runs' data plots ORACLE Archive DCS USER Parameters Status General Status Plot related Parameter Modules visualizati on Comments about modules performance Shifter s name DQM results Run informati on Legend Mouse- over View/edit comment for module performance Time period selection Module selection Test type selection Run Type Shifter s name Access to run analysis and results Run performan ce overview Run Number Run Date #Even ts Drawer sectors Module s Status Detailed comments TCWS GROUP: [email protected] Alexandre Faria ([email protected]) [email protected] Fernando.Guimaraes.Ferreira@c ern.ch [email protected] [email protected] [email protected] http://cern.ch/tcws/ Access to plots Run Type Run Number Run Date Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6

description

Ntuples. CASTOR. General Status. plots. Parameter. Run. Athena. Status. USER. Plot related. ORACLE Archive. CommInfo. Parameters. Runs' data. DCS. Run performance overview. Access to run analysis and results. #Events. Shifters name. Run Date. Run Type. Run Number. - PowerPoint PPT Presentation

Transcript of Tile Commissioning Web System

Page 1: Tile Commissioning Web System

INTRODUCTION

During the ATLAS commissioning, runs are reconstructed by scripts inside the ATHENA framework. This procedure stores data in different locations:

• Parameters in the local MySQL database• Histograms and plots in the local collaboration computer• Ntuples in CASTOR

Voltages, currents and temperatures provided by the Detector Control System (DCS) are also important. This is stored in the Oracle archive.

Previously, the offline shifter needed to access all the data and needed to know whether the run was already reconstructed as illustrated in Figure 1.

TCWS supports TileCal Commissioning activities with added advantages: • Users do not have to follow scripts• Changes are transparent to users• Consistency is guaranteed• Plots and results data are available• Efficient data retrieval through the web• Only a Web browser is required TILE COMMISSIONING WEB SYSTEMTILE COMMISSIONING WEB SYSTEM

TCWS integrates four independent applications: Web Interface for Shifters, Tilecomm Analysis, Timeline and DCS Web System

Web Interface for Shifters (WIS)

In the main table, it has the information about the runs and the corresponding analysis in a test-oriented overview as represented in Figure 2.

INTRODUCTION

During the ATLAS commissioning, runs are reconstructed by scripts inside the ATHENA framework. This procedure stores data in different locations:

• Parameters in the local MySQL database• Histograms and plots in the local collaboration computer• Ntuples in CASTOR

Voltages, currents and temperatures provided by the Detector Control System (DCS) are also important. This is stored in the Oracle archive.

Previously, the offline shifter needed to access all the data and needed to know whether the run was already reconstructed as illustrated in Figure 1.

TCWS supports TileCal Commissioning activities with added advantages: • Users do not have to follow scripts• Changes are transparent to users• Consistency is guaranteed• Plots and results data are available• Efficient data retrieval through the web• Only a Web browser is required TILE COMMISSIONING WEB SYSTEMTILE COMMISSIONING WEB SYSTEM

TCWS integrates four independent applications: Web Interface for Shifters, Tilecomm Analysis, Timeline and DCS Web System

Web Interface for Shifters (WIS)

In the main table, it has the information about the runs and the corresponding analysis in a test-oriented overview as represented in Figure 2.

Web System to Support Analysis for Experimental Equipment Web System to Support Analysis for Experimental Equipment CommissioningCommissioning

CHEP 2007CHEP 2007

TileComm Analysis

Provides an equipment-oriented view that allows the investigation and analysis of generated plots per run/module. Integrates the Data Quality Manager analysis with shifter's comments for equipment performance. The user can choose one

module and/or runs to analyze it or to look one already analyzed. The Figure 3 shows.how the data can be accessed

Timeline

Provides visualization in chronological order of runs for a given set of modules. The summary of corresponding analysis is then.displayed. The Figure 4 is one example

TileComm Analysis

Provides an equipment-oriented view that allows the investigation and analysis of generated plots per run/module. Integrates the Data Quality Manager analysis with shifter's comments for equipment performance. The user can choose one module and/or runs to analyze it or to look one already analyzed. The Figure 3 shows how the data can be accessed.

Timeline

Provides visualization in chronological order of runs for a given set of modules. The summary of corresponding analysis is then displayed. The Figure 4 is one example.

DCS Web System

The system presents the information in three ways: Daily Monitoring – Displays Mean and RMS values for each module/brick pair in a given day. Shows 24 hours parameters plots.

Monthly Analysis – Displays Mean and RMS values for each module/brick for a given month. Shows correlation and progress plots for 30 days.

Real Time – Displays the current values of voltages, currents and temperatures.

This data is provided by the following tools:

• Glance - System for retrieving and integrating data from any databasehttp://cern.ch/atglance

• TileDCSDataGrabber – Framework to retrieve data from the Oracle archive and the conditions database and it produces plots. https://twiki.cern.ch/twiki/bin/view/Atlas/TileDCSDataGrabber

The Figure 5 shows the daily monitoring, with the mean values, RMS values and over 24 hours plots. The Figure 6 shows the real time display.

DCS Web System

The system presents the information in three ways: Daily Monitoring – Displays Mean and RMS values for each module/brick pair in a given day. Shows 24 hours parameters plots.

Monthly Analysis – Displays Mean and RMS values for each module/brick for a given month. Shows correlation and progress plots for 30 days.

Real Time – Displays the current values of voltages, currents and temperatures.

This data is provided by the following tools:

• Glance - System for retrieving and integrating data from any databasehttp://cern.ch/atglance

• TileDCSDataGrabber – Framework to retrieve data from the Oracle archive and the conditions database and it produces plots. https://twiki.cern.ch/twiki/bin/view/Atlas/TileDCSDataGrabber

The Figure 5 shows the daily monitoring, with the mean values, RMS values and over 24 hours plots. The Figure 6 shows the real time display.

Run Athena

CASTOR

Ntuples

CommInfo

Runs' data

plots

ORACLEArchive

DCS

USER

Parameters

Status

GeneralStatus

Plot related

Parameter

Modules visualization

Comments about modules performance

Shifters name

DQM results

Run informatio

n

Legend Mouse-over

View/edit comment for

module performance Time period

selection

Module selection

Test type selection

Run Type

Shifters name

Access to run

analysis and results

Run performan

ce overviewRun

Number

Run Date

#Events

Drawer sectors

Modules

Status

Detailed comments

TCWS GROUP:•[email protected]•Alexandre Faria ([email protected])•[email protected][email protected][email protected][email protected][email protected]

http://cern.ch/tcws/

Access to plots

Run Type

Run Number Run

Date

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6