doc:add images to doc

docs/user/user_categories.md

@@ -21,7 +21,7 @@ Parameters required : time of the first job submitted, the time of the end of th
 
 The purpose of this user is to adapt his interarrival rate. Each time a new job is submitted the waiting time is divided by two. Here is a example of gantt chart supposed to be created :
 
-![image](dicho.png)
+![image](images/dicho.png)
 
 ### routine_greedy
 Parameters required : time of the first job submitted, the time of the end of the submissions, delay between submits and the initial number of jobs. For instance :
@@ -33,7 +33,7 @@ Parameters required : time of the first job submitted, the time of the end of th
 
 The user connects routinely, every delay_between_sumbit. If all his jobs are finished, he submit twice as many. Otherwise he submits half as many.
 
-![image](routine_greedy.png)
+![image](images/routine_greedy.png)
 
 
 ### Think_time_only
@@ -44,7 +44,7 @@ Parameters required : time of the first job submitted, the time of the end of th
 
 When the job previously submitted finishes, the user is awaken by the broker then waits for some time (the `think_time`) before submitting the next one. Here is a example of gantt chart supposed to be created :
 
-![image](thinktimeonly.png)
+![image](images/thinktimeonly.png)
 
 ## Replay users
 There are 6 types of behaviors for replay users :
@@ -70,7 +70,7 @@ Parameters required : name of the user, category of the user (here replay_user_r
 
 This user will follow the input trace in a rigid fashion: they submit tasks of same size and at the same submission time as in the original trace. Here is a gantt chart of the expected results :
 
-![image](replay_rigid.png)
+![image](images/replay_rigid.png)
 
 ### dm_user_reconfig
 Parameters required : name of the user, category of the user (here dm_user_reconfig) and a json input.
@@ -84,7 +84,7 @@ Parameters required : name of the user, category of the user (here dm_user_recon
 The reconfiguration consists in dividing the number of cores requested by two (rounded up) and scaling the execution time accordingly, following the speedup model. Note: if the original number of cores requested was 1, reconfig is equivalent to rigid, and will appear as such in the logs.
 Here is a gantt chart of the expected results :
 
-![image](dm_reconfig.png)
+![image](images/dm_reconfig.png)
 
 ### dm_user_degrad_space
 Parameters required : name of the user, category of the user (here dm_user_degrad_space) and a json input.
@@ -98,7 +98,7 @@ Parameters required : name of the user, category of the user (here dm_user_degra
 The spatial degradation consists in dividing the number of cores requested by two (rounded up), keeping the original submission time. Note: if the original number of cores requested was 1, degrad is equivalent to rigid, and will appear as such in the logs.
 Here is a gantt chart of the expected results :
 
-![image](degrad_space.png)
+![image](images/degrad_space.png)
 
 We can notice that the gantt chart has not been modified hence it is the use of the machines that has been affected.
 
@@ -114,7 +114,7 @@ Parameters required : name of the user, category of the user (here dm_user_degra
 The temporal degradation consists in dividing the execution time by two.
 Here is a gantt chart of the expected results :
 
-![image](dm_degrad_temp.png)
+![image](images/dm_degrad_temp.png)
 
 For this behavior, we can clearly see that the time used by each session submitted in the demande response window has been divided by two.
 
@@ -130,7 +130,7 @@ Parameters required : name of the user, category of the user (here dm_user_renou
 Renouncing consists in simply not submitting the job (and never submit it in the future).
 Here is a gantt chart of the expected results :
 
-![image](dm_renounce.png)
+![image](images/dm_renounce.png)
 
 Here we can see that session 2 and session 3 have been renounced. Indeed, each job is renounced as soon as it is subimmted. However the think-time (2000) is preserved. Here's the timeline of this small example.
 The sessions 2 is submitted at 4000 but since it's in the demande respoonse window, it is renounced. After the think-time, at 6000 session 3 is submitted and renounced. Then at 8000 sessions 4 is also submitted and renounced. Sessions 4 is submittted outside of the window therefore we can see it on the gantt chart.
@@ -147,7 +147,7 @@ Parameters required : name of the user, category of the user (here dm_user_delay
 Delaying consists in not submitting the job straight away but at the end of the demand response window.
 Here is a gantt chart of the expected results :
 
-![image](dm_delay.png)
+![image](images/dm_delay.png)
 
 
 
@@ -178,7 +178,7 @@ Parameters required : name of the user, category of the user (here fb_reconfig)
 A user that replays an input trace, preserving the think time between sessions. During the DR window: reconfigure the jobs spatially.
 Here is a gantt chart of the expected results :
 
-![image](fb_reconfig.png)
+![image](images/fb_reconfig.png)
 
 ### fb_degrad_temp
 Parameters required : name of the user, category of the user (here fb_degrad_temp) and a SABjson input.
@@ -191,7 +191,7 @@ Parameters required : name of the user, category of the user (here fb_degrad_tem
 A user that replays an input trace, preserving the think time between sessions. During the DR window: degrades temporally the submitted jobs.
 Here is a gantt chart of the expected results :
 
-![image](fb_degrad_temp.png)
+![image](images/fb_degrad_temp.png)
 
 ### fb_degrad_space
 Parameters required : name of the user, category of the user (here fb_degrad_space) and a SABjson input.
@@ -205,7 +205,7 @@ Parameters required : name of the user, category of the user (here fb_degrad_spa
 A user that replays an input trace, preserving the think time between sessions. During the demand response window: degrades spatially the submitted jobs.
 Here is a gantt chart of the expected results :
 
-![image](fb_degrad_space.png)
+![image](images/fb_degrad_space.png)
 
 ### fb_renounce
 Parameters required : name of the user, category of the user (here fb_renounce) and a SABjson input.
@@ -219,7 +219,7 @@ Parameters required : name of the user, category of the user (here fb_renounce)
 A user that replays an input trace, preserving the think time between sessions. During the DR window: renounces all jobs.
 Here is a gantt chart of the expected results :
 
-![image](fb_renounce.png)
+![image](images/fb_renounce.png)
 
 ### fb_delay
 Parameters required : name of the user, category of the user (here fb_delay) and a SABjson input.
@@ -233,8 +233,4 @@ Parameters required : name of the user, category of the user (here fb_delay) and
 A user that replays an input trace, preserving the think time between sessions. During the DR window: delay the jobs to the end of the window.
 Here is a gantt chart of the expected results :
 
-![image](fb_delay.png)
-
-
-## Feedback and replay users
-TODO
+![image](images/fb_delay.png)
\ No newline at end of file