Troubleshooting


This page presents frequent problems as a FAQ list. This list is (very) far from being comprehensive. I plan to incorporate users questions as they arise. In case your problem is not addressed in the present page, feel free to send me an email.

Compilation problems

  1. I get one of the following error message
    make: Fatal error in reader: makefile, line 101: Unexpected end of line seen
    make: Fatal error in reader: makefile, line 91: Read of include file `.config' failed
  2. I get the following warning:
    makefile:91: .config: No such file or directory

Runtime problems
  1. I get an error message similar to the following, and fargo quits:
    Error : can't find 'Jup.cfg'.
  2. The OpenMP executable of FARGO is extremely slow at runtime.
Compilation problems
  1. I get one of the following error message
    make: Fatal error in reader: makefile, line 101: Unexpected end of line seen
    make: Fatal error in reader: makefile, line 91: Read of include file `.config' failed
    You should use 'gmake' instead of 'make'.
  2. I get the following warning:
    makefile:91: .config: No such file or directory
    Just ignore this warning: it happens at the very first built,  because the '.config' file does not exist yet.
Runtime problems
  1. I get an error message similar to the following, and fargo quits.
    Error : can't find 'Jup.cfg'.
    Either the planetary system configuration file addressed by PlanetConfig in your parameter file does not exist, or the path to it is incorrect.
  2. The OpenMP executable of FARGO is extremely slow at runtime.
    Depending on your platform, you may need to add in the 'src/mp.h' file the following line:
    #include <omp.h>
    Also, you may check the impact of the following environment variables:
    export OMP_DYNAMIC=FALSE
    export OMP_NUM_THREADS=2 (or 3, 4, etc.)
    (change 'EXPORT xxx=yyyy' with 'setenv xxx yyyy' if you work under tcsh rather than bash)
    The first affectation above prevents an automatic evaluation of the number of threads over which your
    process is split. The second one explicitely tells how many threads you want in your OpenMP sections.
    It is a good idea to set this number to the number of processors available and reserved for your run.