slight update of the docu

Author: markusgft

ct_doc/doc/ct_doc.doxyfile

@@ -38,7 +38,7 @@ PROJECT_NAME           = ct
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = v2.3
+PROJECT_NUMBER         = v3.0
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a

ct_doc/doc/developer_info.dox

@@ -10,13 +10,6 @@ to align the development with ongoing activities.
 \section Code Formatting
 We support clang-format and provide a style template to automatically format the source code. 
 Please refer to the clang-format style sheet in the package root directory for our conventions. 
-Or simply rely on clang-format to do the formatting for you.
-
-Note for developers using the *Eclipse IDE*: you can conveniently integrate clang-format (and our .clang-format 
-configuration file) in your project using the "CppStyle" plugin (see http://www.cppstyle.com/ for 
-detailed information). To automatically format the code according to ct-style, just mark the source-code 
-and press *Ctrl+Shift+f*.
-
 
 Example command for running clang-tidy:
 \code

ct_doc/doc/installation.dox

@@ -29,15 +29,14 @@ library versions as provided in the package sources.
 The following dependencies and bindings are optional but can help to enhance the functionality or performance of the CT
 
  - <a href="http://www.netlib.org/lapack/">lapack</a> (enables Schur method as an alternative to iterative method in ct::optcon::LQR)
+ \code{.sh} $ sudo apt-get install liblapack-dev \endcode
 
  - <a href="https://clang.llvm.org/">clang</a> compiler (faster compilation for large linear models), install from command-line via
  \code{.sh} $ sudo apt-get install clang \endcode
  and possibly replace `clang` with a more specific version, e.g. `clang-3.8`.
  Please make sure that the `clang` and `clang++` commands are in your path.
  You may need to create a symbolic link in `/usr/bin` or use a bash alias.
 
- - <a href="http://wiki.ros.org/indigo">ROS Indigo</a> or <a href="http://wiki.ros.org/kinetic">Kinetic</a> (for ROS bindings, visualization and extended examples), see <a href="../../../../ct_ros/ct_ros_nodes/doc/html/index.html">ct_ros_nodes</a>, <a href="../../../../ct_ros/ct_ros_nodes/doc/html/index.html">ct_ros_msgs</a>
-
  - <a href="https://projects.coin-or.org/Ipopt">IPOPT</a> or <a href="http://www.sbsi-sol-optimize.com/asp/sol_product_snopt.htm">SNOPT</a>
   (for ct::optcon::SnoptSolver and ct::optcon::IpoptSolver as used by ct::optcon::DMS)
 

ct_doc/doc/mainpage.dox

@@ -6,7 +6,7 @@
 
 \section ct1 Control Toolbox
 
-This is the ADRL Control Toolbox ('CT'), an open-source C++ library for efficient modelling, control, 
+The Control Toolbox ('CT'), an open-source C++ library for efficient modelling, control, 
 estimation, trajectory optimization and model predictive control.
 The CT is applicable to a broad class of dynamic systems, but features additional modelling tools specially designed for robotics.
 This page outlines its general concept, its major building blocks and highlights selected application examples.
@@ -47,7 +47,7 @@ The CT was designed with the following features in mind:
     - all algorithm flavors and solver backends are available through simple configuration files.
 
 
-The CT is hosted on bitbucket: <a href="https://bitbucket.org/adrlab/ct" target="_blank">https://bitbucket.org/adrlab/ct</a>
+The CT is hosted on github: <a href="https://github.com/ethz-adrl/control-toolbox" target="_blank">https://github.com/ethz-adrl/control-toolbox</a>
 
 
 
@@ -212,11 +212,6 @@ The four different main modules are detailed in the following.
  - <a href="../../../ct_models/doc/html/index.html">quick link to ct_models</a>
 
 
-\section source_code Source Code
-
-The source code is available at <a href="https://bitbucket.org/adrlab/ct" target="_blank">https://bitbucket.org/adrlab/ct</a>
-
-Examples for interfacing with ROS and advanced application examples are available at <a href="https://bitbucket.org/adrlab/ct_ros/src/master/" target="_blank">ct_ros</a>.
 
 \section gs How to use the Control Toolbox
 
@@ -226,15 +221,15 @@ To get started with the control toolbox, please see \ref getting_started "Gettin
 \section contact Support
 
 For any questions, issues or other troubleshooting please either
-- create an issue: https://bitbucket.org/adrlab/ct/issues
+- create an issue: https://github.com/ethz-adrl/control-toolbox/issues
 - contact the devs: control-toolbox-dev@googlegroups.com
 
 
 \section ct_doc_acknowledgement Acknowledgements
 
 \subsection contribs Contributors
- - Michael Neunert
  - Markus Giftthaler
+ - Michael Neunert
  - Markus Stäuble
  - Farbod Farshidian
  - Diego Pardo
@@ -243,12 +238,11 @@ For any questions, issues or other troubleshooting please either
  - Ruben Grandia
  - Hamza Merzic
 
-\subsection lead_overview Project Lead and Maintenance 
- - Michael Neunert, neunertm (at) gmail (dot) com
+\subsection lead_overview Maintenance 
  - Markus Giftthaler, markusgft (at) gmail (dot) com
 
-\subsection funding Funding
-This software has been developed at the <a href="http://www.adrl.ethz.ch" target="_blank">Agile & Dexterous Robotics Lab</a> 
+\subsection funding Funding 2014-2018
+The core of this software has been developed at the <a href="http://www.adrl.ethz.ch" target="_blank">Agile & Dexterous Robotics Lab</a> 
 at <a href="http://www.ethz.ch/en" target="_blank">ETH Zurich</a>, Switzerland between 2014 and 2018.
 During that time, development has been made possible through financial support from the <a href="http://www.snf.ch/en/" target="_blank">Swiss National Science Foundation (SNF)</a> 
 through a SNF Professorship award to Jonas Buchli and the National Competence Centers in Research (NCCR) 

ct_doc/doc/tags/.gitkeep

@@ -38,7 +38,7 @@ PROJECT_NAME           = ct_models
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = v2.3
+PROJECT_NUMBER         = v3.0
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a

ct_models/doc/ct_models.doxyfile

@@ -38,7 +38,7 @@ PROJECT_NAME           = ct_optcon
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = v2.3
+PROJECT_NUMBER         = v3.0
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a

ct_optcon/doc/ct_optcon.doxyfile

@@ -38,7 +38,7 @@ PROJECT_NAME           = ct_rbd
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = v2.3
+PROJECT_NUMBER         = v3.0
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a