1 / 10

New HEP Communities: AMS , Dampe and Virgo

This presentation discusses the participation of AMS, DAMPE, and Virgo in high energy physics research, their data flow and computing workflows, and proposed architecture solutions to address their computing needs.

crobin
Télécharger la présentation

New HEP Communities: AMS , Dampe and Virgo

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. New HEP Communities:AMS, Dampe and Virgo Presented by Daniele Spiga Daniele.Spiga@pg.infn.it INDIGO SUMMIT EGI-INDIGO workshop on community application support Catania, 09thMay 2017 RIA-653549

  2. New High Energy Physics communities VIRGO: • Participates to the international network of gravitational wave (GW) interferometers that detected in September 2015 the GW signal emitted by the coalescence of two black holes • Several and different analysis pipelines are running in several computing centers world wide distributed • Pipelines looking for different GW signals are based on different workflow managers • HTCondor, CREAM-CE, GlideIN • Cloud computing is currently not used for massive analysis AMS: Focus on next slides The AMS-02 detector on the ISS DAMPE: • A astroparticle physics experiment, installed on board the DAMPE Chinese satellite • Direct measurement of charged cosmic rays (protons, ions, electron) and photon in an energy range from GeV to several TeV in low earth orbit. New HEP Communities: AMS, DAMPE & Virgo

  3. Alpha Magnetic Spectrometer – AMS-02 Objectives • Fundamental physics and antimatter: • primordial origin (signal: anti-nuclei) • “exotic” sources(signal: positrons, anti-p, anti-D, g) • Origin and composition of CRs • sources and acceleration: primaries (p, He, C, ...) • propagation in the ISM: secondaries(B/C, ...) • Study of the solar and geomagnetical physics • effect of the solar modulation • geomagnetic cutoff New HEP Communities: AMS, DAMPE & Virgo

  4. AMS Data Flow: few numbers • Data collected by AMS (~ 35 TB/year) are transmitted from the International Space Station, through the NASA infrastructure, to CERN • Copied at INFN-CNAF (master copy on tape) • Reconstruction step, called std, produces ~ 100 TB/year • About a reconstruction step/year due to improved condition (which in turn is due to improved detector understanding) • Last reprocessing required > 400 CPU-Years, to process > 5 years of AMS data taking • Data reconstruction performed on regional centers distributed among: Europe, China and USA • workflow is adapted, by hand, to the various regional centers • job submission is managed by the LSF or PBS batch systems New HEP Communities: AMS, DAMPE & Virgo

  5. AMS computing workflows: more numbers • Analysis groups skim reconstructed data producing ntuples • Typically a production step takes ~10 CPU-years • Performed several times per year • AMS scientists generate also huge amount of Monte Carlo datasets • In 2015 AMS used ~8000 CPU-years, in 2016 ~11000 • Expectation is that these numbers will increase • as the detector understanding is improving, newer and updated MC productions are required • Statistics must follow the increased statistics of the real data New HEP Communities: AMS, DAMPE & Virgo

  6. Considerations • All this appears to be a limiting factor in the scope of the data analyst daily work • it does not result trivial to exploit modern computing infrastructures such as cloud IaaS • AMS computing model has not been originally designed to cope with the cloud computing paradigm • AMS software environment is not highly portable • Cost for deploying AMS environment on “new” resources is too high • Setting-up environment requires huge effort wrt obtained gain New HEP Communities: AMS, DAMPE & Virgo

  7. AMS - User Stories • As a AMS analyst I need to access a batch system • As analyst I continuously update my code • User libraries • As AMS analyst I can access cloud IaaS providers • As responsible for ntuple production I need access to remote data • read and write • As responsible for ntuple production I need to share produced outputs within analysis group New HEP Communities: AMS, DAMPE & Virgo

  8. Architecture Proposal • AMS Requirements mostly match solutions provided by CMS Analysis Cluster On-Demand. Remote Storage INDIGO PaaS Orchestrator Data Cache/Local Storage TOSCA template Batch System INFN-CNAF Collector Remote Storage Negotiator Schedd Startd AuthN IAM CERN Extensions of CMS use case New HEP Communities: AMS, DAMPE & Virgo

  9. What’s Next The integration of these communities, and the needed development will be implemented in the scope of a INFRA12 Thematic Service, if funded. New HEP Communities: AMS, DAMPE & Virgo

  10. We are ready to share our experience! https://www.indigo-datacloud.eu Better Software for Better Science.

More Related