-
Notifications
You must be signed in to change notification settings - Fork 0
Review of Guideline #39
| Item | Outcome |
|---|---|
| Guideline complies with the Guideline-Template | Yes |
| Name of guideline responsible with affiliation is clearly stated | Yes |
Yes, this guideline refers to application developers.
Yes. The required expertise is application development.
The keyword identified is optimization which do not identify the complete scope of the guideline. The keyword can be improved such as application development optimization.
They are generic but considering that the targeted audience are mainly application developers, it is properly described and there is no need to be more specific.
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.
Yes. The guideline was used for the medical use case to make the allocations static.
-
Guideline advice: None.
-
Insights that led to the guideline: Considering that the majority of TULIPP's audience are software programmers, the guideline is appropriate to keep memory allocation in mind during programming.
-
Recommended implementation method of the guideline along with a solid motivation for the recommendation: The author has advised to refrain from dynamic memory allocation. However, if dynamic allocation is really necessary, then it must be performed at an initialization phase of the application.
-
Instantiation of the recommended implementation method in the reference platform: HIPPEROS developers would be able to comment on the guideline taking into consideration what their OS is able to do regarding garbage collection (if available).
-
Evaluation of the guideline in reference applications: The guideline was evaluated for the medical use case. In order to improve the performance, the allocations were made static.
-
References:
- 03/08/2018: Guideline created
- 10/12/2018: guideline reviewed.
- 30/01/2019: guideline updated
TULIPP Guideline Wiki