Replace "felk" for "fel"

Author: filipopo

docs/120-miscellaneous/3d_model_processing/10-cloudcompare.md

@@ -46,7 +46,7 @@ Used for data processing before meshing and texturing.
 
 [CC command line mode](https://www.cloudcompare.org/doc/wiki/index.php?title=Command_line_mode) opens a way for scripting of most of the functions available within CC GUI.
 **Scripting is faster than GUI and provides repeatability: prefer scripting over GUI.**
-Example script is available [here](https://mrs.felk.cvut.cz/gitlab/NAKI/naki_postprocessing/blob/master/scripts/pointclouds/processPtxFiles.sh).
+Example script is available [here](https://mrs.fel.cvut.cz/gitlab/NAKI/naki_postprocessing/blob/master/scripts/pointclouds/processPtxFiles.sh).
 Example command merging two `.ptx` files, exporting them to `.ply`, sampling the data to resolution of 2 cm and exporting the sampled data to `.ply`:
 ```bash
 CloudCompare -AUTO_SAVE OFF -O Setup249.ptx -O Setup250.ptx -MERGE_CLOUDS -C_EXPORT_FMT PLY -SAVE_CLOUDS FILE "merge_raw.ply" -SS SPATIAL 0.02 -SAVE_CLOUDS FILE "merge_raw_sampled_2cm.ply"

docs/120-miscellaneous/3d_model_processing/30-meshlab.md

@@ -137,8 +137,8 @@ The pointcloud vertex color might not be detailed enough for the whole model or
 
 #### Create whole model
 
-  * **This method is not automatized, only proof of concept.** The method assume having precise position of the images w.r.t. the model. The files for this project are available [here](https://nasmrs.felk.cvut.cz/index.php/apps/files/?dir=/shared/3D_models/raster_texture_example).
-  * Use either [CloudCompare](https://ctu-mrs.github.io/docs/software/3d_model_processing/cloudcompare.html#extracting-images) or [VoxelizeE57Files](https://mrs.felk.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master) package to extract images.
+  * **This method is not automatized, only proof of concept.** The method assume having precise position of the images w.r.t. the model. The files for this project are available [here](https://nasmrs.fel.cvut.cz/index.php/apps/files/?dir=/shared/3D_models/raster_texture_example).
+  * Use either [CloudCompare](https://ctu-mrs.github.io/docs/software/3d_model_processing/cloudcompare.html#extracting-images) or [VoxelizeE57Files](https://mrs.fel.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master) package to extract images.
   * Open the MeshLab and import the mesh model, you would like to texture with `File->Import Mesh...`. The model do not need parametrization.
   * Import all raster images `File->Import Raster...`
   * **Recommend to save the MeshLab project `.mlp` as much as you can. MeshLab likes to crash.**
@@ -191,7 +191,7 @@ ViewportPx="2048 2048"
 FocalMm="6.141"
 ```
 
-* Values are obtained from both CloudCompare `Camera Sensor` output and [VoxelizeE57Files](https://mrs.felk.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master) package running with `--only-export-images` option.
+* Values are obtained from both CloudCompare `Camera Sensor` output and [VoxelizeE57Files](https://mrs.fel.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master) package running with `--only-export-images` option.
 * Copy the whole `.xml` snippet and select `Windows->Paste clipboard to camera setting`.
 * You should be able to see the change in the camera perspective.
 * If you copy again the current value of the camera with `Windows->Copy camera settings to clipboard`, the values are different since MeshLab recalculates the imported values. Values are correct. Here is the example of such a snippet
@@ -230,7 +230,7 @@ FocalMm="6.141"
 ```
 
 * These values represent the Leica BLK 360 camera sensor as described in the previous chapter even the values do not match. MeshLab recalculates the values for its own projection.
-* To correct the camera sensor position and orientation, check the [extract sensor position](https://ctu-mrs.github.io/docs/software/3d_model_processing/cloudcompare.html#extracting-sensor-positions) guide or [VoxelizeE57Files](https://mrs.felk.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master) package. *Note: Not sure if VoxelizeE57Files gives the same transformation.*
+* To correct the camera sensor position and orientation, check the [extract sensor position](https://ctu-mrs.github.io/docs/software/3d_model_processing/cloudcompare.html#extracting-sensor-positions) guide or [VoxelizeE57Files](https://mrs.fel.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master) package. *Note: Not sure if VoxelizeE57Files gives the same transformation.*
 * Correct the values in `cameras.xml` configuration file for the `cameras` tag for each image as below:
 
 ```xml

docs/120-miscellaneous/3d_model_processing/60-fixing_colors.md

@@ -16,7 +16,7 @@ Export
   - 1 structured `.e57` file with *N* low-res clouds, origins and images
   - *N* unstructured `.e57` files with full-point clouds.
 
-1. Merge unstructured data with [VoxelizeE57FilesByOriginDistance](https://mrs.felk.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master)
+1. Merge unstructured data with [VoxelizeE57FilesByOriginDistance](https://mrs.fel.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master)
   - voxelizes data to desired resolution
   - final voxel stores by default a point with the lowest distance from the scanning origin (origin parsed from the structured `.e57` file)
   - filters out measurements with respect to the sensor accuracy

docs/120-miscellaneous/3d_model_processing/99-export.md

@@ -26,8 +26,8 @@ Most of the times, the models are saved in following formats
 
 ## Web
 
-* The basic guide will be described here. Please follow the [original guide](https://mrs.felk.cvut.cz/gitlab/bednaj14/meshlab/blob/master/modely_report.pdf) and the scripts inside for detailed information.
-* Download the [obj2optimizedGlb.sh](https://mrs.felk.cvut.cz/gitlab/bednaj14/meshlab/blob/master/obj2optimizedGlb.sh) script.
+* The basic guide will be described here. Please follow the [original guide](https://mrs.fel.cvut.cz/gitlab/bednaj14/meshlab/blob/master/modely_report.pdf) and the scripts inside for detailed information.
+* Download the [obj2optimizedGlb.sh](https://mrs.fel.cvut.cz/gitlab/bednaj14/meshlab/blob/master/obj2optimizedGlb.sh) script.
 * Recommend to install `NodeJS` with [snapcraft](https://snapcraft.io/node) tool. The `apt` version for `Ubuntu` does not contain the up-to-date version.
 * The convert tool needs to have max *16384x16384* texture. Otherwise it will not work.
   * *Note: In general, it is better to have several lower size texture files than a single large one.*

docs/120-miscellaneous/latex.md

@@ -11,7 +11,7 @@ description: Syncing overleaf with a git repository
   * **Note:** you must login with an email and password and not through a Google account. It is needed to push to the overleaf afterward since it doesn't support SSH keys by default.
 2. Get git link:
   * Once you've created a project, go to the menu, in the section called ```Sync``` you can find ```Git```. Go there.
-    * If you have created a new account, this feature will be paid only. For this purpose you have to use our shared credentials, see on this page "Overleaf credentials" [here](http://mrs.felk.cvut.cz/internal), use them to log in and get GitLab link.
+    * If you have created a new account, this feature will be paid only. For this purpose you have to use our shared credentials, see on this page "Overleaf credentials" [here](http://mrs.fel.cvut.cz/internal), use them to log in and get GitLab link.
   * This will open a pop-up window with ``git clone https://git.overleaf.com/<your overleaf project link>``. Copy the ``https...`` link.
 
 3. Sync your repo:

docs/50-features/20-trackers/index.md

@@ -26,7 +26,7 @@ This page is describing the upcoming ROS2 version of the MRS UAV System (however
 * "MPC tracker"
   * the main *workhorse* of the [MRS UAV System](https://github.com/ctu-mrs/mrs_uav_system), it is used for most of the regular flying
   * based on a unique *realtime simulated Model Predictive Control* approach
-  * originally published in: `Baca, et al., "Model Predictive Trajectory Tracking and Collision Avoidance for Reliable Outdoor Deployment of Unmanned Aerial Vehicles", IROS 2018`, [link](http://mrs.felk.cvut.cz/data/papers/baca-mpc-tracker.pdf)
+  * originally published in: `Baca, et al., "Model Predictive Trajectory Tracking and Collision Avoidance for Reliable Outdoor Deployment of Unmanned Aerial Vehicles", IROS 2018`, [link](http://mrs.fel.cvut.cz/data/papers/baca-mpc-tracker.pdf)
   * produces feasible reference which is smooth up to snap and satisfies given state constraints.
   * can smoothly track trajectories
   * can efficiently stop a UAV from any previous motion

docs/60-simulations/30-FlightForge/01-installation.md

@@ -19,7 +19,7 @@ The FlightForge simulator is composed of two main parts - the simulator itself e
 
 ## FlightForge Simulator 
 
-The prebuild binaries of the simulator can be downloaded from the [here](https://nasmrs.felk.cvut.cz/index.php/s/MnGARsSwnpeVy5z). 
+The prebuild binaries of the simulator can be downloaded from the [here](https://nasmrs.fel.cvut.cz/index.php/s/MnGARsSwnpeVy5z). 
 The simulator is available for Linux and Windows, the simulator can be run by running the binary file `mrs_flight_forge.sh` in the downloaded archive.
 The binary provides the simulator as a standalone application that can be run without the need of Unreal Engine.
 However, if you wish to create a custom environment or modify the simulator you can download our Unreal Engine plugin from [flight_forge repository](https://github.com/ctu-mrs/flight_forge/), and place it in the `Plugins` folder of your Unreal Engine project.

docusaurus.config.ts

@@ -126,7 +126,7 @@ const config: Config = {
           position: 'right',
         },
         {
-          href: 'http://mrs.felk.cvut.cz',
+          href: 'http://mrs.fel.cvut.cz',
           label: 'CTU MRS',
           position: 'right',
         },
@@ -165,7 +165,7 @@ const config: Config = {
             },
             {
               label: 'CTU MRS Group',
-              href: 'https://mrs.felk.cvut.cz',
+              href: 'https://mrs.fel.cvut.cz',
             }
           ],
         },

versioned_docs/version-1.5.0/120-miscellaneous/3d_model_processing/10-cloudcompare.md

@@ -46,7 +46,7 @@ Used for data processing before meshing and texturing.
 
 [CC command line mode](https://www.cloudcompare.org/doc/wiki/index.php?title=Command_line_mode) opens a way for scripting of most of the functions available within CC GUI.
 **Scripting is faster than GUI and provides repeatability: prefer scripting over GUI.**
-Example script is available [here](https://mrs.felk.cvut.cz/gitlab/NAKI/naki_postprocessing/blob/master/scripts/pointclouds/processPtxFiles.sh).
+Example script is available [here](https://mrs.fel.cvut.cz/gitlab/NAKI/naki_postprocessing/blob/master/scripts/pointclouds/processPtxFiles.sh).
 Example command merging two `.ptx` files, exporting them to `.ply`, sampling the data to resolution of 2 cm and exporting the sampled data to `.ply`:
 ```bash
 CloudCompare -AUTO_SAVE OFF -O Setup249.ptx -O Setup250.ptx -MERGE_CLOUDS -C_EXPORT_FMT PLY -SAVE_CLOUDS FILE "merge_raw.ply" -SS SPATIAL 0.02 -SAVE_CLOUDS FILE "merge_raw_sampled_2cm.ply"

versioned_docs/version-1.5.0/120-miscellaneous/3d_model_processing/30-meshlab.md

@@ -137,8 +137,8 @@ The pointcloud vertex color might not be detailed enough for the whole model or
 
 #### Create whole model
 
-  * **This method is not automatized, only proof of concept.** The method assume having precise position of the images w.r.t. the model. The files for this project are available [here](https://nasmrs.felk.cvut.cz/index.php/apps/files/?dir=/shared/3D_models/raster_texture_example).
-  * Use either [CloudCompare](https://ctu-mrs.github.io/docs/software/3d_model_processing/cloudcompare.html#extracting-images) or [VoxelizeE57Files](https://mrs.felk.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master) package to extract images.
+  * **This method is not automatized, only proof of concept.** The method assume having precise position of the images w.r.t. the model. The files for this project are available [here](https://nasmrs.fel.cvut.cz/index.php/apps/files/?dir=/shared/3D_models/raster_texture_example).
+  * Use either [CloudCompare](https://ctu-mrs.github.io/docs/software/3d_model_processing/cloudcompare.html#extracting-images) or [VoxelizeE57Files](https://mrs.fel.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master) package to extract images.
   * Open the MeshLab and import the mesh model, you would like to texture with `File->Import Mesh...`. The model do not need parametrization.
   * Import all raster images `File->Import Raster...`
   * **Recommend to save the MeshLab project `.mlp` as much as you can. MeshLab likes to crash.**
@@ -191,7 +191,7 @@ ViewportPx="2048 2048"
 FocalMm="6.141"
 ```
 
-* Values are obtained from both CloudCompare `Camera Sensor` output and [VoxelizeE57Files](https://mrs.felk.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master) package running with `--only-export-images` option.
+* Values are obtained from both CloudCompare `Camera Sensor` output and [VoxelizeE57Files](https://mrs.fel.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master) package running with `--only-export-images` option.
 * Copy the whole `.xml` snippet and select `Windows->Paste clipboard to camera setting`.
 * You should be able to see the change in the camera perspective.
 * If you copy again the current value of the camera with `Windows->Copy camera settings to clipboard`, the values are different since MeshLab recalculates the imported values. Values are correct. Here is the example of such a snippet
@@ -230,7 +230,7 @@ FocalMm="6.141"
 ```
 
 * These values represent the Leica BLK 360 camera sensor as described in the previous chapter even the values do not match. MeshLab recalculates the values for its own projection.
-* To correct the camera sensor position and orientation, check the [extract sensor position](https://ctu-mrs.github.io/docs/software/3d_model_processing/cloudcompare.html#extracting-sensor-positions) guide or [VoxelizeE57Files](https://mrs.felk.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master) package. *Note: Not sure if VoxelizeE57Files gives the same transformation.*
+* To correct the camera sensor position and orientation, check the [extract sensor position](https://ctu-mrs.github.io/docs/software/3d_model_processing/cloudcompare.html#extracting-sensor-positions) guide or [VoxelizeE57Files](https://mrs.fel.cvut.cz/gitlab/NAKI/naki_postprocessing/tree/master) package. *Note: Not sure if VoxelizeE57Files gives the same transformation.*
 * Correct the values in `cameras.xml` configuration file for the `cameras` tag for each image as below:
 
 ```xml