<?xml version="1.0" encoding="UTF-8"?>
<articles>
<article xmlns:xlink="http://www.w3.org/1999/xlink/">
  <front>
    <journal-meta>
      <journal-title>Nucl. Instrum. Methods Phys. Res., A</journal-title>
      <abbrev-journal-title>Nucl. Instrum. Methods Phys. Res., A</abbrev-journal-title>
      <issn>0167-5087</issn>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>ATLAS trigger and data acquisition</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <name>
            <surname>Scannicchio</surname>
            <given-names>D A</given-names>
          </name>
          <aff>
            <institution>CERN</institution>
          </aff>
        </contrib>
      </contrib-group>
      <pub-date pub-type="pub">
        <year>2010</year>
      </pub-date>
      <volume>617</volume>
      <fpage>306</fpage>
      <lpage>309</lpage>
      <self-uri xlink:href="http://cds.cern.ch/record/1290345"/>
    </article-meta>
    <abstract>The ATLAS trigger system is based on three levels of event selection that selects the physics of interest from an initial bunch crossing rate of 40 MHz to an output rate of View the MathML source compatible with the offline computing power and storage capacity. During nominal LHC operations at a luminosity of View the MathML source, decisions must be taken every 25 ns. The LHC is expected to begin operations with a peak luminosity of View the MathML source with far fewer number of bunches, but quickly ramp up to higher luminosities. Hence, the ATLAS Trigger and Data Acquisition system needs to adapt to the changing beam conditions preserving the interesting physics and detector requirements that may vary with these conditions.</abstract>
  </front>
  <article-type>research-article</article-type>
  <ref/>
</article>

</articles>