Deliverables
A prototype compiler that translates the API of Deliverables D3.1 and D3.2 to the interface offered by the runtime system of Deliverable D4.1
Defines the guidelines, tools and procedures for integrating the AllScale environment and all pilot applications (outcome of T6.3).
Describes the different evaluation criteria and the results of the validation activities performed for every pilot application (outcome of Task 6.4) on the AllScale computing infrastructure.
A C++ implementation of the AllScale API comprising the Core and User API, being compatible to state-of-the-art C++ compilers.
A first proto-type of the runtime system implementing the interface defined by Deliverable D4.1 providing a unified scheduling interface and an implementation of it focusing on high resource utilisation within shared memory systems.
An extended version of Deliverable D3.3 adding automated porting support targeting (i) distributed memory systems and (ii) accelerators as well as (iii) facilities creating and restoring local checkpoints.
A C++ implementation of the AllScale API comprising the Core and User API, being compatible to state-of-the-art C++ compilers.
Defines the guidelines, tools and procedures for integrating the AllScale environment and all pilot applications (outcome of T6.3).
An implementation and evaluation of the resilience techniques identified by Deliverable D5.1 utilising the AllScale API in the context of the pilot application.
Describes the incremental preparation, deployment and validation of the AMDADOS pilot application.
This Deliverable explores and utilises the capabilities of the other deliverables to research strategies to effectively steer applications towards fulfilling customisable trade-offs among (conflicting) objectives.
This deliverable describes the incremental preparation, deployment and validation of the iPIC3D pilot application.
This deliverable will specify the AllScale Core and User API as well as their intended usage within the pilot applications (compare with Deliverable D3.1 covering its actual implementation)
An infrastructure for collecting and aggregating monitoring information within the runtime system.
This deliverable will specify the AllScale Core and User API as well as their intended usage within the pilot applications (compare with Deliverables D3.1 and 3.2 covering its actual implementation)
This deliverable will contain an analysis of the main elements of the data management policy used by the applicants with regard to all data sets generated by the project. This will include a data set reference, name, description, standards, metadata, and management principles such as sharing, archiving and preservation.
Integration of the IPM tool with the HPX framework to develop an infrastructure for collecting, aggregating and querying (abstract) monitoring information effectively throughout connected runtime system instances.
An extended version of Deliverable D4.2 providing resource management support and an adapted scheduler targeting minimal energy usage.
This deliverable describes the characteristics of the AllScale computing infrastructure for the three pilot applications (outcome of Task T6.1).
This deliverable will provide a document with the specification of the API to be used to interact with the runtime system as well as an implementation of the API itself.
This deliverable will describe the detailed software architecture of the AllScale environment comprising all components, their interfaces and responsibilities.
This deliverable will provide information about the project dissemination plans including the specification of the target dissemination groups, publication policy, event planning and marketing. AllScale will exploit popular web 2.0 channels and social media for further enhancing the project image. It is an ongoing deliverable with subsequent updated versions throughout the project lifetime.
Describes the incremental preparation, deployment and validation of the AMDADOS pilot application.
An implementation and evaluation of the resilience techniques identified by Deliverable D5.1 utilising the AllScale API in the context of the pilot application.
An infrastructure for collecting and aggregating monitoring information within the runtime system.
This deliverable will describe the detailed software architecture of the AllScale environment comprising all components, their interfaces and responsibilities.
An extended version of Deliverable D4.2 providing data management support and an adapted scheduler targeting high resource utilisation within distributed memory systems.
This deliverable describes the incremental preparation, deployment and validation of the iPIC3D pilot application.
This deliverable will provide information about the project dissemination plans including the specification of the target dissemination groups, publication policy, event planning and marketing. AllScale will exploit popular web 2.0 channels and social media for further enhancing the project image. It is an ongoing deliverable with subsequent updated versions throughout the project lifetime.
An API implementation for saving and restoring (local) recovery information and associated cost models and their documentation.
This Deliverable explores and utilises the capabilities of the other deliverables to research strategies to effectively steer applications towards fulfilling customisable trade-offs among (conflicting) objectives.
This deliverable will provide information about additional AllScale dissemination materials to be produced in the project, such as project leaflets, posters, newsletters, calendar of events, etc. It will also include other dissemination support materials are required to give higher impact to the project as it progresses.
This deliverable will describe requirements of the project with respect to the pilot applications and project objectives and specify benchmarks for performance eval-uations. Furthermore, it will identify external technological developments potentially influencing the project objectives and requirements.
This deliverable will contain an analysis of the main elements of the data management policy used by the applicants with regard to all data sets generated by the project. This will include a data set reference, name, description, standards, metadata, and management principles such as sharing, archiving and preservation.
This report will describe the overall achievements of the project.
A component identifying failures, estimating failure compensation costs and advising preparation and recovery operations to the runtime system scheduler. The deliverable will outline those techniques and provide an evaluation of those in the context of the AllScale pilot applications.
This deliverable will describe requirements of the project with respect to the pilot applications and project objectives and specify benchmarks for performance evaluations. Furthermore, it will identify external technological developments potentially influencing the project objectives and requirements.
A comprehensive description of developed application specific resilience strategies to be applied on the AllScale pilot applications as well as an evaluation of their expected capabilities.
This deliverable will describe the project website comprising the main dissemination and exploitation channels for promoting and communicating the project, relevant activities and achievements. This deliverable also provides information about the AllScale project factsheet. The web site will also have a part acting as an active “blog of research”, where partners can put articles about intermediate results, events, etc. Periodically updates of the website, according to users’ evaluation session planned in dissemination will be carried out.
Searching for OpenAIRE data...
Publications
Author(s): Peter Thoman, Kiril Dichev, Thomas Heller, Roman Iakymchuk, Xavier Aguilar, Khalid Hasanov, Philipp Gschwandtner, Pierre Lemarinier, Stefano Markidis, Herbert Jordan, Thomas Fahringer, Kostas Katrinis, Erwin Laure, Dimitrios S. Nikolopoulos
Published in: The Journal of Supercomputing, Issue 74/4, 2018, Page(s) 1422-1434, ISSN 0920-8542
DOI: 10.1007/s11227-018-2238-4
Author(s): Peter Thoman, Peter Zangerl, Thomas Fahringer
Published in: Journal of Signal Processing Systems, 2018, ISSN 1939-8018
DOI: 10.1007/s11265-018-1356-9
Author(s): Giorgis Georgakoudis, Hans Vandierendonck, Peter Thoman, Bronis R. De Supinski, Thomas Fahringer, Dimitrios S. Nikolopoulos
Published in: ACM Transactions on Architecture and Code Optimization, Issue 14/4, 2017, Page(s) 1-25, ISSN 1544-3566
DOI: 10.1145/3158643
Author(s): Juan J. Durillo, Philipp Gschwandtner, Klaus Kofler, Thomas Fahringer
Published in: Parallel Computing, 2018, ISSN 0167-8191
DOI: 10.1016/j.parco.2018.03.010
Author(s): Emanuele Ragnoli, Mykhaylo Zayats, Fearghal O'Donncha, Sergiy Zhuk
Published in: Journal of Computational Physics, Issue bimonthly, 2018, Page(s) In Press, ISSN 0021-9991
DOI: 10.5281/zenodo.1462715
Author(s): Gillan, Charles; Novakovic, Aleksandar; Shyamsundar, Murali; Marshall, Adele H; Nikolopoulos, Dimitrios
Published in: Journal of Computers in Biology and Medicine, Issue 1, 2018, ISSN 0010-4825
DOI: 10.5281/zenodo.1244669
Author(s): Roman Iakymchuk; Herbert Jordan; Philipp Gschwandtner; Thomas Heller; Peter Thoman; Xavier Aguilar; Thomas Fahringer; Erwin Laure; Stefano Markidis
Published in: Exascale Applications and Software Conference (EASC2018), 2018
DOI: 10.5281/zenodo.1119103
Author(s): Peter Thoman; Khalid Hasanov; Kiril Dichev; Roman Iakymchuk; Xavier Aguilar; Philipp Gschwandtner; Pierre Lemarinier; Stefano Markidis; Herbert Jordan; Erwin Laure; Kostas Katrinis; Dimitrios S. Nikolopoulos; Thomas Fahringer
Published in: In: Wyrzykowski R., Dongarra J., Deelman E., Karczewski K. (eds) Parallel Processing and Applied Mathematics. PPAM 2017. Lecture Notes in Computer Science, Issue 10778, 2017
DOI: 10.5281/zenodo.1162306
Author(s): Pham, Thanh-Phuong; Ristov, Sasko; Fahringer, Thomas
Published in: Issue 4, 2018
DOI: 10.5281/zenodo.1310921
Author(s): Zangerl, Peter; Jordan, Herbert; Thoman, Peter; Gschwandtner, Philipp; Fahringer, Thomas
Published in: Issue 2, 2018
DOI: 10.5281/zenodo.1309474
Author(s): Jordan, Herbert; Heller, Thomas; Gschwandtner, Philipp; Zangerl, Peter; Thoman, Peter; Fey, Dietmar; Fahringer, Thomas
Published in: Issue 2, 2018
DOI: 10.5281/zenodo.1322420
Author(s): Peter Zangerl, Peter Thoman, Thomas Fahringer
Published in: 2017 25th Euromicro International Conference on Parallel, Distributed and Network-based Processing (PDP), 2017, Page(s) 209-213
DOI: 10.1109/PDP.2017.77
Author(s): Peter Thoman, Peter Zangerl, Thomas Fahringer
Published in: Proceedings of the Computing Frontiers Conference on ZZZ - CF'17, 2017, Page(s) 201-210
DOI: 10.1145/3075564.3075574
Author(s): Klaus Kofler, Juan J. Durillo, Philipp Gschwandtner, Thomas Fahringer
Published in: 2017 46th International Conference on Parallel Processing Workshops (ICPPW), 2017, Page(s) 190-199
DOI: 10.1109/ICPPW.2017.37
Author(s): Akhriev, Albert; Gschwandtner, Philipp; Jordan, Herbert; O'Donncha, Fearghal
Published in: MTS/IEEE Oceans 2018, Issue 1, 2018, Page(s) 1-7
DOI: 10.5281/zenodo.1346169
Author(s): Kiril Dichev, Kirk Cameron, Dimitrios S. Nikolopoulos
Published in: Proceedings of the 25th European MPI Users' Group Meeting on - EuroMPI'18, 2018, Page(s) 1-11
DOI: 10.1145/3236367.3236379
Author(s): Peter Thoman; Peter Zangerl; Thomas Fahringer
Published in: 25th Euromicro International Conference on Parallel, Distributed and Network-based Processing, Issue 1, 2017
DOI: 10.5281/zenodo.375519
Author(s): Bernhard Scholz, Herbert Jordan, Pavle Subotić, Till Westmann
Published in: Proceedings of the 25th International Conference on Compiler Construction - CC 2016, 2016, Page(s) 196-206
DOI: 10.1145/2892208.2892226
Author(s): Thomas Fahringer; Thomas Heller; Peter Thoman; Herbert Jordan; Peter Zangerl
Published in: 5th International Workshop on Multicore Software Engineering (IWMSE 2016), Issue 2, 2016
DOI: 10.5281/zenodo.345835
Author(s): Jordan, Herbert; Scholz, Bernhard; Subotić, Pavle
Published in: International Conference on Computer Aided Verification, CAV 2016, Issue 2, 2016
DOI: 10.1007/978-3-319-41540-6_23
Author(s): Fearghal O'Donncha, Srikumar Venugopal, Scott C. James, Emanuele Ragnoli
Published in: OCEANS 2016 MTS/IEEE Monterey, Issue 1, 2016, Page(s) 1-7
DOI: 10.1109/OCEANS.2016.7761131
Author(s): Iakymchuk, Roman; Jordan, Herbert; Bo Peng, Ivy; Markidis, Stefano; Laure, Erwin
Published in: Exascale Applications and Software Conference (EASC2016), 2016
Author(s): Kiril Dichev, Dimitrios S. Nikolopoulos
Published in: 2016 IEEE International Conference on Cluster Computing (CLUSTER), 2016, Page(s) 506-514
DOI: 10.1109/CLUSTER.2016.99