gettinstarted

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
gettinstarted [2020/09/09 16:31] – [Neptus] albertogettinstarted [2023/09/06 11:21] (current) – external edit 127.0.0.1
Line 51: Line 51:
 ==== IMC ==== ==== IMC ====
 <code> <code>
-cd aurlab 
 git clone https://github.com/adallolio/imc.git git clone https://github.com/adallolio/imc.git
 cd imc/ cd imc/
Line 58: Line 57:
  
 ==== Working with DUNE ==== ==== 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 DUNEmake sure you make your own //branch//.+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> <code>
-cd aurlab +./dune -c ntnu-autonaut -p Simulation
-cd dune +
-git checkout -b the-branch-you-work-on +
-</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  +
- +
-<code> +
-cd build +
-cmake ../dune +
-./dune -c name.ini+
 </code> </code>
  
  • gettinstarted.1599661897.txt.gz
  • Last modified: 2023/09/06 00:32
  • (external edit)