Tips

This page has not been updated. However almost all explanations are fully relevant.

Organization tip

The user path contains the Multivac-x.y directory which contains the includes directory (the library which has not to be modified to use Multivac), the main track.cpp which has to be changed for any new simulation (because it gives the simulation function the datas, the arguments needed) and the makefile (which indicates to the compiler where to find the different files and how to manage the compilation). As the includes directory is never changed, it is really convenient to create a new directory in the user path: runs in which we will process any new simulation. In this runs directory, let's create other directories run1, run2 ... In each, we just put a copy of the makefile (cf section one first), a copy of track.cpp and a new directory, called output for example, in which we will store all the output files created during the simulation: Curves, X, Y, Points, Edges, Phi, F... We will also put the different matlab functions in this output directory to display these outputs with the graphic tools of Matlab (see next section).
In each directory runk (k is the number of the run), we just have to change track.cpp to realize the simulation we need, with the parameters and the types of inputs we want.
We just have to change the directory of the ouput files in track.cpp (cf previous section) and set it to:
" userpath/runs/runk/output/ " to have our outputs in the expected directory. The makefile has not to be modified since track.cpp is in the same directory (otherwise we need the complete path of the file track.cpp in the makefile) and the path of the "includes" given to the makefile is the same than the previous one: /userpath/Multivac-x.y/includes.

Here is a scheme representing this very convenient file organization.


File organization


With this organization, we can do as many different simulations as we whish (there is a different track.cpp in each "run" directory) and keep the results of simulation number k in the runk/output directory.
We also have only one copy of the Multivac library (the includes directory) for all the simulations (indeed, the makefile in runk tells the compiler to go and search the "includes" needed in the directory /userpath/Multivac-x.y/includes).