Deliverables
A report detailing the set of DARE components activated for the use case, their configuration parameters and possible customization steps (if needed).It will also report on pilot execution benchmarks to assess the usability and performance of the pilot. At early stage the pilot prototype will be evaluated and results will feed in the next stages. CERFACS will be responsible for delivery.
A report detailing the set of DARE components activated for the use case, their configuration parame-ters and possible customization steps (if needed). The deliverables will also report on the stages of execution of the EPOS Use Case Pilot accounting for technical and operational issues and assessing the scalability and performance of the Pilot. They will also contain the results of the evaluation phases aimed at quantifying and testing the development of the Pilot and the related services in the framework of the DARE platform. INGV will be responsible for delivery.
A report detailing the set of DARE components activated for the use case, their configuration parameters and possible customization steps (if needed).It will also report on pilot execution benchmarks to assess the usability and performance of the pilot. At early stage the pilot prototype will be evaluated and results will feed in the next stages. CERFACS will be responsible for delivery.
A report on the computational resources mobilised to serve the DARE platform deployment, along with usage statistics for the reporting period. It will also provide details on the adopted approach for deploying the DARE platform and the associated components, indicating the processes for transferring assessed development versions to the installation publicly available. FRAUNHOFER will be responsible for delivery.
A report describing the sustainability outcomes and strategy of the project for the uptake and maintenance of the DARE solution and its individual parts. It will also document possible markets, specifying the positioning of DARE within these markets and indicating possible means of commercializing and monetizing services over the hyper-platform. GRNET will be responsible for delivery.
A report documenting the various training activities and events for the respective period. INGV will be responsible for delivery.
A report documenting the various dissemination, awareness and outreach activities and results for the respective period. GRNET will be responsible for delivery.
Iterative refinements of the DARE architecture, providing the rationale for the design choices and showcasing its association with the expressed user requirements. It will also indicate current developments in approaches and technologies relevant to the functionality and audience of the platform, and highlighting the required steps for keeping the platform up-to-date with these developments. UEDIN will be responsible for preparing the deliverable.
A set of guidelines and good practices for managing and maintaining a DARE platform deployment. GRNET will be responsible for delivery.
A set of guidelines and good practices for managing and maintaining a DARE platform deployment. GRNET will be responsible for delivery.
Iterative refinements of the DARE architecture, providing the rationale for the design choices and showcasing its association with the expressed user requirements. It will also indicate current developments in approaches and technologies relevant to the functionality and audience of the platform, and highlighting the required steps for keeping the platform up-to-date with these developments. UEDIN will be responsible for preparing the deliverable.
A report documenting the various training activities and events for the respective period. INGV will be responsible for delivery.
The deliverables will describe the progresses in the definition and prioritisation of the requirements of specific Test Cases. They will also report on the achievement of the Test Cases’ needs based on the exploitation of the DARE platform. The deliverables will then account for later enrichment/design of the Test Cases based on evolving needs of the involved user communities. KIT will be responsible for delivery
This deliverable will report on the identification, assessment and prioritisation requirements based on specific Test Cases and the targeted users. It will take into account the needs based on the current and envisioned RIs and e-infra European Landscape offering. Those requirements will be adjusted in later phases by taking into account the related DARE Tools and Services. CERFACS will be responsible for delivery.
The deliverables will describe the progresses in the definition and prioritisation of the requirements of specific Test Cases. They will also report on the achievement of the Test Cases’ needs based on the exploitation of the DARE platform. The deliverables will then account for later enrichment/design of the Test Cases based on evolving needs of the involved user communities. KIT will be responsible for delivery
This deliverable will report on the identification, assessment and prioritisation requirements based on specific Test Cases and the targeted users. It will take into account the needs based on the current and envisioned RIs and e-infra European Landscape offering. Those requirements will be adjusted in later phases by taking into account the related DARE Tools and Services. CERFACS will be responsible for delivery.
A report detailing the set of DARE components activated for the use case, their configuration parame-ters and possible customization steps (if needed). The deliverables will also report on the stages of execution of the EPOS Use Case Pilot accounting for technical and operational issues and assessing the scalability and performance of the Pilot. They will also contain the results of the evaluation phases aimed at quantifying and testing the development of the Pilot and the related services in the framework of the DARE platform. INGV will be responsible for delivery.
A report documenting the various dissemination, awareness and outreach activities and results for the respective period. GRNET will be responsible for delivery.
A report providing the mapping of the user stories to the technical needs and corresponding assets that are required to properly and effectively carry them out. UEDIN will be responsible for delivery.
A report on the computational resources mobilised to serve the DARE platform deployment, along with usage statistics for the reporting period. It will also provide details on the adopted approach for deploying the DARE platform and the associated components, indicating the processes for transferring assessed development versions to the installation publicly available. FRAUNHOFER will be responsible for delivery.
A report providing the mapping of the user stories to the technical needs and corresponding assets that are required to properly and effectively carry them out. UEDIN will be responsible for delivery.
Code base and software packages of the tools and services responsible for harmonizing and connecting large, varying datasets. This toolkit will be based on extensions and integration of the Semagrow and Exareme systems and will allow DARE to interact with a multitude of external databases and registries. ATHENA will be responsible for delivery.
Code base and software packages of the tools and services responsible for harmonizing and connecting large, varying datasets. This toolkit will be based on extensions and integration of the Semagrow and Exareme systems and will allow DARE to interact with a multitude of external databases and registries. ATHENA will be responsible for delivery.
The data-driven abstraction specification DARE software components, produced by the extension and improvement of dis-pel4py. These components will allow for the context-agnostic, abstract specifications of methods addressing data, computing and complexity extremes. The set of execution mappings services, progressively enriched and refined throughout the DARE development cycles. These map-pings will be extended to include the orchestration of Semagrow and Exareme calls, as well as they will allow for the automated assignment of parts of methods to different infrastructures by making use of knowledge and semantics gathered during earlier tests and runs. UEDIN will be responsible for delivery.
The set of DARE services and components that will form the base layer of the DARE solution, responsible for carrying out the data management and analytics functionality required now and in the mid-term future – based on the BDE platform. NCSR-D will be responsible for delivery.
Implementation of the DARE software API, ready to be introduced in the integrated DARE software stack. NCSR-D will be responsible for delivery.
The set of external tools to be incorporated in the DARE solution, with the necessary changes/extensions. The toolkit will be accompanied by a report summarising the DARE-specific modifica-ions on the tools, along with integration and usage guidelines. KNMI will be responsible for delivery.
The full set of DARE components and services, forming the official DARE platform releases. These will be in the form of openly accessible code and documentation, bundled in configurable and deploy-able software package. NCSRD will be responsible for delivery.
Implementation of the DARE software API, ready to be introduced in the integrated DARE software stack. NCSR-D will be responsible for delivery.
The set of DARE services and components that will form the base layer of the DARE solution, responsible for carrying out the data management and analytics functionality required now and in the mid-term future – based on the BDE platform. NCSR-D will be responsible for delivery.
The set of services used for managing the data-lineage information produced by the applications developed with the DARE technology. KNMI will be responsible for delivery
The set of services used for managing the data-lineage information produced by the applications developed with the DARE technology. KNMI will be responsible for delivery.
The data-driven abstraction specification DARE software components, produced by the extension and improvement of dis-pel4py. These components will allow for the context-agnostic, abstract specifications of methods addressing data, computing and complexity extremes. The set of execution mappings services, progressively enriched and refined throughout the DARE development cycles. These map-pings will be extended to include the orchestration of Semagrow and Exareme calls, as well as they will allow for the automated assignment of parts of methods to different infrastructures by making use of knowledge and semantics gathered during earlier tests and runs. UEDIN will be responsible for delivery.
The set of external tools to be incorporated in the DARE solution, with the necessary changes/extensions. The toolkit will be accompanied by a report summarising the DARE-specific modifications on the tools, along with integration and usage guidelines. KNMI will be responsible for delivery.
The full set of DARE components and services, forming the official DARE platform releases. These will be in the form of openly accessible code and documentation, bundled in configurable and deploy-able software package. NCSRD will be responsible for delivery.
A report that will outline how data will be collected, processed or generated and following what methodology and standards, whether and how this data will be shared and/or made open, and how it will be curated and preserved. NCSR-D will be responsible for the deliverable.
A report that will outline how data will be collected, processed or generated and following what methodology and standards, whether and how this data will be shared and/or made open, and how it will be curated and preserved. NCSR-D will be responsible for the deliverable.
Setup and maintenance plan for the project’s web site, social media accounts, blogs, forums, etc. NCSRD will be responsible for delivery.
Searching for OpenAIRE data...
Publications
Author(s): Maarten Plieger; Wim Som de Cerff; Xavier Pivan; Alessandro Spinuso; Christian Page
Published in: eScience, 5, 2019
Publisher: eScience 2019
DOI: 10.17605/osf.io/wkm93
Author(s): , Rosa
Published in: 4, 2019
Publisher: eScience Conference 2019
DOI: 10.5281/zenodo.3357805
Author(s): Christian Page, Wim Som De Cerff, Maarten Plieger, Alessandro Spinuso, Iraklis Angelos Klampanos, Malcolm Atkinson and Vangelis Karkaletsis
Published in: 2020
Publisher: EGU General Assembly 2020
DOI: 10.5194/egusphere-egu2020-4658
Author(s): Pagé, Christian; Plieger, Maarten; Som De Cerff, Wim; De Vreede, Ernst; Drost, Niels; Klampanos, Iraklis Angelos; Karkaletsis, Vangelis; Atkinson, Malcolm; Pivan, Xavier
Published in: 6, 2019
Publisher: Science Gateways 2019
DOI: 10.17605/osf.io/t8y3h
Author(s): Malcolm Atkinson, Rosa Filgueira, Iraklis Klampanos, Antonis Koukourikos, Amrey Krause, Federica Magnoni, Christian Page, Andreas Rietbrock, Alessandro Spinuso
Published in: 2019 15th International Conference on eScience (eScience), 2019, Page(s) 311-320, ISBN 978-1-7281-2451-3
Publisher: IEEE
DOI: 10.1109/escience.2019.00042
Author(s): Iraklis Klampanos, Athanasios Davvetas, Andre Gemund, Malcolm Atkinson, Antonios Koukourikos, Rosa Filgueira, Amrey Krause, Alessandro Spinuso, Angelos Charalambidis, Federica Magnoni, Emanuele Casarotti, Christian Page, Mike Lindner, Andreas Ikonomopoulos, Vangelis Karkaletsis
Published in: 2019 15th International Conference on eScience (eScience), 2019, Page(s) 578-585, ISBN 978-1-7281-2451-3
Publisher: IEEE
DOI: 10.1109/escience.2019.00079
Author(s): Federica Magnoni; Emanuele Casarotti; Pietro Artale Harris; Mike Lindner,; Andreas Rietbrock; Iraklis Angelos Klampanos; Athanasios Davvetas; Alessandro Spinuso; Rosa Filgueira; Amy Krause; Malcolm Atkinson; André Gemund; Vangelis Karkaletsis
Published in: 2, 2019
Publisher: AGU Fall Meeting
DOI: 10.5281/zenodo.4396310
Author(s): Christian Page, Wim Som de Cerff, Maarten Plieger, Alessandro Spinuso, Xavier Pivan
Published in: 2019 15th International Conference on eScience (eScience), 2019, Page(s) 586-587, ISBN 978-1-7281-2451-3
Publisher: IEEE
DOI: 10.1109/escience.2019.00080
Author(s): Klampanos, Iraklis; Atkinson, Malcolm; Pagé, Christian; Koukourikos, Antonis; Magnoni, Federica; Rietbrock, Andreas; Karkaletsis, Vangelis
Published in: 2018
Publisher: AGU Fall Meeting 2018
DOI: 10.5281/zenodo.2531467
Author(s): Pagé, Christian; Som de Cerff, Wim; Spinuso, Alessandro; Plieger, Maarten; Klampanos, Iraklis; Atkinson, Malcolm; Karkaletsis, Vangelis
Published in: 3, 2018
Publisher: AGU 2018 Fall Meeting
DOI: 10.1002/essoar.10500166.1
Author(s): Christian Page; Xavier Pivan; Alessandro Spinuso; Wim Som de Cerff; Maarten Plieger
Published in: 3, 2018
Publisher: IWSG 2018 Conference
DOI: 10.13140/RG.2.2.21787.31520
Author(s): Rafiq Saleh; Alessandro Spinuso; Andre Gemuend; Emanuele Casarotti
Published in: EGU General Assembly 2018, Geophysical Research Abstracts, 3, 2018
Publisher: EGU2018
DOI: 10.5281/zenodo.3381547
Author(s): Christian Pagé; Xavier Pivan; Asela Rajapakse; Wim Som de Cerff
Published in: Christian Pagé, Xavier Pivan, Asela Rajapakse, Wim Som de Cerff, Maarten Plieger, Ernst de Vreede, Alessandro Spinuso, Lars Bärring, Antonio Cofiño, Alessandro d’Anca, and Sandro Fiore, E Vol. 20, EGU2018-12280-1,,, 1, 2018
Publisher: GU General Assembly 2018, Geophysical Research Abstracts
DOI: 10.5281/zenodo.3381543
Author(s): Alessandro Spinuso; Andre Gemünd; Rafiq Saleh; Federica Magnoni
Published in: 2, 2018
Publisher: 10th International Workshop on Science Gateways (IWSG 2018)
DOI: 10.5281/zenodo.3381534
Author(s): Liang Liang; Rosa Filgueira; Yan Yan
Published in: 2, 2020
Publisher: WORKS 2020
DOI: 10.5281/zenodo.4396296
Author(s): Page, Christian; Som de Cerff, Wim; Plieger, Maarten; Spinuso, Alessandro; de Vreede, Ernst; Drost, Niels
Published in: Crossref, 4, 2019
Publisher: AGU Fall Meeting
DOI: 10.1002/essoar.10501325.1
Author(s): Alessandro Spinuso, Malcolm Atkinson, Federica Magnoni
Published in: 2019 15th International Conference on eScience (eScience), 2019, Page(s) 560-569, ISBN 978-1-7281-2451-3
Publisher: IEEE eScience 2019
DOI: 10.1109/escience.2019.00077
Author(s): Rui Zhao, Malcolm Atkinson
Published in: 2019 15th International Conference on eScience (eScience), 2019, Page(s) 594-603, ISBN 978-1-7281-2451-3
Publisher: IEEE
DOI: 10.1109/escience.2019.00082
Author(s): Pagé, Christian; Plieger, Maarten; Som de Cerff, Wim; Spinuso, Alessandro; Filgueira, Rosa; Atkinson, Malcolm; Themeli, Sissy; Klampanos, Iraklis; Karkaletsis, Vangelis
Published in: 2, 2020
Publisher: AGU 2020 Fall Meeting
DOI: 10.1002/essoar.10505229.1
Author(s): Iraklis Klampanos, Chrysoula Themeli, Alessandro Spinuso, Rosa Filgueira, Malcolm Atkinson, André Gemünd, Vangelis Karkaletsis
Published in: Journal of Open Source Software, 5/54, 2020, Page(s) 2664, ISSN 2475-9066
Publisher: Journal of Open Source Software
DOI: 10.21105/joss.02664
Author(s): Luca Trani, Malcolm Atkinson, Daniele Bailo, Rossana Paciello, Rosa Filgueira
Published in: Future Generation Computer Systems, 89, 2018, Page(s) 421-437, ISSN 0167-739X
Publisher: Elsevier BV
DOI: 10.1016/j.future.2018.07.005