ComputingandSoftwarePublicResults < AtlasPublic

<!--
   * Set ALLOWTOPICCHANGE = atlas-twiki-admins, atlas-physics-coordination, atlas-mgt-members, Main.RichardMount, Main.EricLancon, Main.MarkusElsing, Main.RolfSeuster, Main. JaroslavGuenther
-->

%ATLASPUBLICHEADER%

---+!! <nop> Computing and Software - Public Results

%TOC% <!-- this line is optional --> 
%STARTINCLUDE% 

---+ Introduction

<!-- Add an introduction here, describing the purpose of this topic. -->

This page contains public plots and documents related to ATLAS computing and software. 

More material is available elsewhere concerning related activities, such as:
   * [[SimulationPublicResults][ATLAS simulation public results]]
   * [[MCPublicResults][ATLAS Monte Carlo public results]]
   * [[EventDisplayPublicResults][ATLAS event displays public results]]
All ATLAS public results can be found [[https://twiki.cern.ch/twiki/bin/view/AtlasPublic][here]].

The ATLAS code repository is also public, and can be found [[https://gitlab.cern.ch/atlas/athena/][on gitlab]].

---+ Computing TDR and related Documents

%TABLE{ sort="off" datavalign="center" headeralign="left,left,left" dataalign="left,left, left" tableborder="0" cellpadding="4" cellspacing="3" headerbg="%COLHEADER%" headercolor="white" databg="%COLTAB1%, %COLTAB2%"  tablerules="cols" tableframe="vsides" }%
| *report* | *links* | *year* |
| ATLAS HL-LHC Computing Conceptual Design Report | [[https://atlas.web.cern.ch/Atlas/GROUPS/PHYSICS/UPGRADE/CERN-LHCC-2020-015/][Plots]] [[https://cds.cern.ch/record/2729668][CDS]] | 2020 |
| Update of Computing Models for Run-2 | [[https://cds.cern.ch/record/1695401/?ln=en][CDS]] | 2014 |
| Computing TDR | [[https://cds.cern.ch/record/837738/?ln=en][CDS]] | 2005 |
| Computing Model Document | [[https://cds.cern.ch/record/811058/?ln=en][CDS]] | 2004 |
| Technical Proposal | [[https://cds.cern.ch/record/322322/?ln=en][CDS]] | 1996 |

---+ Public Notes, Conference Proceedings and Slides

<!-- A complete list of ATLAS computing and software public notes can be found on CDS. A lot of material is as well available on recent computing and software related talks and proceedings at international conferences. -->

%TABLE{ sort="off" datavalign="center" headeralign="left,left" dataalign="left, left" tableborder="0" cellpadding="4" cellspacing="3" headerbg="%COLHEADER%" headercolor="white" databg="%COLTAB1%, %COLTAB2%"  tablerules="cols" tableframe="vsides" }%
| *type of public documents* | *links* |
| list of ATLAS-SOFT-PUB notes | [[https://cds.cern.ch/search?ln=en&as=1&cc=ATLAS+Notes&m1=a&p1=ATL+SOFT+PUB&f1=reportnumber&op1=a&m2=a&p2=&f2=&op2=a&m3=a&p3=&f3=&action_search=Search&c=ATLAS+Notes&c=&sf=&so=d&rm=&rg=10&sc=1&of=hb][CDS]] |
| list of conference proceedings | [[https://cds.cern.ch/search?ln=en&as=1&cc=ATLAS+Notes&m1=a&p1=ATL+SOFT+PROC&f1=reportnumber&op1=a&m2=a&p2=&f2=&op2=a&m3=a&p3=&f3=&action_search=Search&c=ATLAS+Notes&c=&sf=&so=d&rm=&rg=10&sc=1&of=hb][CDS]] |
| list of conference talks | [[https://cds.cern.ch/search?ln=en&as=1&cc=ATLAS+Notes&m1=a&p1=ATL+SOFT+SLIDE&f1=reportnumber&op1=a&m2=a&p2=&f2=&op2=a&m3=a&p3=&f3=&action_search=Search&c=ATLAS&c=&sf=&so=d&rm=&rg=10&sc=1&of=hb][CDS]] |

---+ Recent Public Plots

<table  bgcolor="#f5f5fa" cellspacing="10" cellpadding="10" border="1"> <tbody> 


<!-- 
START Computing Model 2020 plots
-->

<tr>
<td bgcolor="#eeeeee"> 
Projected CPU requirements of ATLAS between 2020 and 2034 based on 2020 assessment. Three scenarios are shown, corresponding to an ambitious (“aggressive”), modest (“conservative”) and minimal (“baseline”) development programme. The black lines indicate annual improvements of 10% and 20% in the computational capacity of new hardware for a given cost, assuming a sustained level of annual investment. The blue dots with the brown lines represent the 3 ATLAS scenarios following the present LHC schedule. The red triangles indicate the Conservative R&D scenario under an assumption of the LHC reaching <mu>=200 in Run4 (2028-2030).
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/cpuHLLHC_comparison_2020_InputData_3April_CMSC.jpg" alt="CPU HL-LHC w CMS" /> <br>
 [[%ATTACHURL%/cpuHLLHC_comparison_2020_InputData_3April_CMSC.pdf][pdf-file]], [[%ATTACHURL%/cpuHLLHC_comparison_2020_InputData_3April_CMSC.jpg][jpg-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Projected CPU requirements of ATLAS between 2020 and 2034 based on 2020 assessment. Three scenarios are shown, corresponding to an ambitious (“aggressive”), modest (“conservative”) and minimal (“baseline”) development programme. The black lines indicate annual improvements of 10% and 20% in the computational capacity of new hardware for a given cost, assuming a sustained level of annual investment. The blue dots with the brown lines represent the 3 ATLAS scenarios following the present LHC schedule. 
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/cpuHLLHC_comparison_2020_InputData_3April_ATLAS.jpg" alt="CPU HL-LHC" /> <br>
 [[%ATTACHURL%/cpuHLLHC_comparison_2020_InputData_3April_ATLAS.pdf][pdf-file]], [[%ATTACHURL%/cpuHLLHC_comparison_2020_InputData_3April_ATLAS.jpg][jpg-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Snapshot of projected CPU resources required by ATLAS in 2030, by computational task
 </td>
 <td>
 <img width="90" src="%ATTACHURLPATH%/CPU_PieChart_baseline_3April_2030.jpg" alt="CPU HL-LHC" />  
 <img width="90" src="%ATTACHURLPATH%/CPU_PieChart_conservativeRD_3April_2030.jpg" alt="CPU HL-LHC" /> 
 <img width="90" src="%ATTACHURLPATH%/CPU_PieChart_aggressiveRD_3April_2030.jpg" alt="CPU HL-LHC" /><br>
[[%ATTACHURL%/CPU_PieChart_baseline_3April_2030.pdf][pdf-file]], [[%ATTACHURL%/CPU_PieChart_baseline_3April_2030.jpg][jpg-file]]      
     [[%ATTACHURL%/CPU_PieChart_conservativeRD_3April_2030.pdf][pdf-file]], [[%ATTACHURL%/CPU_PieChart_conservativeRD_3April_2030.jpg][jpg-file]]      
     [[%ATTACHURL%/CPU_PieChart_aggressiveRD_3April_2030.pdf][pdf-file]], [[%ATTACHURL%/CPU_PieChart_aggressiveRD_3April_2030.jpg][jpg-file]] 
 </td> 
</tr>

<tr>
<td bgcolor="#eeeeee"> 
Projected disk storage requirements of ATLAS between 2020 and 2034 based on 2020 assessment. Three scenarios are shown, corresponding to an ambitious (“aggressive”), modest (“conservative”) and minimal (“baseline”) development programme. The black lines indicate annual improvements of 10% and 20% in the storage capacity of new hardware for a given cost, assuming a sustained level of annual investment. The blue dots with the brown lines represent the 3 ATLAS scenarios following the present LHC schedule. 
 </td>
 <td align="center">
     <img src="%ATTACHURLPATH%/diskHLLHC_comparison_plot_2020_InputData_3April_ATLAS.jpg" alt="diskHLLHC_comparison_plot_2020_InputData_3April_ATLAS.jpg" width="300"  />
<br>
 [[%ATTACHURL%/diskHLLHC_comparison_plot_2020_InputData_3April_ATLAS.pdf][pdf-file]], [[%ATTACHURL%/diskHLLHC_comparison_plot_2020_InputData_3April_ATLAS.jpg][jpg-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Projected disk storage requirements of ATLAS between 2020 and 2034 based on 2020 assessment. Three scenarios are shown, corresponding to an ambitious (“aggressive”), modest (“conservative”) and minimal (“baseline”) development programme. The black lines indicate annual improvements of 10% and 20% in the storage capacity of new hardware for a given cost, assuming a sustained level of annual investment. The blue dots with the brown lines represent the 3 ATLAS scenarios following the present LHC schedule. The red triangles indicate the Conservative R&D scenario under an assumption of the LHC reaching <mu>=200 in Run4 (2028-2030). 
 </td>
 <td align="center">
     <img src="%ATTACHURLPATH%/diskHLLHC_comparison_plot_2020_InputData_3April_CMSC.jpg" alt="diskHLLHC_comparison_plot_2020_InputData_3April_CMSC.jpg" width="300"  />
<br>
 [[%ATTACHURL%/diskHLLHC_comparison_plot_2020_InputData_3April_CMSC.pdf][pdf-file]], [[%ATTACHURL%/diskHLLHC_comparison_plot_2020_InputData_3April_CMSC.jpg][jpg-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Snapshot of projected disk resources required by ATLAS in 2030, by data type
 </td>
 <td>
 <img width="90" src="%ATTACHURLPATH%/Disk_PieChart_baseline_3April_2030.jpg" alt="Disk HL-LHC" />  
 <img width="90" src="%ATTACHURLPATH%/Disk_PieChart_conservativeRD_3April_2030.jpg" alt="Disk HL-LHC" /> 
 <img width="90" src="%ATTACHURLPATH%/Disk_PieChart_aggressiveRD_3April_2030.jpg" alt="Disk HL-LHC" /><br>
[[%ATTACHURL%/Disk_PieChart_baseline_3April_2030.pdf][pdf-file]], [[%ATTACHURL%/Disk_PieChart_baseline_3April_2030.jpg][jpg-file]]      
     [[%ATTACHURL%/Disk_PieChart_conservativeRD_3April_2030.pdf][pdf-file]], [[%ATTACHURL%/Disk_PieChart_conservativeRD_3April_2030.jpg][jpg-file]]      
     [[%ATTACHURL%/Disk_PieChart_aggressiveRD_3April_2030.pdf][pdf-file]], [[%ATTACHURL%/Disk_PieChart_aggressiveRD_3April_2030.jpg][jpg-file]] 
 </td> 
</tr>


<tr>
<td bgcolor="#eeeeee"> 
Projected tape storage requirements of ATLAS at Tier-1 sites between 2020 and 2034 based on 2020 assessment. Three scenarios are shown for Tier-1 sites, corresponding to an ambitious (“aggressive”), modest (“conservative”) and minimal (“baseline”) development programme. The red triangles indicate the Conservative R&D scenario under an assumption of the LHC reaching <mu>=200 in Run4 (2028-2030).
 </td>
 <td align="center">
     <img src="%ATTACHURLPATH%/tapeT1HLLHC_comparison_plot_2020_InputData_3April_CMSC.jpg" alt="tapeT1HLLHC_comparison_plot_2020_InputData_3April_CMSC" width="300"  />
<br>
 [[%ATTACHURL%/tapeT1HLLHC_comparison_plot_2020_InputData_3April_CMSC.pdf][pdf-file]], [[%ATTACHURL%/tapeT1HLLHC_comparison_plot_2020_InputData_3April_CMSC.jpg][jpg-file]] 
 </td> </tr>


<tr>
<td bgcolor="#eeeeee"> 
Projected tape storage requirements of ATLAS at Tier-0 between 2020 and 2034 based on 2020 assessment. The Tier-0 line is based solely on the expected event size and LHC performance assumptions, since Tier-0 disk is used only for raw data and no other data products. The red triangles indicate the Conservative R&D scenario under an assumption of the LHC reaching <mu>=200 in Run4 (2028-2030)
 </td>
 <td align="center">
     <img src="%ATTACHURLPATH%/tapeT0HLLHC_comparison_plot_2020_InputData_3April_CMSC.jpg" alt="tapeT0HLLHC_comparison_plot_2020_InputData_3April_CMSC" width="300"  />
<br>
 [[%ATTACHURL%/tapeT0HLLHC_comparison_plot_2020_InputData_3April_CMSC.pdf][pdf-file]], [[%ATTACHURL%/tapeT0HLLHC_comparison_plot_2020_InputData_3April_CMSC.jpg][jpg-file]] 
 </td> </tr>


<tr>
<td bgcolor="#eeeeee"> 
Projected tape storage requirements of ATLAS at Tier-0 and Tier-1 sites between 2020 and 2034 based on 2020 assessment. Three scenarios are shown for Tier-1 sites, corresponding to an ambitious (“aggressive”), modest (“conservative”) and minimal (“baseline”) development programme. The Tier-0 line is based solely on the expected event size and LHC performance assumptions, since Tier-0 disk is used only for raw data and no other data products. The red triangles indicate the Conservative R&D scenario for Tier-0 and Tier-1 sites under an assumption of the LHC reaching <mu>=200 in Run4 (2028-2030)

 </td>
 <td align="center">
     <img src="%ATTACHURLPATH%/tapeT1T0HLLHC_comparison_plot_2020_InputData_3April_CMSC.jpg" alt="tapeT1T0HLLHC_comparison_plot_2020_InputData_3April_CMSC" width="300"  />
<br>
 [[%ATTACHURL%/tapeT1T0HLLHC_comparison_plot_2020_InputData_3April_CMSC.pdf][pdf-file]], [[%ATTACHURL%/tapeT1T0HLLHC_comparison_plot_2020_InputData_3April_CMSC.jpg][jpg-file]] 
 </td> </tr>


<tr>
<td bgcolor="#eeeeee"> 
Projected tape storage requirements of ATLAS at Tier-0 and Tier-1 sites between 2020 and 2034 based on 2020 assessment. Three scenarios are shown for Tier-1 sites, corresponding to an ambitious (“aggressive”), modest (“conservative”) and minimal (“baseline”) development programme. The Tier-0 line is based solely on the expected event size and LHC performance assumptions, since Tier-0 disk is used only for raw data and no other data products.


 </td>
 <td align="center">
     <img src="%ATTACHURLPATH%/tapeT1T0HLLHC_comparison_plot_2020_InputData_3April_ATLAS.jpg" alt="tapeT1T0HLLHC_comparison_plot_2020_InputData_3April_ATLAS" width="300"  />
<br>
 [[%ATTACHURL%/tapeT1T0HLLHC_comparison_plot_2020_InputData_3April_ATLAS.pdf][pdf-file]], [[%ATTACHURL%/tapeT1T0HLLHC_comparison_plot_2020_InputData_3April_ATLAS.jpg][jpg-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Snapshot of projected tape storage resources required by ATLAS Tier-1 sites in 2030, by data type
 </td>
 <td>
 <img width="90" src="%ATTACHURLPATH%/Tape_PieChart_baseline_3April_2030.jpg" alt="Disk HL-LHC" />  
 <img width="90" src="%ATTACHURLPATH%/Tape_PieChart_conservativeRD_3April_2030.jpg" alt="Tape HL-LHC" /> 
 <img width="90" src="%ATTACHURLPATH%/Tape_PieChart_aggressiveRD_3April_2030.jpg" alt="Tape HL-LHC" /><br>
[[%ATTACHURL%/Tape_PieChart_baseline_3April_2030.pdf][pdf-file]], [[%ATTACHURL%/Tape_PieChart_baseline_3April_2030.jpg][jpg-file]]      
     [[%ATTACHURL%/Tape_PieChart_conservativeRD_3April_2030.pdf][pdf-file]], [[%ATTACHURL%/Tape_PieChart_conservativeRD_3April_2030.jpg][jpg-file]]      
     [[%ATTACHURL%/Tape_PieChart_aggressiveRD_3April_2030.pdf][pdf-file]], [[%ATTACHURL%/Tape_PieChart_aggressiveRD_3April_2030.jpg][jpg-file]] 
 </td> 
</tr>





<!-- 
END Computing Model 2020 plots
-->



<tr>
<td bgcolor="#eeeeee"> 
*Superseded by 2020 modelling: see above* Estimated total disk resources (in PBytes) needed for the years 2018 to 2032 for both data and simulation processing. The plot updates the projection made in 2017 which was based on the Run-2 computing model and with updated LHC expected running conditions. The blue points show the improvements possible in two different scenarios, which require significant development work (1) top curve, reduction of AOD and DAOD size of 30% compared to the Run-2 trend, bottom curve further reduction with the inclusion of a common DAOD format to be used by most analysis, removal of previous year AODs from disk and the storage of only one DAOD version. The solid line shows the amount of resources expected to be available if a flat funding scenario is assumed, which implies an increase of 15% per year, based on the current technology trends.  
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/diskHLLHC_noold.png" alt="diskHLLHC_noold.png" /> <br>
 [[%ATTACHURL%/diskHLLHC_noold.pdf][pdf-file]], [[%ATTACHURL%/diskHLLHC_noold.png][png-file]] 
 </td> </tr>


<tr>
<td bgcolor="#eeeeee"> 
*Superseded by 2020 modelling: see above* Estimated total disk resources (in PBytes) needed for the years 2018 to 2032 for both data and simulation processing. The plot updates the projection made in 2017 which was based on the Run-2 computing model and with updated LHC expected running conditions. The brown points are estimates made in 2017 and based on the current event sizes and using the ATLAS computing model parameters from 2017. The blue points show the improvements possible in two different scenarios, which require significant development work: (1) top curve, reduction of AOD and DAOD size of 30% compared to the Run-2 trend, bottom curve further reduction with the inclusion of a common DAOD format to be used by most analysis, removal of previous year AODs from disk and the storage of only one DAOD version. The solid line shows the amount of resources expected to be available if a flat funding scenario is assumed, which implies an increase of 15% per year, based on the current technology trends.  
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/diskHLLHC_18.png" alt="diskHLLHC_18.png" /> <br>
 [[%ATTACHURL%/diskHLLHC_18.pdf][pdf-file]], [[%ATTACHURL%/diskHLLHC_18.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
*Superseded by 2020 modelling: see above* Fraction of disk resources needed in 2028 at the end of Run-4 for different data types. This plot: assuming a reduction in size of 30% of AOD and DAOD.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/disk2028_baseline.png" alt="disk2028_baseline.png" /> <br>
 [[%ATTACHURL%/disk2028_baseline.pdf][pdf-file]], [[%ATTACHURL%/disk2028_baseline.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
*Superseded by 2020 modelling: see above* Fraction of disk resources needed in 2028 at the end of Run-4 for different data types. This plot: a further reduction with the inclusion of a common DAOD format to be used by most analysis, removal of previous year AODs from disk and the storage of only one DAOD version. 
.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/disk2028_reduced.png" alt="disk2028_reduced.png" /> <br>
 [[%ATTACHURL%/disk2028_reduced.pdf][pdf-file]], [[%ATTACHURL%/disk2028_reduced.png][png-file]] 
 </td> </tr>


<tr>
<td bgcolor="#eeeeee"> 
*Superseded by 2020 modelling: see above* Estimated CPU resources (in MHS06) needed for the years 2018 to 2032 for both data and simulation processing. The plot updates the projection made in 2017 (which was based on the Run-2 computing model) with updated LHC running conditions and revised scenarios for future computing models. The blue points show the improvements possible in three different scenarios, which require significant development work: (1) top curve with fast calo sim used for 75% of the Monte Carlo simulation; (2) middle curve using in addition a faster version of reconstruction, which is seeded by the event generator information; (3) bottom curve, where the time spent in event generation is halved, either by software improvements or re-using some of the events.  The solid line shows the amount of resources expected to be available if a flat funding scenario is assumed, which implies an increase of 20% per year, based on the current technology trends.  
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/cpuHLLHC_noold.png" alt="cpuHLLHC_noold.png" /> <br>
 [[%ATTACHURL%/cpuHLLHC_noold.pdf][pdf-file]], [[%ATTACHURL%/cpuHLLHC_noold.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
*Superseded by 2020 modelling: see above* Estimated CPU resources (in MHS06) needed for the years 2018 to 2032 for both data and simulation processing. The plot updates the projection made in 2017 (which was based on the Run-2 computing model) with updated LHC running conditions and revised scenarios for future computing models. The brown points are estimates made in 2017, based on the current software performance estimates and using the ATLAS computing model parameters from 2017. The blue points show the improvements possible in three different scenarios, which require significant development work: (1) top curve with fast calo sim used for 75% of the Monte Carlo simulation; (2) middle curve using in addition a faster version of reconstruction, which is seeded by the event generator information; (3) bottom curve, where the time spent in event generation is halved, either by software improvements or by re-using some of the events.  The solid line shows the amount of resources expected to be available if a flat funding scenario is assumed, which implies an increase of 20% per year, based on the current technology trends.  
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/cpuHLLHC_18.png" alt="cpuHLLHC_18.png" /> <br>
 [[%ATTACHURL%/cpuHLLHC_18.pdf][pdf-file]], [[%ATTACHURL%/cpuHLLHC_18.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
*Superseded by 2020 modelling: see above* Fraction of CPU resources needed in 2028 at the end of Run-4 for different processing workflows.The “MC-Full” section in green is related to the fraction of time spent on the full AtlasG4 simulation and divided in a simulation part “(Sim)” for the Geant4 simulation and a reconstruction part “(Rec)” accounting the time spent reconstructing the events. Similarly, the “MC-Fast” section in red shows this distribution for the time spent running the Fast Calo simulation.  This plot: using fast calo sim for 75% of the Monte Carlo simulation and standard reconstruction.  </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/cpu2028.png" alt="cpu2028.png" /> <br>
 [[%ATTACHURL%/cpu2028.pdf][pdf-file]], [[%ATTACHURL%/cpu2028.png][png-file]] 
 </td> </tr>


<tr>
<td bgcolor="#eeeeee"> 
*Superseded by 2020 modelling: see above* Fraction of CPU resources needed in 2028 at the end of Run-4 for different processing workflows.The “MC-Full” section in green is related to the fraction of time spent on the full AtlasG4 simulation and divided in a simulation part “(Sim)” for the Geant4 simulation and a reconstruction part “(Rec)” accounting the time spent reconstructing the events. Similarly, the “MC-Fast” section in red shows this distribution for the time spent running the Fast Calo simulation.  This plot: using in addition a faster version of reconstruction, which is seeded by the event generator information, and assuming event generation is sped up by a factor of two. 
</td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/cpu2028_fast.png" alt="cpu2028_fast.png" /> <br>
 [[%ATTACHURL%/cpu2028_fast.pdf][pdf-file]], [[%ATTACHURL%/cpu2028_fast.png][png-file]] 
 </td> </tr>


<tr>
<td bgcolor="#eeeeee"> 
OBSOLETE: Estimated total disk resources (in PBytes) needed for the years 2018 to 2028 for both data and simulation processing. The blue points are estimates based on the current event sizes estimates and using the ATLAS computing model parameters from 2017. The solid line shows the amount of resources expected to be available if a flat funding scenario is assumed, which implies an increase of 15% per year, based on the current technology trends.   
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/diskHLLHC.png" alt="diskHLLHC.png" /> <br>
 [[%ATTACHURL%/diskHLLHC.pdf][pdf-file]], [[%ATTACHURL%/diskHLLHC.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
 OBSOLETE: Estimated CPU resources (in kHS06) needed for the years 2018 to 2028 for both data and simulation processing. The blue points are estimates based on the current software performance estimates and using the ATLAS computing model parameters from 2017. The solid line shows the amount of resources expected to be available if a flat funding scenario is assumed, which implies an increase of 20% per year, based on the current technology trends.  
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/cpuHLLHC.png" alt="cpuHLLHC.png" /> <br>
 [[%ATTACHURL%/cpuHLLHC.pdf][pdf-file]], [[%ATTACHURL%/cpuHLLHC.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
The dependency of reconstruction wall time per event on the average number of interactions per bunch crossing (<&#956;>) is shown for the current Inner Detector reconstruction with default tracking cuts. The plot contains a selection of reconstructed luminosity blocks of RAW data from 13 !TeV pp LHC collisions in 2017. An ATLAS luminosity block typically corresponds to one minute of data-taking. Tier-0 reconstruction jobs were required to run in single-core mode on a selected sub-cluster of 16-core machines (with Intel(R) Xeon(R) CPU E5-2630 v3 of 2.40 GHz clock speed, memory of 4 GB/core, 21 HS06/core with HT off). The typical collision runs (blue scatter plot) can be only qualitatively compared with the performance in high-&#956; run 335302 (red boxes), which had special data-taking conditions. Furthermore, the high-&#956; run jobs were configured to produce only AOD outputs, whereas standard jobs proceeded with 12 additional output types (different DRAW, DESD, DAOD and HIST), which takes extra processing time. The behaviour of the tracking reconstruction, which dominates the CPU use at high pileup, for High Luminosity LHC conditions with an upgraded tracking detector has been studied in reference [1].%BR%%BR%
[1] "Technical Design Report for the ATLAS ITk Pixel Detector", ATLAS Collaboration, CERN-LHCC-2017-021, ATLAS-TDR-030, Geneva 2018.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/reco_WtPerEvent_NOfit_revised.png" alt="reco_WtPerEvent_NOfit_revised.png" /> <br>
 [[%ATTACHURL%/reco_WtPerEvent_NOfit_revised.pdf][pdf-file]], [[%ATTACHURL%/reco_WtPerEvent_NOfit_revised.png][png-file]] 
 </td> </tr>


<tr>
<td bgcolor="#eeeeee"> 
Digitization time per event, in HepSpec06 seconds, as a function of the average number of interactions per bunch crossing, with 25 ns bunch spacing. A linear fit to the times is overlaid. On a modern CPU, one second of wall clock time corresponds to about 10 HepSpec06 seconds. </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/cpuVSmu_all.png" alt="icpuVSmu_all.png" /> <br>
 [[%ATTACHURL%/cpuVSmu_all.pdf][pdf-file]], [[%ATTACHURL%/cpuVSmu_all.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
On this figure the total reconstruction time per event is shown for a top Monte Carlo simulation sample with 40 pileup at 13 !TeV, 25 ns bunch spacing. An overall improvement of a factor 3 is visible comparing the 2012 Tier-0 release (17.2.7.9), the release 19.0.3.3 which is optimised for reconstruction of the Run-1 data and the release 19.1.1.1 which is optimised for reconstructing Run-2 data. The CPU time is shown as well separately for the Inner Detector reconstruction as the tracking is dominating the total resource needs. The simulation is done using a Run-1 detector geometry without the IBL. The HS06 scaling factor for the machine used for this study is quoted as 11.95.
This is the updated comparison of the CPU time for reconstructing top pair events with Run-2 pileup in different releases, including the MC15 production release (candidate), showing a speedup factor exceeding 4.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/id_evtloop_cpu_time-CHEP2015.png" alt="id_evtloop_cpu_time-CHEP2015.png" /> <br>
 [[%ATTACHURL%/id_evtloop_cpu_time-CHEP2015.pdf][pdf-file]], [[%ATTACHURL%/id_evtloop_cpu_time-CHEP2015.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Event-wise fractional overlaps between derivations built from the muon stream, run 203875 (2012) using 5000 input events. Each cell of the plot displays the fraction of events accepted in the first format that are also accepted in the second. A higher number indicates that more events are shared between the two formats. Since the different formats contain very different numbers of events, a cell indicating the overlap of format A with format B may not have the same value as its counterpart in the other half of the square representing the overlap of B with A. Also it should be noted that these plots cover only event-wise overlaps: overlaps in variables are not displayed. Hence, it is possible that a pair of formats may be fully correlated in terms of the events selected, but may contain orthogonal sets of variables - in which case no information is shared. Finally, it can clearly be seen that overlaps vary strongly with the trigger stream producing the events.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/muonOverlaps-CHEP2015.png" alt="muonOverlaps-CHEP2015.png" /> <br>
 [[%ATTACHURL%muonOverlaps-CHEP2015.pdf][pdf-file]], [[%ATTACHURL%/muonOverlaps-CHEP2015.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Event-wise fractional overlaps between derivations built from the e-gamma stream, produced from run 203875 (2012) using 5000 input events. Each cell of the plot displays the fraction of events accepted in the first format that are also accepted in the second. A higher number indicates that more events are shared between the two formats. Since the different formats contain very different numbers of events, a cell indicating the overlap of format A with format B may not have the same value as its counterpart in the other half of the square representing the overlap of B with A. Also it should be noted that these plots cover only event-wise overlaps: overlaps in variables are not displayed. Hence, it is possible that a pair of formats may be fully correlated in terms of the events selected, but may contain orthogonal sets of variables - in which case no information is shared. Finally, it can clearly be seen that overlaps vary strongly with the trigger stream producing the events.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/egammaOverlaps-CHEP2015.png" alt="egammaOverlaps-CHEP2015.png" /> <br>
 [[%ATTACHURL%egammaOverlaps-CHEP2015.pdf][pdf-file]], [[%ATTACHURL%/egammaOverlaps-CHEP2015.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Event-wise fractional overlaps between derivations built from the jet stream, run 203875 (2012) using 5000 input events. Each cell of the plot displays the fraction of events accepted in the first format that are also accepted in the second. A higher number indicates that more events are shared between the two formats. Since the different formats contain very different numbers of events, a cell indicating the overlap of format A with format B may not have the same value as its counterpart in the other half of the square representing the overlap of B with A. Also it should be noted that these plots cover only event-wise overlaps: overlaps in variables are not displayed. Hence, it is possible that a pair of formats may be fully correlated in terms of the events selected, but may contain orthogonal sets of variables - in which case no information is shared. Finally, it can clearly be seen that overlaps vary strongly with the trigger stream producing the events.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/jetsOverlaps-CHEP2015.png" alt="jetsOverlaps-CHEP2015.png" /> <br>
 [[%ATTACHURL%jetsOverlaps-CHEP2015.pdf][pdf-file]], [[%ATTACHURL%/jetsOverlaps-CHEP2015.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Memory profile of ATLAS MC digitization and reconstruction jobs comparing total RSS of 8 serial jobs to RSS of one <nop>AthenaMP job with 8 worker processes. Memory savings at the reconstruction step of this particular job are ~45%.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/AthenaMP-vs-Serial-19.1.1.5-pileup-CHEP2015.png" alt="AthenaMP-vs-Serial-19.1.1.5-pileup-CHEP2015.png" /> <br>
 [[%ATTACHURL%AthenaMP-vs-Serial-19.1.1.5-pileup-CHEP2015.pdf][pdf-file]], [[%ATTACHURL%/AthenaMP-vs-Serial-19.1.1.5-pileup-CHEP2015.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
<nop>AthenaMP schematic view </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/Atlas-AthenaMP-Schematic-CHEP2015.png" alt="Atlas-AthenaMP-Schematic-CHEP2015.png" /> <br>
 [[%ATTACHURL%Atlas-AthenaMP-Schematic-CHEP2015.pdf][pdf-file]], [[%ATTACHURL%/Atlas-AthenaMP-Schematic-CHEP2015.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
<nop>Yoda scaling with number of parallel processors (cores). The plot shows how the event throughput of Atlas G4 simulation scales with number of parallel processors (cores) when running within Yoda system on the Edison HPC at NERSC (Berkeley). The scalability is already quite good, although there is certainly a room for improvement and we will be looking into it in the coming months.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/ATLAS-Yoda-Sim-Throughput-CHEP2015.png" alt="ATLAS-Yoda-Sim-Throughput-CHEP2015.png" /> <br>
 [[%ATTACHURL%ATLAS-Yoda-Sim-Throughput-CHEP2015.pdf][pdf-file]], [[%ATTACHURL%/ATLAS-Yoda-Sim-Throughput-CHEP2015.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Size of <nop>DxAOD (derivation) datasets as a fraction of the size of the parent xAOD datasets, evaluated for all derivation types across all runs in period B, for the three physics streams. Each entry in the histogram represents a single derived dataset, with the value being equal to the size of the dataset divided by the size of its parent (input) dataset. There are a total of 65 formats, three streams and more than 100 runs, leading to several thousand individual datasets.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/size-CHEP2015.png" alt="size-CHEP2015.png" /> <br>
 [[%ATTACHURL%size-CHEP2015.pdf][pdf-file]], [[%ATTACHURL%/size-CHEP2015.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Fraction of total input events written into the <nop>DxAOD (derivation) datasets, evaluated for all derivation types across all runs in period B, for the three physics streams. Each entry in the histogram represents a single derived dataset, with the value being equal to the number of selected events in the dataset divided by the number of input events. There are a total of 65 formats, three streams and more than 100 runs, leading to several thousand individual datasets.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/skim-CHEP2015.png" alt="skim-CHEP2015.png" /> <br>
 [[%ATTACHURL%skim-CHEP2015.pdf][pdf-file]], [[%ATTACHURL%/skim-CHEP2015.png][png-file]] 
 </td> </tr>


<tr>
<td bgcolor="#eeeeee"> 
The rate of new data transformations added to the ATLAS production system.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/transformations.png" alt="transformations.png" /> <br>
 [[%ATTACHURL%transformations.pdf][pdf-file]], [[%ATTACHURL%/transformations.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Monthly rate of task requests submitted to the ATLAS production system.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/tasks.png" alt="tasks.png" /> <br>
 [[%ATTACHURL%tasks.pdf][pdf-file]], [[%ATTACHURL%/tasks.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Comparison of monthly rates of task requests in the ATLAS production systems ProdSys1 and ProdSys2.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/comparison.png" alt="comparison.png" /> <br>
 [[%ATTACHURL%comparison.pdf][pdf-file]], [[%ATTACHURL%/comparison.png][png-file]] 
 </td> </tr>


<tr>
<td bgcolor="#eeeeee"> 
Comparison of the energy loss distributions for 1 GeV single muon tracks in the ATLAS Pixel and SCT Detectors for full simulation (based on the Geant4 toolkit) and FATRAS simulation.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/Muon_1GeV_DeltaP_2.png" alt="Muon_1GeV_DeltaP_2.png" /> <br>
 [[%ATTACHURL%Muon_1GeV_DeltaP_2.pdf][pdf-file]], [[%ATTACHURL%/Muon_1GeV_DeltaP_2.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Comparison of the energy loss eta distributions for 1 GeV single muon tracks in the ATLAS Pixel and SCT Detectors for full simulation (based on the Geant4 toolkit) and FATRAS simulation.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/Muon_1GeV_Eta_DeltaEProfile_3.png" alt="Muon_1GeV_Eta_DeltaEProfile_3.png" /> <br>
 [[%ATTACHURL%Muon_1GeV_Eta_DeltaEProfile_3.pdf][pdf-file]], [[%ATTACHURL%/Muon_1GeV_Eta_DeltaEProfile_3.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Comparison of hit distribution of single muon tracks in the ATLAS Pixel and SCT Detectors using FATRAS tracking geometry from GeoModel and from XML configuration file.
 </td>
 <td align="center">
 <img width="300" src="%ATTACHURLPATH%/myplotRZ.png" alt="myplotRZ.png" /> <br>
 [[%ATTACHURL%/myplotRZ.pdf][pdf-file]], [[%ATTACHURL%/myplotRZ.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Energy fraction deposited in the 3rd layer of the Hadronic Endcap calorimeter by charged pions. The black points show the Geant4 inputs, and the result of the longitudinal
energy parametrisation is shown in light blue. A good agreement is observed. The results of a Kolmogorov (KS) and chi2 test are displayed as well.
 </td>
 <td align="center">
<img alt="/FCS_pions_layer10.png" src="%ATTACHURLPATH%/FCS_pions_layer10_prelim.png" width="300" />
 [[%ATTACHURL%/FCS_pions_layer10.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Total cell energy deposited in the calorimeter by photons. The black points show the Geant4 inputs, and the result of the longitudinal energy
parametrisation is shown in light blue. A good agreement is observed. The results of a Kolmogorov (KS) and chi2 test are displayed as well.
 </td>
 <td align="center">
<img alt="/FCS_photons_totalE.png" src="%ATTACHURLPATH%/FCS_photons_totalE_prelim.png" width="300" />
 [[%ATTACHURL%/FCS_photons_totalE.png.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
The ratio of the FastCaloSim energy profile and the reconstructed cells energy profile, as a function of the distance of the centre of the cell and the pion calorimeter entrance position deta(pi,cell), dphi(pi,cell), for the original hit-cell assignment with the simplified geometry. The bias in phi due to the wrong description of the accordion shape of the calorimeter in the simplified geometry is greatly reduced when using the hit displacement method.
 </td>
 <td align="center">
<img src="%ATTACHURLPATH%/Closure_noWiggle.png" alt="Closure_noWiggle.png" width="300" />
 [[%ATTACHURL%/Closure_noWiggle.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
The ratio of the FastCaloSim energy profile and the reconstructed cells energy profile, as a function of the distance of the centre of the cell and the pion calorimeter entrance position deta(pi,cell), dphi(pi,cell), for the modified hit-cell assignment using the wiggle hit displacement method (b). The bias in phi due to the wrong description of the accordion shape of the calorimeter in the simplified geometry is greatly reduced when using the hit displacement method.
 </td>
 <td align="center">
<img src="%ATTACHURLPATH%/Closure_withWiggle.png" alt="Closure_withWiggle.png" width="300" />
 [[%ATTACHURL%/Closure_withWiggle.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Illustration of the energy normalized per bin area used as input to the NN fit. This example is for 50 GeV central (0.20<|eta|<0.25) pions in the EMB1 layer and corresponds to events included in the first bin of the PCA energy parameterisation. 
 </td>
 <td align="center">
<img alt="NNeur4_Lay1_E50000_eta0.20_PID211_reference_polar.png" src="%ATTACHURLPATH%/NNeur4_Lay1_E50000_eta0.20_PID211_reference_polar.png" width="300" />
 [[%ATTACHURL%/NNeur4_Lay1_E50000_eta0.20_PID211_reference_polar.png][png-file]] 
 </td> </tr>

<tr>
<td bgcolor="#eeeeee"> 
Illustration of the output of the NN parametrisation of Fig. 9 input. This example is for 50 GeV central (0.20<|eta|<0.25) pions in the EMB1 layer and corresponds to events included in the first bin of the PCA energy parameterisation. 
 </td>
 <td align="center">
<img alt="NNeur4_Lay1_E50000_eta0.20_PID211_NNoutput_polar.png" src="%ATTACHURLPATH%/NNeur4_Lay1_E50000_eta0.20_PID211_NNoutput_polar.png" width="300" />
 [[%ATTACHURL%/NNeur4_Lay1_E50000_eta0.20_PID211_NNoutput_polar.png][png-file]] 
 </td> </tr>


</table>





<!-- *********************************************************** --> <!-- Do NOT remove the remaining lines, but add requested info as appropriate--> <!-- *********************************************************** -->

---

<!-- For significant updates to the topic, consider adding your 'signature' (beneath this editing box) --> *Major updates*:%BR% -- 
<!-- Person responsible for the page: 
Either leave as is - the creator's name will be inserted; 
Or replace the complete REVINFO tag (including percentages symbols) with a name in the form Main.TwikiUsersName --> 
<!-- %RESPONSIBLE% %REVINFO{"$wikiusername" rev="1.2"}% %BR% -->
%SUBJECT% %BR% <!-- Once this page has been reviewed, please add the name and the date e.g. Main.StephenHaywood - 31 Oct 2006 -->

%STOPINCLUDE%
Topic revision: r17 - 2020-11-17 - ZacharyMarshall
Account
- Log In
- Cern Search
- TWiki Search
- Google Search
Atlas All webs
Edit
Attach
Copyright &© 2008-2021 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