<?xml version="1.0" encoding="UTF-8"?>
<event>
<ID>149557</ID>
<category>Conferences</category>
<parentProtection>false</parentProtection>
<materialList>[["minutes", "Minutes"], ["notes", "Notes"], ["paper", "Paper"], ["poster", "Poster"], ["slides", "Slides"], ["summary", "Summary"]]</materialList>
<announcer>
 <user>
  <title></title>
  <name first="John Steven" middle="" last="De Stefano Jr"></name>
  <organization>Brookhaven National Laboratory (US)</organization>
  <email>jd@bnl.gov</email>
  <userid>22874</userid>
 </user>
</announcer>
<supportEmail caption="Support">chep2012@bnl.gov</supportEmail>
<keywords>
 <keyword>CHEP</keyword>
</keywords>
<title>Computing in High Energy and Nuclear Physics (CHEP) 2012</title>
<description></description>
<participants></participants>
<closed>False</closed>
<location>
 <name>New York City, NY, USA</name>
 <address></address>
 <room></room>
</location>
<startDate>2012-05-21T06:00:00</startDate>
<endDate>2012-05-25T18:00:00</endDate>
<creationDate>2011-08-02T14:01:11</creationDate>
<modificationDate>2012-06-19T20:27:46</modificationDate>
<timezone>US/Eastern</timezone>
<chair>
 <user>
  <title></title>
  <name first="Michael" middle="" last="Ernst"></name>
  <organization>Unknown</organization>
  <email>mernst@bnl.gov</email>
 </user>
 <user>
  <title></title>
  <name first="Dirk" middle="" last="Duellmann"></name>
  <organization>CERN</organization>
  <email>dirk.duellmann@cern.ch</email>
 </user>
</chair>
<contribution color="#8ec473" textcolor="#021F03">
 <ID>481</ID>
 <parentProtection>false</parentProtection>
 <materialList>[["minutes", "Minutes"], ["notes", "Notes"], ["paper", "Paper"], ["poster", "Poster"], ["slides", "Slides"], ["summary", "Summary"]]</materialList>
 <track>Event Processing (track 2)</track>
 <type>
  <id>2</id>
  <name>Poster</name>
 </type>
 <title>Methods and the computing challenges of the realistic simulation of physics events in the presence of pile-up in the ATLAS experiment</title>
 <speakers>
  <user>
   <title></title>
   <name first="Andrew" middle="" last="Haas"></name>
   <organization>SLAC National Accelerator  Laboratory</organization>
   <email>drandyhaas@gmail.com</email>
  </user>
 </speakers>
 <primaryAuthors>
  <user>
   <title></title>
   <name first="Collaboration" middle="" last="Atlas"></name>
   <organization>Atlas</organization>
   <email>carlino@na.infn.it</email>
  </user>
 </primaryAuthors>
 <coAuthors>
  <user>
   <title></title>
   <name first="Philip" middle="" last="Clark"></name>
   <organization>University of Edinburgh (GB)</organization>
   <email>p.j.clark@ed.ac.uk</email>
  </user>
  <user>
   <title></title>
   <name first="Daniel" middle="" last="Froidevaux"></name>
   <organization>CERN</organization>
   <email>daniel.froidevaux@cern.ch</email>
  </user>
 </coAuthors>
 <location>
  <name>Kimmel Center</name>
  <address>None</address>
  <room>Rosenthal Pavilion (10th floor)</room>
 </location>
 <startDate>2012-05-24T13:30:00</startDate>
 <endDate>2012-05-24T18:15:00</endDate>
 <duration>04:45</duration>
 <abstract>We are now in a regime where we observe substantial multiple proton-proton collisions within each filled LHC bunch-crossing and also multiple filled bunch-crossings within the sensitive time window of the ATLAS detector. This will increase with increased luminosity in the near future.
Including these effects in Monte Carlo simulation poses significant computing challenges. We present a description of the standard approach used by the ATLAS experiment and details of how we manage the conflicting demands of keeping the background dataset size as small as possible while minimizing the effect of background event re-use. We also present details of the methods used to minimize the memory footprint of these digitization jobs, to keep them within the grid limit, despite combining the information from thousands of simulated events at once.
We also describe an alternative approach, known as Overlay. Here, the actual detector conditions are sampled from raw data using a special zero-bias trigger, and the simulated physics events are overlaid on top of this zero-bias data. This gives a realistic simulation of the detector response to physics events. The overlay simulation runs in time linear in the number of events and consumes memory proportional to the size of a single event, with small overhead. We explain the computational issues and challenges that will arise in running overlay in production mode on the grid. Finally we discuss the computational issues that may arise in the future in generating large amount of luminosity weighted zero-bias data and making it available on the grid</abstract>
 <material>
  <ID>slides</ID>
  <title>Slides</title>
  <description></description>
  <type></type>
  <files>
  </files>
  <types>
   <type>
    <name>doc</name>
    <imgURL>http://indico.cern.ch/images/word.png</imgURL>
    <imgAlt>word file</imgAlt>
   </type>
   <type>
    <name>ppt</name>
    <imgURL>http://indico.cern.ch/images/powerpoint.png</imgURL>
    <imgAlt>powerpoint file</imgAlt>
   </type>
   <type>
    <name>pdf</name>
    <imgURL>http://indico.cern.ch/images/pdf_small.png</imgURL>
    <imgAlt>pdf file</imgAlt>
   </type>
   <type>
    <name>odt</name>
    <imgURL>http://indico.cern.ch/images/writer.png</imgURL>
    <imgAlt>writer file</imgAlt>
   </type>
   <type>
    <name>odp</name>
    <imgURL>http://indico.cern.ch/images/impress.png</imgURL>
    <imgAlt>presentation file</imgAlt>
   </type>
   <type>
    <name>ods</name>
    <imgURL>http://indico.cern.ch/images/calc.png</imgURL>
    <imgAlt>spreadsheet file</imgAlt>
   </type>
   <type>
    <name>other</name>
    <imgURL>http://indico.cern.ch/images/file_small.png</imgURL>
    <imgAlt>unknown type file</imgAlt>
   </type>
   <type>
    <name>link</name>
    <imgURL>http://indico.cern.ch/images/link.png</imgURL>
    <imgAlt>link</imgAlt>
   </type>
  </types>
 </material>
</contribution>
<plugins>
 <collaboration>
<!-- Needed for timezone awareness -->
  <todayReference>2013-05-24</todayReference>
  <tomorrowReference>2013-05-25</tomorrowReference>
 </collaboration>
</plugins>
</event>
