From e4d93ffbb43630705dffbd2eca1158131590c832 Mon Sep 17 00:00:00 2001 From: Federico Stagni Date: Mon, 7 Oct 2024 12:58:36 +0200 Subject: [PATCH] fix size --- slides.md | 36 +++++++++++++++++++++++++----------- 1 file changed, 25 insertions(+), 11 deletions(-) diff --git a/slides.md b/slides.md index 68d2ab5..937f5f9 100644 --- a/slides.md +++ b/slides.md @@ -601,17 +601,31 @@ title: Extensions Dirac has to support different Communities with different workflows and requirements. Examples: -- LHCb is a HEP experiment. Stores the metadata and provenance of every produced files in a LHCb-specific database (with an Oracle backend) - - --> [see talk in Track 3 on Monday](https://indico.cern.ch/event/1338689/contributions/6010069/) - - --> See also poster #461 on `LbMCSubmit` tool -- Belle2 is a HEP experiment. Uses Rucio as data management solution. - - --> [see talk in Track 1 this afternoon](https://indico.cern.ch/event/1338689/contributions/6010888/) -- CTAO is an Astrophysics experiment with radically different requirements (wrt to HEP exp.) on how to process its data - - --> [see talk in Track 4 tomorrow](https://indico.cern.ch/event/1338689/contributions/6011028/) -- HERD is astronomy and particle astrophysics experiment using dHTC for data managemnt - - --> [see talk in Track 4 tomorrow](https://indico.cern.ch/event/1338689/contributions/6011011/) -- EGI use DIRAC as WMS, and EGI-CheckIn as indentity provider -- WeNMR brings together complementary research teams in the structural biology and life science area + It is sometimes necessary to extend all Dirac(X) components (including Web and Pilot). DiracX aims to provide an easy way to do so.