Deployed a0d5426 to 0.1 with MkDocs 1.1.2 and mike 0.5.5

0.1/file-structure/index.html

@@ -803,7 +803,7 @@
 <p>All the source code is saved in <code>src/</code>. The <code>src/data/</code> folder stores scripts to download, clean and pre-process sensor data, <code>src/features</code> has scripts to extract behavioral features organized in their respective subfolders , <code>src/models/</code> can host any script to create models or statistical analyses with the behavioral features you extract, and <code>src/visualization/</code> has scripts to create plots of the raw and processed data.</p>
 <p>There are other important files and folders but only relevant if you are interested in extending RAPIDS (e.g. virtual env files, docs, tests, Dockerfile, the Snakefile, etc.). In the figure below, we represent the interactions between users and files. After a user modifies <code>config.yaml</code> and <code>.env</code> the <code>Snakefile</code> file will decide what Snakemake rules have to be executed to produce the required output files (behavioral features) and what scripts are in charge of producing such files. In addition, users can add or modifiy files in the <code>data</code> folder (for example to configure the <a href="../setup/configuration/#participant-files">participants files</a> or the <a href="../setup/configuration/#day-segments">day segment files</a>).</p>
 <figure>
-  <img src="/img/files.png" width="600" />
+  <img src="../img/files.png" width="600" />
   <figcaption>Interaction diagram between the user, and important files in RAPIDS</figcaption>
 </figure>
                 

latest/file-structure/index.html

@@ -803,7 +803,7 @@
 <p>All the source code is saved in <code>src/</code>. The <code>src/data/</code> folder stores scripts to download, clean and pre-process sensor data, <code>src/features</code> has scripts to extract behavioral features organized in their respective subfolders , <code>src/models/</code> can host any script to create models or statistical analyses with the behavioral features you extract, and <code>src/visualization/</code> has scripts to create plots of the raw and processed data.</p>
 <p>There are other important files and folders but only relevant if you are interested in extending RAPIDS (e.g. virtual env files, docs, tests, Dockerfile, the Snakefile, etc.). In the figure below, we represent the interactions between users and files. After a user modifies <code>config.yaml</code> and <code>.env</code> the <code>Snakefile</code> file will decide what Snakemake rules have to be executed to produce the required output files (behavioral features) and what scripts are in charge of producing such files. In addition, users can add or modifiy files in the <code>data</code> folder (for example to configure the <a href="../setup/configuration/#participant-files">participants files</a> or the <a href="../setup/configuration/#day-segments">day segment files</a>).</p>
 <figure>
-  <img src="/img/files.png" width="600" />
+  <img src="../img/files.png" width="600" />
   <figcaption>Interaction diagram between the user, and important files in RAPIDS</figcaption>
 </figure>