Ruben Martinez-Cantin committed b7d5598

Corrected formatting

Comments (0)

Files changed (1)

 It can be used as an example of the interfaces that bayesian-optimization provide.
 There are three kind of interfaces.
-2.1 - C functional usage
+==== 2.1 - C functional usage ==== 
 This interface is fully functional from C and C++. It resembles the classic 
 NLOPT interface, therefore, NLOPT manual can used as well. We just need to 
 in the current implementation, it is not used. You can just use a NULL pointer.
-2.2 - C++ polymorphic usage
+==== 2.2 - C++ polymorphic usage ==== 
 The second way to use the function is by creating an object that inherits 
 from the Krigging object defined in krigging.hpp
 Note that the checkReachability function has been included for future 
 compatibility, although in the current implementation, it is not used.
-2.3 - Python functional usage
+==== 2.3 - Python functional usage ====
 The file bin/ provides an example of the Python interface. It is similar
 the C interface. The parameters must be defined as a Python dictionary.
 === 3 -  DEPENDENCIES: ===
-3.1 - BOOST:
+==== 3.1 - BOOST: ====
 This code uses Boost libraries for matrix operations (uBlas) and random
 number generation. They can be found in standard linux distributions or
 They are not very efficient, so it may change in future versions.
-3.2 - DIRECT:
+==== 3.2 - DIRECT: ====
 This library requires some other nonlinear optimization library 
 (e.g.: DIRECT). 
-a) Using Fortran DIRECT:
+===== a) Using Fortran DIRECT: =====
 For completeness, it includes a Fortran 77 implementation of the
 DIRECT-L algorithm by J. Gablonsky
 This code has only been tested using gcc and libgfortran. Due to some
 limitations of the F77 compiler, it doesn't work in 64bit OS.
-b) Using NLOPT (default):
+===== b) Using NLOPT (default): =====
 We recommend the use of NLOPT for the inner loop optimization. The latest
 version can be downloaded from 
 NLOPT does not require external libraries and it is compatible with 
 Windows and Mac. Although compiling it in Windows is tricky.
-3.3 - PYTHON:
+==== 3.3 - PYTHON: ====
 The library has been tested with Python 2.6.
+=== 4. KNOWN ISSUES ===
 - In some systems, the linker is not able to find the shared libraries. You
 just need to point the LD_LIBRARY_PATH and PYTHONPATH to the corresponding