Differences

This shows you the differences between two versions of the page.

--- gettinstarted [2018/09/27 13:35] – [IMC] alberto
+++ gettinstarted [2023/09/06 11:21] (current) – external edit 127.0.0.1
@@ Line 15: / Line 15: @@
 </code>
 ==== DUNE ====
-All code and shared files are placed on a gitlab repository. You can find it here: [[https://gitlab.com/aurlab|AURlab Git]]. To get the code yourself, you clone it into your chosen folder.
+All code and shared files are placed on a gitlab repository. You can find it here: [[https://github.com/adallolio|Albertos Git]]. To get the code yourself, you clone it into your chosen folder.
 <code>
-mkdir aurlab
+mkdir dune_all
-cd aurlab
+cd dune_all
-git clone https://gitlab.com/aurlab/lsts_toolchain/dune.git
+git clone https://github.com/adallolio/dune.git
+cd dune/
+git checkout AutoNaut
+cd ..
 mkdir build
 cd build
 cmake ../dune
 make -j8
-cd ../dune
-git checkout projects/AutoNaut
 </code>
@@ Line 33: / Line 34: @@
 Now, clone and build Neptus.
 <code>
-cd aurlab
+git clone https://github.com/adallolio/neptus.git
-git clone https://gitlab.com/aurlab/lsts_toolchain/neptus.git
 cd neptus
+git checkout AutoNaut
 ant
 </code>
@@ Line 42: / Line 43: @@
 <code>
-git checkout projects/AutoNaut
+git checkout AutoNaut
 ./neptus.sh
 </code>
@@ Line 49: / Line 50: @@
 ==== IMC ====
-cd aurlab
-git clone https://gitlab.com/aurlab/lsts_toolchain/imc.git
-==== Working with DUNE ====
-To start DUNE, you need to choose a configuration file (that is, a .ini-file). These files are placed under the // /etc//-folder. Before you write anything in DUNE, make sure you make your own //branch//.
 <code>
-cd aurlab
+git clone https://github.com/adallolio/imc.git
-cd dune
+cd imc/
-git checkout -b the-branch-you-work-on
+git checkout AutoNaut
 </code>
-Now you should have moved to your own branch. Every time you make something new on your branch, or do some major updates (minimum once a day), you should commit your changes.
-To run DUNE using your specific config file, you write
+==== Working with DUNE ====
+To start DUNE, you need to choose a configuration file (that is, a .ini-file). These files are placed under the // /etc//-folder. Assuming you are in the correct branch (AutoNaut), you can run simulations by typing
 <code>
-cd build
+./dune -c ntnu-autonaut -p Simulation
-cmake ../dune
-./dune -c name.ini
 </code>
@@ Line 95: / Line 87: @@
 </code>
-It could be wise to follow the tutorial on [[https://github.com/LSTS/dune/wiki|LSTS Dune Tutorials]]. The tasks communicate using IMC Messages. Read more about them on [[software:imc|IMC]]. To make debugging easier, you can code your printouts as //err//, //war//, //inf// and //cri//:
+It could be wise to follow the tutorial on [[https://github.com/LSTS/dune/wiki|LSTS Dune Tutorials]]. The tasks communicate using IMC Messages. Read more about them on [[https://lsts.fe.up.pt/toolchain/imc|IMC]]. To make debugging easier, you can code your printouts as //err//, //war//, //inf// and //cri//:
 <code>
@@ Line 104: / Line 96: @@
 ==== Cross-compiling dune ====
-To be able to use dune on an on-board platform, you need to cross-compile it and have a version of Glued on your on-board computer. See [[software:glued|Glued]] for description of how this is done.
+To be able to use dune on an on-board platform, you need to cross-compile it and have a version of Glued on your on-board computer. See [[https://lsts.fe.up.pt/toolchain/glued|GLUED]] for description of how this is done.