New iteration png to jpg

Docs/adv_opendrive.md

@@ -21,7 +21,7 @@ Traffic lights, stops and yields will be generated on the fly. Pedestrians will
 !!! Important
     It is especially important to double check the OpenDRIVE file. Any issues in it will propagate when running the simulation.
 
-![opendrive_standalone](img/opendrive_standalone.png)
+![opendrive_standalone](img/opendrive_standalone.jpg)
 
 ---
 ## Run a standalone map
@@ -55,7 +55,7 @@ python3 config.py -x opendrive/TownBig.xodr
 
 The generation of the mesh is the key element of this mode. The feature can only be successful if the resulting mesh is smooth and fits its definition perfectly. For that reason, this step is constantly being improved. In the last iterations, junctions have been polished to avoid inaccuracies that occur, especially where uneven lanes joined.  
 
-![opendrive_meshissue](img/opendrive_meshissue.png)
+![opendrive_meshissue](img/opendrive_meshissue.jpg)
 <div style="text-align: right"><i>When generating junction meshes, higher lanes tend to block the ones below them. <br>The parameter <code>smooth_junctions</code> prevents this kind of issue.</i></div>
 
 Besides that, instead of creating the whole map as a unique mesh, different portions are created. By dividing the mesh, the simulator can avoid rendering portions that are not visible, and save up costs. Working smaller also allows to generate huge maps and contain issues that may occur on a small portion of the mesh.

Docs/adv_ptv.md

@@ -46,7 +46,7 @@ In order for a new PTV-Vissim network to run with CARLA, there are a few setting
 * __Specify the vehicle and pedestrian types__. These are the types that will be used in PTV-Vissim to sync with the spawnings done in CARLA. By default are empty.  
 * __Export the network as `.inpx`__. Create the network, export it, and run the co-simulation with `run_synchronization.py`.  
 
-![ptv_types](img/ptv_types.png)
+![ptv_types](img/ptv_types.jpg)
 <div style="text-align: right"><i>Any vehicle that is spawned in CARLA, will be spawned in PTV-Vissim using these types.</i></div>
 
 !!! Warning

Docs/adv_traffic_manager.md

@@ -39,7 +39,7 @@ The following diagram is a summary of the internal architecture of the Traffic M
 The inner structure of the TM can be easily translated to code. Each relevant element has its equivalent in the C++ code (.cpp files) inside `LibCarla/source/carla/trafficmanager`. 
 
 <div style="text-align:center">
-<img src="../img/traffic_manager_diagram.png">
+<img src="../img/traffic_manager_diagram.jpg">
 </div>
 
 ### Stages

Docs/build_system.md

@@ -11,7 +11,7 @@ The most challenging part of the setup is to compile all the dependencies and mo
 
 The goal is to be able to call Unreal Engine's functions from a separate Python process.
 
-![modules](img/modules.png)
+![modules](img/build_modules.jpg)
 
 In Linux, we compile CARLA and all the dependencies with clang-8.0 and C++14 standard. We however link against different runtime C++ libraries depending on where the code going to be used, since all the code that is going to be linked with Unreal Engine needs to be compiled using `libc++`.
 

Docs/core_map.md

@@ -250,7 +250,7 @@ So far there are seven different maps available. Each one has unique features an
   </div>
 
   <div class="townslide fade">
-    <img src="../img/Town10.png">
+    <img src="../img/Town10.jpg">
     <div class="text">Town10</div>
   </div>