1. **Introduction**

  

  

This Data Management Plan (DMP) describes the data management life cycle for
all datasets that will be collected, processed or generated by the ExaNoDe
project. This document outlines how research data will be handled during the
project and after the project completion. The DMP is not a fixed document, but
it evolves during the lifespan of the ExaNoDe project. This is the first
version of the DMP which has been aligned with the amendment reference No
AMD-671578-13. The DMP will be updated according to project needs.

Several categories of datasets are identified within the ExaNoDe project:

  * **Reporting material** such as Consortium Agreement, Grant Agreement, deliverables or any other kind of material exchanged with the European Commission. 

  

  * **Scientific publications, presentations and dissemination material** that describe the research work within ExaNoDe. 

  

  * **Technical datasets** including the technical work such as source code of tools, libraries, RTL codes, netlist, design scripts, etc. 

  

  * **Evaluation datasets** that accompany the scientific publications and/or deliverables and usually provide more information than the one included in the publications. 

  

This DMP addresses the points below on a dataset by dataset basis and reflects
the current status of reflection within the consortium about the data that
will be produced:

  * **Data set reference and name:** identifier for the data set to be produced. 

  

  * **Data set description:** description of the data that will be generated or collected, its origin (in case it is collected), nature and scale and to whom it could be useful. 

  

  * **Standards and metadata:** reference to existing suitable standards of the discipline. 

  

  * **Data sharing:** description of how data will be shared, including access procedures, embargo periods (if any), outlines of technical mechanisms for dissemination and necessary software and other tools for enabling re-use, and definition of whether access will be widely open or restricted to specific groups. Identification of the repository where data will be stored, if already existing and identified, indicating in particular the type of repository (institutional, standard repository for the discipline, etc.). 

  

  * **Archiving and preservation (including storage and backup):** description of the procedures that will be put in place for long-term preservation of the data. Indication of how long the data should be preserved. 

  

The following sections provide the current status of reflection within the
consortium about the data that will be produced for the various identified
categories.

  2. **Reporting material**

  

  

Several non-technical documents for reporting the project progress with the
European Commission will be produced within ExaNoDe, such as the Consortium
Agreement, Grant Agreement, and meeting minutes.

A list of these datasets is provided in Table 1.  
  
<table>  
<tr>  
<th>

**Type Reference Description Standards Data sharing Archiving and**

**and name and preservation**

**metadata**

</th> </tr>  
<tr>  
<td>

**Document**

</td>  
<td>

Grant Agreement number: 671578

</td>  
<td>

ExaNoDe Grant Agreement

electronically signed by all consortium members

</td>  
<td>

pdf file

</td>  
<td>

Codendi repository  (1)  for ExaNoDe consortium members, EC

repository  (2)  for

Commission services.

</td>  
<td>

Dataset will be available on Codendi at least two years after the end of the
project.

</td> </tr>  
<tr>  
<td>

**Document**

</td>  
<td>

Consortiu m

Agreement ref. 22773

</td>  
<td>

ExaNoDe

Consortium Agreement

signed by all consortium legal entities

</td>  
<td>

Paper copy

</td>  
<td>

All partners have the same hard copy of the CA. An electronic copy is shared
on Codendi repository  (1)  .

</td>  
<td>

Hard copy must be maintained and preserved by each partner even after the end
of the project (at least 6 years).

</td> </tr>  
<tr>  
<td>

**Document**

</td>  
<td>

Amendme

nt

Reference

No AMD-

671578-13

</td>  
<td>

ExaNoDe amendment

electronicaly signed by the Commission and the Coordinator

</td>  
<td>

pdf file

</td>  
<td>

Data sharing on: Codendi

repository  (1)  for

ExaNoDe consortium members, EC

repository  (2)  for

Commission services.

</td>  
<td>

Dataset will be available on Codendi at least two years after the end of the
project.

</td> </tr>  
<tr>  
<td>

**Guide**

</td>  
<td>

Project manual

</td>  
<td>

ExaNoDe

project manual

</td>  
<td>

Microsoft Office documents

</td>  
<td>

Data sharing on Codendi repository  (1)  for

ExaNoDe consortium members.

</td>  
<td>

Dataset will be available on Codendi at least two years after the end of the
project.

</td> </tr>  
<tr>  
<td>

**Minutes**

</td>  
<td>

Meeting minutes

</td>  
<td>

ExaNoDe

meeting minutes

</td>  
<td>

pdf files

</td>  
<td>

Data sharing on Codendi repository  (1)  for

ExaNoDe consortium members.

</td>  
<td>

Dataset will be available on Codendi at least two years after the end of the
project.

</td> </tr>  
<tr>  
<td>

**Document**

</td>  
<td>

Periodic

Progress

Report

</td>  
<td>

ExaNoDe

Periodic

Progress Reports (for check meetings with the

Commission and formal reviews)

</td>  
<td>

pdf files

</td>  
<td>

Data sharing on Codendi repository  (1)  for

ExaNoDe consortium members.

An electronic copy is provided to the reviewers and the Project Officer before
each check meeting or review.

</td>  
<td>

Dataset will be available on Codendi at least two years after the end of the
project.

</td> </tr>  
<tr>  
<td>

**Presentations**

</td>  
<td>

Project meeting, check meeting and formal review presentatio ns

</td>  
<td>

ExaNoDe

presentations made during the project meetings, the check meetings and the
formal reviews

</td>  
<td>

pdf files

</td>  
<td>

Data sharing on Codendi repository  (1)  for

ExaNoDe consortium members.

An electronic copy is provided to the reviewers and the Project Officer before
each check meeting or review.

</td>  
<td>

Dataset will be available on Codendi at least two years after the end of the
project.

</td> </tr>  
<tr>  
<td>

**Document**

</td>  
<td>

Memorand um-ofUnderstan ding

</td>  
<td>

Memorandum-

of-

Understanding signed between the coordinators of the projects:

ExaNoDe,

ExaNeSt and EcoScale.

</td>  
<td>

pdf file

</td>  
<td>

Data sharing on Codendi repository  (1)  for

ExaNoDe consortium members.

</td>  
<td>

Dataset will be available on Codendi at least two years after the end of the
project.

</td> </tr> </table>

#  Table 1: Reporting datasets

**Notes from table:**

  1. Codendi is a project management environment  ( _https://minalogic.net/account/login.php_ )  used for ExaNoDe, which offers an easy, secured and consortium-limited access to ExaNoDe project datasets. Figure 1 shows the document menu which can be used to upload and download reporting materials including technical deliverables. 

  

  

**Figure 1: Codendi document repository of the ExaNoDe project**

  2. Research Participant Portal to manage the ExaNoDe project and communicate with the European Commission throughout the project’s life cycle : 

  

  

_http://ec.europa.eu/research/participants/portal/desktop/en/home.html_

Apart from the above non-technical reporting dataset, ExaNoDe deliverables are
considered to be scientific reports of the work within the project. Several
deliverables will be publicly available and posted on the ExaNoDe website in
PDF format. Deliverables will be stored in the Codendi repository in Microsoft
Word format. The table below lists the deliverables based on their type and
dissemination level.  
  
<table>  
<tr>  
<th>

**Type**

</th>  
<th>

**Reference and name**

</th>  
<th>

**Dissemination level**

</th>  
<th>

**Data sharing**

</th>  
<th>

**Archiving and preservation**

</th> </tr>  
<tr>  
<td>

**Reports**

</td>  
<td>

D1.1, D1.3,

D3.4, D3.9, D4.1, D4.2, D4.7, D6.4,

D6.7

</td>  
<td>

Confidential

</td>  
<td>

Codendi repository for ExaNoDe consortium members, EC continuous reporting
repository  (3)  for Commission services.

</td>  
<td>

Dataset will be available on Codendi at least two years after the end of the
project.

</td> </tr>  
<tr>  
<td>

**Others**

</td>  
<td>

D3.5, D4.3,

D4.5, D5.1,

D5.3, D5.4

</td>  
<td>

Confidential

</td>  
<td>

Codendi repository for ExaNoDe consortium members, EC continuous reporting
repository  (3)  for Commission services.

</td>  
<td>

Dataset will be available on Codendi at least two years after the end of the
project.

</td> </tr>  
<tr>  
<td>

**Demonst**

**rators**

</td>  
<td>

D4.4, D4.6

</td>  
<td>

Confidential

</td>  
<td>

Codendi repository for ExaNoDe consortium members, EC continuous reporting
repository  (3)  for Commission services.

</td>  
<td>

Dataset will be available on Codendi at least two years after the end of the
project.

</td> </tr>  
<tr>  
<td>

**ORDP:**

**Open**

**Research**

**Data**

**Pilot**

</td>  
<td>

D1.4

</td>  
<td>

Public

</td>  
<td>

Codendi repository for ExaNoDe consortium members, EC continuous reporting
repository  (3)  for Commission services, ExaNoDe website  (4)  for public
access.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Reports**

</td>  
<td>

D2.1, D2.2,

D2.3, D2.4,

D2.5, D2.6, D2.7, D3.1, D3.2, D3.6,

D3.7, D5.2,

D5.5, D6.2,

D6.5

</td>  
<td>

Public

</td>  
<td>

Codendi repository for ExaNoDe consortium members, EC continuous reporting
repository  (3)  for Commission services, ExaNoDe website  (4)  for public
access.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Demonst**

**rators**

</td>  
<td>

D3.3, D3.8

</td>  
<td>

Public

</td>  
<td>

Codendi repository for ExaNoDe consortium members, EC continuous reporting
repository  (3)  for Commission services, ExaNoDe website  (4)  for public
access.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Others**

</td>  
<td>

D6.1, D6.3, D6.6

</td>  
<td>

Public

</td>  
<td>

Codendi repository for ExaNoDe consortium members, EC continuous reporting
repository  (3)  for Commission services, ExaNoDe website  (4)  for public
access.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr> </table>

#  Table 2: Deliverables

**Notes from table:**

(3) Figure 2 shows the continuous reporting menu which is used for reporting
the ExaNoDe documentation with the European Commission.

**Figure 2: Continuous reporting repository of the ExaNoDe project:**

**_http://ec.europa.eu/research/participants/portal/desktop/en/home.html_ **
(4)  _http://exanode.eu/_

#  3 Scientific publications, presentations and dissemination materials

There is a need to maximise the impact of European collaborative projects, and
this is one of the primary goals of the European Commission’s funding schemes,
aiming at promoting Europe’s strategic position in target technical fields.
The ExaNoDe consortium considers dissemination activities to be as important
as the technical work carried on within each task, to maximize the impact of
the project and get feedback from outside the project environment to drive the
work performed in a successful manner.

In the ExaNoDe project, the partners plan to give great importance to
dissemination, by presenting posters or publishing scientific papers to
international conferences or journals, by participating in events such as
workshops organized by the European community and by providing dissemination
materials with project website, flyers, and so on. For this purpose, a large
amount of dissemination data will be generated throughout the project.

For more information on the planned dissemination activities, deliverable D6.2
“Dissemination strategy Document” presents the plan for the dissemination of
the ExaNoDe project outcomes, and the project manual [1] sets the basic rules
for publications, presentations and copyright usage. This section of the DMP,
describes in detail how dissemination data will be handled within the ExaNoDe
project.

The following table provides the available scientific publications,
presentations and dissemination materials, as at M18 of the ExaNoDe project:  
  
<table>  
<tr>  
<th>

**Type Reference Description Data sharing and name**

</th>  
<th>

**Archiving and preservation**

</th> </tr>  
<tr>  
<td>

**Article**

</td>  
<td>

ExaNoDe

@ HPC

Wire 2016

</td>  
<td>

HPC Wire article on

“EU Projects Unite on Heterogeneous ARM-based Exascale Prototype” published on
Feb 24th 2016.

</td>  
<td>

HPC Wire repository

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Poster**

</td>  
<td>

ExaNoDe

@ DATE

2016

</td>  
<td>

Poster presented at

DATE 2016 in

Dresden by CEA

</td>  
<td>

Codendi repository for ExaNoDe consortium members; ExaNoDe website for public
access.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Poster**

</td>  
<td>

ExaNoDe

@

HiPEAC

2017

</td>  
<td>

Poster presented at

HiPEAC 2017 in

Stockholm by CEA

</td>  
<td>

Codendi repository for ExaNoDe consortium members; ExaNoDe website for public
access.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Presentation**

</td>  
<td>

ExaNoDe

@ ISC

2016

</td>  
<td>

Presentation at workshop on

International

Cooperation at ISC 2016 in Frankfurt by BSC.

</td>  
<td>

Codendi repository for ExaNoDe consortium members.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Presentation**

</td>  
<td>

ExaNoDe

@ MontBlanc workshop

2017

</td>  
<td>

Presentation at MontBlanc project workshop in

Barcelona by CEA.

</td>  
<td>

Codendi repository for ExaNoDe consortium members.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Publication**

</td>  
<td>

ExaNoDe

@ ISC

2017

</td>  
<td>

Position paper submitted at ISC

</td>  
<td>

Codendi repository for ExaNoDe consortium members.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td>  
<td>

2017 in Frankfurt by

VOSYS.

</td>  
<td>

</td>  
<td>

</td> </tr>  
<tr>  
<td>

**Publication**

</td>  
<td>

ExaNoDe

@

MEMSYS

2016

</td>  
<td>

Publication by BSC at MEMSYS 2016

</td>  
<td>

Codendi repository for ExaNoDe consortium members.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Publication**

</td>  
<td>

ExaNoDe

@

IWOMP

2016

</td>  
<td>

Publication by UOM at IWOMP 2016

</td>  
<td>

Codendi repository for ExaNoDe consortium members.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Publication**

</td>  
<td>

ExaNoDe

@ ISPASS

2016

</td>  
<td>

Publication by UOM at ISPASS 2016

</td>  
<td>

Codendi repository for ExaNoDe consortium members.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Publication**

</td>  
<td>

ExaNoDe

@ PACT

2016

</td>  
<td>

Publication by UOM at PACT 2016

</td>  
<td>

Codendi repository for ExaNoDe consortium members.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Poster**

</td>  
<td>

ExaNoDe @

ACACES

2016

</td>  
<td>

Poster presented at

ACACES 2016 in

Fiuggi by FORTH

</td>  
<td>

Codendi repository for ExaNoDe consortium members.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Website**

</td>  
<td>

ExaNoDe

project website

</td>  
<td>

exanode.eu

</td>  
<td>

Website subcontractor premises

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Flyer**

</td>  
<td>

ExaNoDe

flyer

</td>  
<td>

Public information about the project, its objectives and future achievements

</td>  
<td>

Website for public access.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr> </table>

**Table 3: Scientific publications, presentations and dissemination
materials**

Table 3 will be amended throughout the project, in order to include newly
generated dissemination data.

The publications and related research data will be publicly provided by
research data repositories respecting the policies and rules set out by the
publishers (journals or conferences). The partners will use an open access
repository, connected to the tools proposed by the European Commission (e.g.
OpenAIRE), to grant access to the publications and to a bibliographic metadata
in a standard format including information requested by the European
Commission. Moreover, some posters shown in Table 3 will be posted on the
ExaNoDe website.

All scientific publications involving BSC will be uploaded to the UPCommons
open access repository of _Universitat Politècnica de Catalunya_ (UPC).

**4 Technical Datasets**

The technical datasets generated by the ExaNoDe project include:

  * Mini-application and performance-critical kernel codes (from WP2 “Co-Design for Exascale HPC systems”); 

  

  * Firmware, OS, virtual machine, parallel programming models and runtime libraries codes (from WP3 “Enablement of Software Compute Node”); 

  

  * System-on-Chip design databases: RTL code, hard-macro design, gate netlist, design scripts, design environment, GDS2 file (from WP4 “Compute node design and manufacture”); 

  

  * Board design datasets (from WP5 “System Integration & Evaluation”). 

  

The following technical datasets are foreseen for ExaNoDe project:  
  
<table>  
<tr>  
<th>

**Type Reference Description Standards Data sharing Archiving and**

**and name and preservation**

**metadata**

</th> </tr>  
<tr>  
<td>

**Code**

</td>  
<td>

Mini-apps or kernels of performance-

critical algorithms

</td>  
<td>

Source or binary code of the miniapplications or performance critical kernels.

</td>  
<td>

Binary files or plain text files.

</td>  
<td>

No such datasets have been generated at M18 of the ExaNoDe project. Data
sharing, and archiving policies will be described in an updated DMP.

</td> </tr>  
<tr>  
<td>

**Binary code**

</td>  
<td>

Virtual machine enhanced checkpoint with post-copy

</td>  
<td>

Source code of the virtual machine

memory

snapshot based on post-copy.

</td>  
<td>

plain text files (e.g., .h,

.c)

</td>  
<td>

The code will be released in the form of

diff patches to the open source Qemu and

Linux communities.

</td>  
<td>

Source code available in various mailing lists archives, and in QEMU code tree
once upstream.

</td> </tr>  
<tr>  
<td>

**Binary code**

</td>  
<td>

Virtual machine incremental checkpoint

</td>  
<td>

Binary release of the Virtual Machine incremental checkpointing feature.

</td>  
<td>

Binary file

</td>  
<td>

Binary will be released to the ExaNoDe consortium for integration and final
project prototype demonstration.

</td>  
<td>

Binary released to

ExaNoDe

consortium for use only within the project lifetime.

</td> </tr>  
<tr>  
<td>

**Binary code**

</td>  
<td>

ExaNoDe firmware

</td>  
<td>

Realization of

UNIMEM support on experimental prototypes of

the ExaNoDe project (hardware design for

FPGAs together with Linux device drivers)

</td>  
<td>

Binary files

</td>  
<td>

The firmware, in the form of binary code (FPGA bitstreams, Linux device
drivers and kernel configuration), will be installed in the shared

testbed, hosted at FORTH premises,

available for use by partners.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Binary code**

</td>  
<td>

ExaNoDE

operating system

</td>  
<td>

Enhancements and additions to the Linux kernel (together with API libraries)
for exposing Unimem

platform functionality to programming models and enduser applications.

</td>  
<td>

Binary files

</td>  
<td>

The operating system, in the form of binary code (Linux with Unimem support
and low-level API libraries), will be installed in the shared

testbed, hosted at FORTH premises,

available for use by partners.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Source code**

</td>  
<td>

UNIMEMoptimized MPI library

</td>  
<td>

MPI library that has been optimized for

use with

UNIMEM

memory scheme

</td>  
<td>

Implementat ion of the

MPI

standard consisting of plain text files (e.g., .h,

.c)

</td>  
<td>

The UNIMEM MPI source code will be maintained by BSC and FORTH and available
from a git or SVN repository hosted at BSC. The code will be freely
downloadable with an open source licence.

</td>  
<td>

The UNIMEM

MPI source code will be available at least three years after the end of the
project.

</td> </tr> </table>  
<table>  
<tr>  
<th>

**Source code**

</th>  
<th>

GPI

</th>  
<th>

PGAS based

distributed onesided and asynchronous programming model.

</th>  
<th>

GPI implements the GASPI standard to be found at: www.gaspi.d

e

</th>  
<th>

The GPI code will be maintained at

Fraunhofer's premises and released with an open source licence.

</th>  
<th>

Dataset will be available at least five years after the end of the project.

</th> </tr>  
<tr>  
<td>

**Source code**

</td>  
<td>

Mercurium

</td>  
<td>

OmpSs

compiler

</td>  
<td>

plain text files (e.g., .h,

.c)

</td>  
<td>

The Mercurium compiler source code is maintained by BSC and freely
downloadable from a git repository hosted at BSC, with the LGPL licence.

</td>  
<td>

The Mercurium source code will be available at least 3 years after the end of
the project.

</td> </tr>  
<tr>  
<td>

**Source code**

</td>  
<td>

Nanos 6

</td>  
<td>

OmpSs runtime system

</td>  
<td>

plain text files (e.g., .h,

.c)

</td>  
<td>

The Nanos 6 runtime system source code is maintained by BSC in a git
repository hosted at BSC. Before the end of the project the code will be
freely downloadable with an open source licence.

</td>  
<td>

The Nanos 6 source code will be available at least 3 years after the end of
the project.

</td> </tr>  
<tr>  
<td>

**Source code**

</td>  
<td>

OpenStream

</td>  
<td>

OpenStream compiler and runtime system

</td>  
<td>

Plain text files (e.g., .h,

.c)

</td>  
<td>

The OpenStream source code is maintained by UoM and publicly available through
a dedicated

portal

( _www.openstream.info_ )  and git repository hosted at UoM. The runtime
system code is freely available under GPLv2 license, the compiler is based on
the GNU C Compiler

and inherits its licenses (mostly GPLv2 and 3).

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Source code**

</td>  
<td>

Thermal management

</td>  
<td>

Power capping and thermal management

</td>  
<td>

plain text files (e.g., .h,

.c, .py)

</td>  
<td>

The thermal management runtime code is maintained by ETHZ in a git repository
hosted at ETHZ. Before the end of the project the code will be freely
downloadable with an open source licence.

</td>  
<td>

The thermal management

source code will be available at least 3 years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Chiplet RTL code**

</td>  
<td>

ExaNode_Chi plet_RTL

</td>  
<td>

RTL code of chiplet design

</td>  
<td>

VHDL, Verilog…

files

</td>  
<td>

The RTL code will be maintained at CEA's premises.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**ExaConv RTL code**

</td>  
<td>

ExaNode_Exa Conv_RTL

</td>  
<td>

RTL code of the

Convolution Hardware operator

</td>  
<td>

VHDL, Verilog…

files

</td>  
<td>

The RTL code will be maintained at ETHZ's premises.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**UoM RTL**

**code + Rx/Tx**

**cells**

</td>  
<td>

ExaNode_Uo M_Macros

</td>  
<td>

Rx/Tx Hard macro

</td>  
<td>

VHDL, Verilog…

files

</td>  
<td>

The RTL code + Hard Macro will be

</td>  
<td>

Dataset will be available at least

</td> </tr>  
<tr>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

</td>  
<td>

maintained at UoM's premises.

</td>  
<td>

two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Chiplet netlist**

</td>  
<td>

ExaNode_Chi

plet_Netlist

</td>  
<td>

Mapping of the RTL code of the chiplet design onto 28FDSOI technology

</td>  
<td>

Verilog netlist

</td>  
<td>

The RTL code will be maintained at CEA's premises.

</td>  
<td>

Dataset will be available at least

two years after the end of the project. Snapshot backup policy is in place

\+ copy in another room on a daily basis with 6

months retention of the data

</td> </tr>  
<tr>  
<td>

**Design scripts**

</td>  
<td>

ExaNode_Des

ign_Scripts

</td>  
<td>

Scripts and constraints used to generate both netlist and GDS

starting from

RTL code

</td>  
<td>

sh, csh, tcl, sdc …. files

</td>  
<td>

The design scripts will be maintained at CEA's premises.

</td> </tr>  
<tr>  
<td>

**GDS2 file**

</td>  
<td>

ExaNode_GD

S2

</td>  
<td>

Output of the design flow, file sent to the foundry

</td>  
<td>

GDS2

</td>  
<td>

The GDS2 code will be maintained at CEA's premises.

</td> </tr>  
<tr>  
<td>

**Verification environment**

</td>  
<td>

ExaNode_Veri f_Env

</td>  
<td>

Testbench and associated files used to validate the RTL code both functionally
and in test mode

</td>  
<td>

sh, csh, tcl,

C …. files

</td>  
<td>

The verification environment plaform will be maintained at CEA's premises.

</td> </tr>  
<tr>  
<td>

**FPGA RTL**

**code**

</td>  
<td>

ExaNode_Chi plet_FPGA_R TL

</td>  
<td>

RTL code for FPGAs chiplet programming

</td>  
<td>

VHDL,

Verilog files

</td>  
<td>

The RTL code will be maintained at FORTH's premises.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**FPGA scripts**

</td>  
<td>

ExaNode_Chi

plet_FPGA_S

cripts

</td>  
<td>

Script for program load

onto the FPGAs chiplet

</td>  
<td>

sh, csh, tcl, C files

</td>  
<td>

The script bunch will be maintained at

FORTH's premises.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**FPGA Design**

</td>  
<td>

ExaNode_CFP GA1_RTL

</td>  
<td>

RTL code and

Vivado files for

MCM Compute FPGA1 programming

</td>  
<td>

VHDL,

Verilog,

Vivado files

</td>  
<td>

The RTL code and Vivado files will be maintained at FORTH's premises.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**FPGA Design**

</td>  
<td>

ExaNode_CFP GA2_RTL

</td>  
<td>

RTL code and

Vivado files for

MCM Compute FPGA2 programming

</td>  
<td>

VHDL,

Verilog,

Vivado files

</td>  
<td>

The RTL code and Vivado files will be maintained at FORTH's premises.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**FPGA scripts**

</td>  
<td>

ExaNode_CFP

GA_Scripts

</td>  
<td>

Script for program load onto the MCM FPGAs

</td>  
<td>

sh, csh, tcl, C files

</td>  
<td>

The script bunch will be maintained at

FORTH's premises.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Schematics**

</td>  
<td>

ExaNodeDem

onstration board schematics

</td>  
<td>

Schematics in ORCAD format

</td>  
<td>

.opj

</td>  
<td>

The schematics will be maintained at FORTH's premises.

</td>  
<td>

Dataset will be available at least two years after the end of the project

</td> </tr>  
<tr>  
<td>

**PCB Layout**

</td>  
<td>

ExaNodeDem onstration board layout

</td>  
<td>

Layout in

Allegro format

</td>  
<td>

.brd and gerber files

</td>  
<td>

The PCB layout files will be maintained at FORTH's premises.

</td>  
<td>

Dataset will be available at least two years after the end of the project

</td> </tr> </table>

#  Table 4: Technical Datasets within ExaNoDe

Some of the technical datasets will be maintained at the partners’ premises
and made available for ExaNoDe partners for prototype integration. This could
also be done through the CVS repository of the Codendi web-based project
management environment for ExaNoDe. It offers an easy, secured and consortium
limited access to ExaNoDe project datasets.

Moreover several of the technical datasets will be provided under open-source
licenses and are publicly available for download from a git or SVN repository
hosted at the partner’s premises (see Table 4 for related datasets).

Aiming to reach the widest audience possible, and accomplishing dissemination
and communication strategy and with the aim of getting sustainability at the
end of the project, the ExaNoDe website can provide descriptions and links to
the various individual sites hosting the source code licensed under any kind
of open-source license. This kind of decisions will be taken along the project
lifecycle and thus, the DMP will be updated accordingly.

#  5 Evaluation Datasets

The evaluation datasets accompany the scientific publications and
deliverables. These datasets include evaluation and performance measurements
of the ExaNoDe architecture and prototype. We foresee the following evaluation
datasets:  
  
<table>  
<tr>  
<th>

**Type**

</th>  
<th>

**Reference and name**

</th>  
<th>

**Description**

</th>  
<th>

**Standards and metadata**

</th>  
<th>

**Data sharing**

</th>  
<th>

**Archiving and preservation**

</th> </tr>  
<tr>  
<td>

**Simulation results**

</td>  
<td>

Chiplet simulation results

</td>  
<td>

Simulation results from the verification testbench

</td>  
<td>

Completed

verification plan

</td>  
<td>

The simulation results will be available at CEA's premises.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

Snapshot backup policy is in place + copy in another room on a daily basis
with 6 months retention of

the data

</td> </tr>  
<tr>  
<td>

**Measureme**

**nts**

</td>  
<td>

Critical kernels performan ces

</td>  
<td>

Performance measurements of miniapplications or critical kernels

</td>  
<td>

Measuremen

t result files

</td>  
<td>

The results will be available from the Codendi SVN repository for project
internal sharing.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Measureme**

**nts**

</td>  
<td>

Synthetic benchmark

performan ces

</td>  
<td>

Performance measurements of synthetic benchmarks

</td>  
<td>

Measuremen

t result files

</td>  
<td>

The results will be available from the Codendi SVN repository for project
internal sharing.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Measureme**

**nts**

</td>  
<td>

Microbenchmark

s for

UNIMEM mechanism

s

</td>  
<td>

Performance measurements of synthetic benchmarks using the

UNIMEM

firmware on ExaNoDe

testbench

</td>  
<td>

Measuremen

t result files

</td>  
<td>

The results will be available from the Codendi SVN repository for project
internal sharing.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr>  
<tr>  
<td>

**Measureme**

**nts**

</td>  
<td>

benchmark performan ces

</td>  
<td>

Performance measurements

of

communicatio n benchmarks

</td>  
<td>

Measuremen

t result files

</td>  
<td>

The results will be available from the Codendi SVN repository for project
internal sharing.

</td>  
<td>

Dataset will be available at least two years after the end of the project.

</td> </tr> </table>

**Table 5: Evaluation datasets**

Page

  6. **Concluding Remarks**

  

  

This deliverable presents the Data Management Plan (DMP) of the ExaNoDe
project aligned with the amendment reference No AMD-671578-13. It describes
the data management life cycle for all datasets that will be collected,
processed or generated by ExaNoDe project. Several categories of datasets have
been identified. Categories by categories, this DMP addresses data sharing and
archiving and reflects the current status of reflection within the consortium
about the data that will be produced.

The DMP evolves during the lifespan of the ExaNoDe project and it will be
updated according to project needs.

  7. **References and Applicable Documents**

  

  

[1] Wray F. ExaNoDe Project Manual, V1.3 Dec. 2016

Page