Google Earth

Installation

Installation instructions can be found here.

Steps for demo

  1. Zoom out to show the full globe activity
  2. Explain
    1. Fixed lines are active data links, where GREEN is good status, YELLOW warning status, RED critical status
    2. Blue lines showing up from time to time are processing jobs being picked up by worker nodes
  3. Zoom in: to the site of their choice if they have a specific one, to the Europe region if they don't
  4. Explain
    1. Dots moving along the lines are transfer attempts, where GREEN is a successful one, RED is a failed attempt
  5. Click on a site to pop up additional info
  6. Explain ....

QAOES

QAOES stands for Quick Analysis Of Error Sources. The tool is available via the web interface QAOES.

Steps for demo

  1. load the page and select the 3 input parameters
  2. explain the 3 parameters:
    1. timerange: the input data for the Association Rule mining is job monitoring data taken from the past x hours. Choices are: 6, or 12 hours.
    2. minimum number of jobs, called "minimum support": it is the minimum percentage of jobs in the input data that has to contain all the components (component = attribute-value pair, like site=CERN) in order to generate a rule. The value is given in percent, so between 0 and 100. Choices in the interface are: 0.1%, 0.5%, 1%.
    3. confidence: states how significant the rules have to be. It is the percentage of how many jobs which contain the components of the antecedent also contain the components of the consequent.
  3. click "Show Output" and explain:
    • in general: an association rule is an implication A => C, the left-hand-side is also called antecedent, the right-hand-side consequent. The output of QAOES presents only rules of the format "components" => "Error Code".
    • there are three values for each association rule (line):
      1. support/number of jobs: percentage of jobs and number of jobs in the input data that contain the components and the error code
      2. confidence of the rule
      3. lift: represents the interestingness of a rule. The higher the value, the more "interesting". It is the ratio of the components AND the error occuring together and the components and the error occuring separately, lift(A=>C) = F(A and C)/(F(A)*F(C))
    • for each line, there are a couple of links on the left side:
      1. click on the link to the job summary, which contains the settings of the present components
      2. click on "Add Rule" to add a new rule to the expert system. A rule consists of a problem and a solution. For the problem definition the attributes and values in the present components can be used. The solution is a chain of steps that should be undertaken.
      3. "Show/hide Rules": if there are already rules in the knowledge base which match a present association rule, the rule (with the solution) can be shown/hidden. A rule can be edited and ranked.

SAM

Service Availability Monitoring

1. We created first the CMS interface 2. The other experiments saw it, liked it and asked for the same. 3. Clickable plots to see the performance of sites and services 4. Possibility to go down to the log of the tests

Link

http://dashb-sam.cern.ch (at the moment, only the part of the VO view is available)

Steps for demo

  1. Start with the http://dashb-sam.cern.ch
  2. Select an experiment
  3. Uncheck the box 'open in a new window'
  4. Click on Show results (it might take a while)
  5. Click on historical view
  6. Select some parameters, and click on show results
  7. If the person is still there, keep on clicking on plots

SSB

Site Status Board

Links

http://dashb-ssb.cern.ch/ssb.html http://dashb-alice-ssb.cern.ch/ssb.html http://dashb-lhcb-ssb.cern.ch/ssb.html

Demo instruction

  1. Start with the CMS map.
  2. Present the index and expanded table
  3. If you click on a cell, you will get a link to the info provided by the experiment for that cell
  4. If you click on a header, you will get the historical view
  5. Click on alternative views, and then the 'commissioning'
  6. Explain that the experiment can define different activities, and different metrics for each activity
  7. Show the gridmap interface
  8. If you have time, show also the gridmap interface of ALICE, and click on play. You will see how the sites have evolved over the last 2 months

-- RicardoRocha - 2009-09-15


This topic: ArdaGrid > WebHome > Dashboard > DemoGuidelines
Topic revision: r7 - 2009-12-18 - unknown
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback