\cond \endcond

Control is a C++ (template) library that provides a suite of control algorithms. The algorithms are implemented in a generic fashion. A CMake module is available to make it easy to include Control in other CMake-based projects: Findcontrol.cmake.

• Header-only
• Full suite of tests

To install this project, please ensure that you have installed the following (install guides are provided on the respective websites):

• Git
• A C++ compiler, e.g., GCC, clang, MinGW
• CMake
• Doxygen (optional)
• Gcov (optional)
• LCOV (optional)

In addition, Control depends on the following libraries:

• SML (maths library)
• CATCH (unit testing library necessary for BUILD_TESTS option)
• Eigen (linear algebra library necessary for BUILD_TESTS_WITH_EIGEN option)

These dependencies will be downloaded and configured automagically if not already present locally (requires an internet connection).

Run the following commands to download, build, and install this project.

git clone https://www.github.com/openastro/control
cd control
git submodule init && git submodule update
mkdir build && cd build
cmake .. && cmake --build .

To install the header files, run the following from within the build directory:

make install

Note that dependencies are installed by fetching them online, in case they cannot be detected on your local system. If the build process fails, check the error log given. Typically, building fails due to timeout. Simply run the cmake --build . command once more.

You can pass the following, general command-line options when running CMake:

• -DCMAKE_INSTALL_PREFIX[=$install_dir]: set path prefix for install script (make install); if not set, defaults to usual locations
• -DBUILD_DOXYGEN_DOCS[=ON|OFF (default)]: build the Doxygen documentation (LaTeX must be installed with amsmath package)
• -DBUILD_TESTS[=ON|OFF (default)]: build tests (execute tests from build-directory using ctest -V)
• -DBUILD_DEPENDENCIES[=ON|OFF (default)]: force local build of dependencies, instead of first searching system-wide using find_package()

The following commands are conditional and can only be set if BUILD_TESTS = ON:

• -DBUILD_TESTS_WITH_EIGEN[=ON|OFF (default)]: build tests using Eigen (execute tests from build-directory using ctest -V)
• -DBUILD_COVERAGE_ANALYSIS[=ON|OFF (default)]: build code coverage using Gcov and LCOV (both must be installed; requires GCC compiler; execute coverage analysis from build-directory using make coverage)

Pass these options either directly to the cmake .. command, e.g., to build the tests:

cmake -DBUILD_TESTS=on ..

N.B.: Toggling options to build tests using ccmake does not work correctly, as the necessarily libraries are not download automagically!

This project has been set up with a specific file/folder structure in mind. The following describes some important features of this setup:

• cmake/Modules : Contains CMake modules, including Findcontrol.cmake module
• docs: Contains project-specific docs in Markdown that are also parsed by Doxygen. This sub-directory includes global_todo.md, which contains a global list of TODO items for project that appear on TODO list generated in Doxygen documentation
• doxydocs: HTML output generated by building Doxygen documentation
• include/control: Project header files (*.hpp)
• scripts: Shell scripts used in Travis CI build
• test: Project test source files (*.cpp), including testCppProject.cpp, which contains include for Catch
• .travis.yml: Configuration file for Travis CI build, including static analysis using Coverity Scan and code coverage using Coveralls
• CMakeLists.txt: main CMakelists.txt file for project (should not need to be modified for basic build)
• Dependencies.cmake: list of dependencies and automated build, triggered if dependency cannot be found locally
• Doxyfile.in: Doxygen configuration file, adapted for generic use within project build (should not need to be modified)
• LICENSE.md: license file for project
• ProjectFiles.cmake: list of project source files to build
• README.md: project readme file, parsed as main page for Doxygen documentation

Once you've made your great commits:

1. Fork Control
2. Create a topic branch - git checkout -b my_branch
3. Push to your branch - git push origin my_branch
4. Create a Pull Request from your branch
5. That's it!

The copyright holders are not liable for any damage(s) incurred due to improper use of Control.