Skip to content

Review of Guideline #38

philippemilletresearch edited this page Jan 30, 2019 · 5 revisions

Review of Guideline #38

Formatting

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

Is the audience of the guideline correctly specified?

Yes

Is the expertise required to write the guideline correctly specified?

Yes

Are the keywords well selected?

Maybe add a few more keywords like application mapping, GPGPU, accelerators etc. since it is more focused towards this.

Are parts of the guideline too generic or too specific?

Insight is well written; starting with the target implementation, the problem statement and why it is necessary to solve it. The implementation method described is a bit general, which is helpful in understanding the issues faced. The guideline is fairly clear and technical in terms of the problem faced but adding more details on data organization and application modification to improve maximum chip utilization and performance would be helpful. The solution proposed is too generic and can be explained more, so it becomes more helpful for other users who want to adapt it.

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)?

No. It should be mentioned.

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

Yes, the guideline specifies the work in the project that can benefit.

Other comments

  1. Guideline advice: There are some typos that can be improved.

  2. Insights that led to the guideline: see above.

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

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

  5. Evaluation of the guideline in reference applications: Briefly explained.

  6. References: OK

Track changes:

  1. 03/08/2018: Guideline created
  2. 30/11/2018: guideline reviewed.
  3. 30/01/2019: guideline updated
Clone this wiki locally