Energy-Toolbox-Front-end.md

@@ -2,11 +2,14 @@ A user interface is provided where the user can select the applications for anal
 
 [[/uploads/figure1_energy.png]]
 
-Figure 1 displays the user interface for project-related information. As has been already stated, this panel shall be deprecated once the whole SDK4ED platform has been integrated and user and project management has been centralised. The backend will then automatically query the main integration module for user and project related information.
+The Figure above displays the user interface for project-related information. As has been already stated, this panel shall be deprecated once the whole SDK4ED platform has been integrated and user and project management has been centralised. The backend will then automatically query the main integration module for user and project related information.
 “New/Last analysis” is used to start a new analysis or to display the profiling results of the last analysis performed. 
 Developers can specify the scale of the analysis, by selecting “Full Analysis” for profiling the application to report all indicators or to choose a specific analysis (eg. hotspots indication, static analysis). The selection depends on the availability of the accelerator, developer preferences and priorities, etc. 
 
-Figure 2 shows one of the two main functionalities of the toolbox, which is the identification of hotspots and the reporting of profiling results for each one. 
+The following image shows one of the two main functionalities of the toolbox, which is the identification of hotspots and the reporting of profiling results for each one. 
+
+[[/uploads/figure2_energy.png]]
+
 This panel consists of two parts: 
 Profiling results across the whole application: Includes the following profiling information, which correspond to the indicators for energy consumption, as reported in D3.2: “Suitable Indicators for energy consumption”: 
 * CPU cycles: The number of CPU cycles for the whole application execution
@@ -21,6 +24,10 @@ Profiling results per hotspot: Includes the hotspot ID, source file, start and e
 * Ratio of cache misses 
 The hotspots can be identified at two granularity levels: At function-level and at loop-level. Developers can configure this selecting by “Hotspot Granularity”.
 
-Figure 3 shows the values of a subset of the acceletor-specific indicators (i.e. the ones that influence the accelerator decision in higher degree than the others) for each hotspot. The values of these indicators are shown when “Full Analysis” is initially selected. The “Hotspot Granularity” is also applicable in this case. 
+The next Figure depicts the values of a subset of the acceletor-specific indicators (i.e. the ones that influence the accelerator decision in higher degree than the others) for each hotspot. The values of these indicators are shown when “Full Analysis” is initially selected. The “Hotspot Granularity” is also applicable in this case. 
+
+[[/uploads/figure3_energy.png]]
+
+The proposed optimizations per hotspot are depicted in the lowest part of the energy toolbox GUI, shown in the following Figure. The first column is the hotspot ID and the second the proposed optimization for each one. 
 
-The proposed optimizations per hotspot are depicted in the lowest part of the energy toolbox GUI, shown in Figure 4. The first column is the hotspot ID and the second the proposed optimization for each one. 
+[[/uploads/figure4_energy.png]]
\ No newline at end of file