Skip to main content

Delivering Agile Research Excellence on European e-Infrastructures

Deliverables

D7.3 Pilot Tools and Services, Execution and Evaluation Report I

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.

D6.4 Pilot Tools and Services, Execution and Evaluation Report II

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.

D7.4 Pilot Tools and Services, Execution and Evaluation Report II

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.

D5.2 Platform Infrastructure and Usage and Deployment II

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.

D8.6 Sustainability, Exploitation and Commercialisation Plan

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.

D8.5 Training and Consulting Report II

A report documenting the various training activities and events for the respective period. INGV will be responsible for delivery.

D8.2 Dissemination and Outreach Report I

A report documenting the various dissemination, awareness and outreach activities and results for the respective period. GRNET will be responsible for delivery.

D2.2 DARE Architecture and Technical Positioning II

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.

D5.3 Operational Requirements and Guidelines I

A set of guidelines and good practices for managing and maintaining a DARE platform deployment. GRNET will be responsible for delivery.

D5.4 Operational Requirements and Guidelines II

A set of guidelines and good practices for managing and maintaining a DARE platform deployment. GRNET will be responsible for delivery.

D2.1 DARE Architecture and Technical Positioning I

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.

D8.4 Training and Consulting Report I

A report documenting the various training activities and events for the respective period. INGV will be responsible for delivery.

D6.1 Requirements and Test Cases I

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

D7.2 Requirements and Test Cases II

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.

D6.2 Requirements and Test Cases II

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

D7.1 Requirements and Test Cases I

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.

D6.3 Pilot Tools and Services, Execution and Evaluation Report I

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.

D8.3 Dissemination and Outreach Report II

A report documenting the various dissemination, awareness and outreach activities and results for the respective period. GRNET will be responsible for delivery.

D3.1 Decomposed User Stories I

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.

D5.1 Platform Infrastructure and Usage and Deployment I

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.

D3.2 Decomposed User Stories II

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.

D4.5 Data Consolidation and Linking Toolkit I

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.

D4.6 Data Consolidation and Linking Toolkit II

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.

D4.3 Data-driven Abstraction Specification and Execution Mapping Services Toolkit I

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.

D4.2 Big Data Analytics Toolkit II

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.

D3.6 DARE API II

Implementation of the DARE software API, ready to be introduced in the integrated DARE software stack. NCSR-D will be responsible for delivery.

D3.7 Integrated Monitoring and Management Tools I

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.

D4.8 Integrated Software Stack and Semantic Registry II

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.

D3.5 DARE API I

Implementation of the DARE software API, ready to be introduced in the integrated DARE software stack. NCSR-D will be responsible for delivery.

D4.1 Big Data Analytics Toolkit I

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.

D3.4 Data Lineage Services II

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

D3.3 Data Lineage Services I

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.

D4.4 Data-driven Abstraction Specification and Execution Mapping Services Toolkit II

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.

D3.8 Integrated Monitoring and Management Tools II

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.

D4.7 Integrated Software Stack and Semantic Registry I

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.

D2.6 Data Management Plan II

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.

D2.5 Data Management Plan I

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.

D8.1 DARE Online Presence Setup and Management

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

Comprehensible Control for Researchers and Developers Facing Data Challenges

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
DOI: 10.1109/escience.2019.00042

DARE: A Reflective Platform Designed to Enable Agile Data-Driven Research on the Cloud

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
DOI: 10.1109/escience.2019.00079

Ease Access to Climate Simulations for Researchers: IS-ENES Climate4Impact

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
DOI: 10.1109/escience.2019.00080

DARE to Deliver Research Agility on Cloud E-Infrarstructures

Author(s): Klampanos, Iraklis; Atkinson, Malcolm; Pagé, Christian; Koukourikos, Antonis; Magnoni, Federica; Rietbrock, Andreas; Karkaletsis, Vangelis
Published in: 2018
DOI: 10.5281/zenodo.2531467

Leveraging and Easing End Users' Climate Data Access by Interfacing Infrastructures

Author(s): Pagé, Christian; Som de Cerff, Wim; Spinuso, Alessandro; Plieger, Maarten; Klampanos, Iraklis; Atkinson, Malcolm; Karkaletsis, Vangelis
Published in: Issue 3, 2018
DOI: 10.1002/essoar.10500166.1

Improving Climate Data Access through integration of the DARE Platform, the ENES CDI and EUDAT B2 Services

Author(s): Christian Page; Xavier Pivan; Alessandro Spinuso; Wim Som de Cerff; Maarten Plieger
Published in: Issue 3, 2018
DOI: 10.13140/RG.2.2.21787.31520

EPOS-IP and DARE use case: the VERCE platform for a widely accessible forward and inverse seismic modelling

Author(s): Rafiq Saleh; Alessandro Spinuso; Andre Gemuend; Emanuele Casarotti
Published in: EGU General Assembly 2018, Geophysical Research Abstracts, Issue 3, 2018
DOI: 10.5281/zenodo.3381547

Using the EGI FedCloud and the ESGF CWT-API in a WPS workflow to provide data analysis computations for the IS-ENES climate4impact platform

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,,, Issue 1, 2018
DOI: 10.5281/zenodo.3381543

Forward and Inverse Seismic Modelling Science Gateway ( a provenance-powered solution )

Author(s): Alessandro Spinuso; Andre Gemünd; Rafiq Saleh; Federica Magnoni
Published in: Issue 2, 2018
DOI: 10.5281/zenodo.3381534

Active Provenance for Data-Intensive Workflows: Engaging Users and Developers

Author(s): Alessandro Spinuso, Malcolm Atkinson, Federica Magnoni
Published in: 2019 15th International Conference on eScience (eScience), 2019, Page(s) 560-569
DOI: 10.1109/escience.2019.00077

Towards a Computer-Interpretable Actionable Formal Model to Encode Data Governance Rules

Author(s): Rui Zhao, Malcolm Atkinson
Published in: 2019 15th International Conference on eScience (eScience), 2019, Page(s) 594-603
DOI: 10.1109/escience.2019.00082

DARE Platform: a Developer-Friendly and Self-Optimising Workflows-as-a-Service Framework for e-Science on the Cloud

Author(s): Iraklis Klampanos, Chrysoula Themeli, Alessandro Spinuso, Rosa Filgueira, Malcolm Atkinson, André Gemünd, Vangelis Karkaletsis
Published in: Journal of Open Source Software, Issue 5/54, 2020, Page(s) 2664, ISSN 2475-9066
DOI: 10.21105/joss.02664

Establishing Core Concepts for Information-Powered Collaborations

Author(s): Luca Trani, Malcolm Atkinson, Daniele Bailo, Rossana Paciello, Rosa Filgueira
Published in: Future Generation Computer Systems, Issue 89, 2018, Page(s) 421-437, ISSN 0167-739X
DOI: 10.1016/j.future.2018.07.005