Guideline Review Template

Review of Guideline #XXX

Note: Replace XXX in the title with the ID of the guideline you are reviewing

Formatting

Item	Outcome
Guideline complies with the Guideline-Template	Yes/No
Name of guideline responsible with affiliation is clearly stated	Yes/No

Select Yes or No in the table above.

Is the audience of the guideline correctly specified?

Audience is at least one of (only the name of the category should appear):

• HW designers: Dealing with the design of the hardware platform, the components choices and the interfaces according to system requirements.
• OS designers: Dealing with the operating system design and development facing the need to bring standard APIs for applications and making the OS work on the hardware platform while bringing the application the means to efficiently control the hardware behaviour.
• Toolchain designers: Dealing with the application developers. They must bring a comprehensive tool that allows the application designer to efficiently map the application on the hardware.
• Application developers: Knowing the algorithms behind an application and having the ability to develop the code on the chosen hardware. They understand the complete stack and can make use of the tool to develop faster the application. We will also find under this category :
  • Software developers that can develop and optimise software on CPUs (GPPs, GPUs, DSPs...)
  • RTL/VHDL/Verilog developers that can develop and optimise code on FPGAs.
• System architects: Dealing with the whole system definition from the definition of the constraints that comes from the final product, having in mind the targeted price of the solution and able to understand integration issues that come with any choice from the other four groups.

Note: Stating audiences outside of these groups is not allowed

Is the expertise required to write the guideline correctly specified?

Note: Only the categories listed above are allowed

Are the keywords well selected?

**Note: Each time we use a new keyword, it must be added to the template to be shared by the guideline reviewers

Keywords are one of the following (only the name of the category should appear):

• Component selection: The guideline is dealing with the choice of a component. The component can be hardware (e.g. a chip, an interface...) or software (e.g. an OS, a library, an API...) or both (e.g. a protocol)
• Energy efficiency: The guideline is dealing with improving what the platform can achieve with the lowest possible energy consumption. This is often referred as power saving but the main idea is to get longer time of use on batteries. Energy is then preferred to power for, the power being the time derivative of the energy, energy saving is what will allow the system to work longer with a given amount of energy in its batteries. To this end one will have to measure and monitor power consumption over time, evaluate time spent to process functions to extract the efficiency of the platform in the execution of each function. One will also have to understand power optimization like DVFS or isolation of power domains.
• Code Optimisation: The guideline is dealing with the optimisation of source code. The source code can be either C, assembly as well as VHDL or Verilog. Optimisation can refer to executing faster or consuming less energy or less power.
• FPGA: The guideline is dealing with FPGA technology.
• System optimisation: The guideline deals with design choices that the developer needs to consider to improve a KPI such as frame rate or energy consumption.
• GPU: The guideline is dealing with GPU technology.
• Toolchain: The guideline is dealing with how to use the Toolchain efficiently.

Are parts of the guideline too generic or too specific?

1. Please use a numbered list to refer to requested changes

Note: If too specific, also check and add advices : how the guideline could be extended? Note: If too generic, then it is meaningless. Give hints : how to improve the impact?

Does the guideline explicitly refer to the handbook? To which part of the deliverable is it relevant (e.g., chapter of D1.2/D1.3)?

If no, what parts of D1.2/D1.3 should it refer to. You must evaluate and give a clear answer to help the guideline author to create a link with the handbook.

Does the guideline specify the work done in the project that can benefit from the guideline?

If no, do you have any suggestions on how the project can benefit from these insights?

Other comments

Note: give detailed comments on each part. You can also add other comments as additional list elements

1. Guideline advice:

2. Insights that led to the guideline:

3. Recommended implementation method of the guideline along with a solid motivation for the recommendation:

4. Instantiation of the recommended implementation method in the reference platform:

5. Evaluation of the guideline in reference applications:

6. References:

7. Please use a numbered list to refer to other requested changes