In order to enable an iCal export link, your account needs to have an API key created. This key enables other applications to access data from within Indico even when you are neither using nor logged into the Indico system yourself with the link provided. Once created, you can manage your key at any time by going to 'My Profile' and looking under the tab entitled 'HTTP API'. Further information about HTTP API keys can be found in the Indico documentation.

I have read and understood the above.

Additionally to having an API key associated with your account, exporting private event information requires the usage of a persistent signature. This enables API URLs which do not expire after a few minutes so while the setting is active, anyone in possession of the link provided can access the information. Due to this, it is extremely important that you keep these links private and for your use only. If you think someone else may have acquired access to a link using this key in the future, you must immediately create a new key pair on the 'My Profile' page under the 'HTTP API' and update the iCalendar links afterwards.

Modernizing the ATLAS Simulation Infrastructure

In order to enable an iCal export link, your account needs to have an API key created. This key enables other applications to access data from within Indico even when you are neither using nor logged into the Indico system yourself with the link provided. Once created, you can manage your key at any time by going to 'My Profile' and looking under the tab entitled 'HTTP API'. Further information about HTTP API keys can be found in the Indico documentation.

I have read and understood the above.

Additionally to having an API key associated with your account, exporting private event information requires the usage of a persistent signature. This enables API URLs which do not expire after a few minutes so while the setting is active, anyone in possession of the link provided can access the information. Due to this, it is extremely important that you keep these links private and for your use only. If you think someone else may have acquired access to a link using this key in the future, you must immediately create a new key pair on the 'My Profile' page under the 'HTTP API' and update the iCalendar links afterwards.

I have read and understood the above.

Permanent link for public information only:

Permanent link for all public and protected information:

Please use CTRL + C to copy this URL

11 Oct 2016, 14:15

15m

GG C1 (San Francisco Mariott Marquis)

GG C1

San Francisco Mariott Marquis

Speaker

Andrea Di Simone
(Albert-Ludwigs-Universitaet Freiburg (DE))

Description

The ATLAS Simulation infrastructure has been used to produce upwards of 50 billion proton-proton collision events for analyses
ranging from detailed Standard Model measurements to searches for exotic new phenomena. In the last several years, the
infrastructure has been heavily revised to allow intuitive multithreading and significantly improved maintainability. Such a
massive update of a legacy code base requires careful choices about what pieces of code to completely rewrite and what to wrap or
revise. The initialization of the complex geometry was generalized to allow new tools and geometry description languages, popular
in some detector groups. The addition of multithreading requires Geant4 MT and GaudiHive, two frameworks with fundamentally
different approaches to multithreading, to work together. It also required enforcing thread safety throughout a large code base,
which required the redesign of several aspects of the simulation, including “truth,” the record of particle interactions with the
detector during the simulation. These advances were possible thanks to close interactions with the Geant4 developers.