From 5bd002afdd01f0f43cbdc32fc91d819445b2de37 Mon Sep 17 00:00:00 2001 From: Dante Gama Dessavre Date: Wed, 22 Apr 2020 17:29:10 -0500 Subject: [PATCH] First commit --- .github/CODEOWNERS | 27 + .github/ISSUE_TEMPLATE/bug_report.md | 26 + .../ISSUE_TEMPLATE/documentation-request.md | 35 + .github/ISSUE_TEMPLATE/feature_request.md | 20 + .github/ISSUE_TEMPLATE/submit-question.md | 10 + .github/PULL_REQUEST_TEMPLATE.md | 44 + .gitignore | 46 + BUILD.md | 152 + CHANGELOG.md | 10 + CONTRIBUTING.md | 56 + LICENSE | 201 ++ README.md | 15 + build.sh | 169 ++ ci/checks/black_lists.sh | 62 + ci/checks/changelog.sh | 39 + ci/checks/copyright.py | 104 + ci/checks/style.sh | 85 + ci/gpu/build.sh | 206 ++ ci/local/README.md | 57 + ci/local/build.sh | 128 + ci/prtest.config | 6 + ci/release/update-version.sh | 62 + cpp/CMakeLists.txt | 180 ++ cpp/Doxyfile.in | 2436 +++++++++++++++++ cpp/cmake/EvalGpuArchs.cmake | 60 + cpp/cmake/FindNCCL.cmake | 116 + cpp/cmake/FindUCX.cmake | 114 + cpp/cmake/doxygen.cmake | 33 + cpp/include/raft.hpp | 31 + cpp/scripts/gitutils.py | 137 + cpp/scripts/include_checker.py | 90 + cpp/scripts/run-clang-format.py | 149 + cpp/test/test.cpp | 24 + img/rapids_arrow.png | Bin 0 -> 192477 bytes img/rapids_logo.png | Bin 0 -> 113880 bytes python/pytest.ini | 8 + python/raft/__init__.py | 1 + python/raft/dask/__init__.py | 0 python/raft/dask/common/__init__.py | 0 python/raft/include_test/__init__.py | 16 + .../raft/include_test/raft_include_test.pyx | 19 + python/raft/test/test_raft.py | 20 + python/setup.cfg | 15 + python/setup.py | 139 + python/setuputils.py | 254 ++ python/versioneer.py | 1822 ++++++++++++ 46 files changed, 7224 insertions(+) create mode 100755 .github/CODEOWNERS create mode 100755 .github/ISSUE_TEMPLATE/bug_report.md create mode 100755 .github/ISSUE_TEMPLATE/documentation-request.md create mode 100755 .github/ISSUE_TEMPLATE/feature_request.md create mode 100755 .github/ISSUE_TEMPLATE/submit-question.md create mode 100755 .github/PULL_REQUEST_TEMPLATE.md create mode 100644 .gitignore create mode 100644 BUILD.md create mode 100644 CHANGELOG.md create mode 100755 CONTRIBUTING.md create mode 100755 LICENSE create mode 100755 README.md create mode 100755 build.sh create mode 100755 ci/checks/black_lists.sh create mode 100755 ci/checks/changelog.sh create mode 100644 ci/checks/copyright.py create mode 100644 ci/checks/style.sh create mode 100644 ci/gpu/build.sh create mode 100644 ci/local/README.md create mode 100644 ci/local/build.sh create mode 100644 ci/prtest.config create mode 100755 ci/release/update-version.sh create mode 100644 cpp/CMakeLists.txt create mode 100644 cpp/Doxyfile.in create mode 100755 cpp/cmake/EvalGpuArchs.cmake create mode 100755 cpp/cmake/FindNCCL.cmake create mode 100644 cpp/cmake/FindUCX.cmake create mode 100644 cpp/cmake/doxygen.cmake create mode 100755 cpp/include/raft.hpp create mode 100644 cpp/scripts/gitutils.py create mode 100644 cpp/scripts/include_checker.py create mode 100755 cpp/scripts/run-clang-format.py create mode 100644 cpp/test/test.cpp create mode 100644 img/rapids_arrow.png create mode 100644 img/rapids_logo.png create mode 100644 python/pytest.ini create mode 100644 python/raft/__init__.py create mode 100644 python/raft/dask/__init__.py create mode 100644 python/raft/dask/common/__init__.py create mode 100644 python/raft/include_test/__init__.py create mode 100644 python/raft/include_test/raft_include_test.pyx create mode 100644 python/raft/test/test_raft.py create mode 100644 python/setup.cfg create mode 100644 python/setup.py create mode 100755 python/setuputils.py create mode 100644 python/versioneer.py diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS new file mode 100755 index 0000000000..907808c0bb --- /dev/null +++ b/.github/CODEOWNERS @@ -0,0 +1,27 @@ +#cpp code owners +cpp/ @rapidsai/cuml-cpp-codeowners +cpp/ @rapidsai/cugraph-cpp-codeowners + +#python code owners +python/ @rapidsai/cuml-python-codeowners +python/ @rapidsai/cugraph-python-codeowners + +#cmake code owners +**/CMakeLists.txt @rapidsai/cuml-cmake-codeowners +**/CMakeLists.txt @rapidsai/cugraph-cmake-codeowners +**/cmake/ @rapidsai/cuml-cmake-codeowners +**/cmake/ @rapidsai/cugraph-cmake-codeowners +python/setup.py @rapidsai/cuml-cmake-codeowners +python/setup.py @rapidsai/cugraph-cmake-codeowners +build.sh @rapidsai/cuml-cmake-codeowners +build.sh @rapidsai/cugraph-cmake-codeowners +**/build.sh @rapidsai/cuml-cmake-codeowners +**/build.sh @rapidsai/cugraph-cmake-codeowners + +#build/ops code owners +.github/ @rapidsai/ops-codeowners +ci/ @rapidsai/ops-codeowners +conda/ @rapidsai/ops-codeowners +**/Dockerfile @rapidsai/ops-codeowners +**/.dockerignore @rapidsai/ops-codeowners +docker/ @rapidsai/ops-codeowners diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100755 index 0000000000..bb9f1a2804 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,26 @@ +--- +name: Bug report +about: Create a bug report to help us improve RAFT +title: "[BUG]" +labels: "? - Needs Triage, bug" +assignees: '' + +--- + +**Describe the bug** +A clear and concise description of what the bug is. + +**Steps/Code to reproduce bug** +Follow this guide http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports to craft a minimal bug report. This helps us reproduce the issue you're having and resolve the issue more quickly. + +**Expected behavior** +A clear and concise description of what you expected to happen. + +**Environment details (please complete the following information):** + - Environment location: [Bare-metal, Docker, Cloud(specify cloud provider)] + - Method of RAFT install: [conda, Docker, or from source] + - If method of install is [Docker], provide `docker pull` & `docker run` commands used + + +**Additional context** +Add any other context about the problem here. diff --git a/.github/ISSUE_TEMPLATE/documentation-request.md b/.github/ISSUE_TEMPLATE/documentation-request.md new file mode 100755 index 0000000000..89a026f343 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/documentation-request.md @@ -0,0 +1,35 @@ +--- +name: Documentation request +about: Report incorrect or needed documentation +title: "[DOC]" +labels: "? - Needs Triage, doc" +assignees: '' + +--- + +## Report incorrect documentation + +**Location of incorrect documentation** +Provide links and line numbers if applicable. + +**Describe the problems or issues found in the documentation** +A clear and concise description of what you found to be incorrect. + +**Steps taken to verify documentation is incorrect** +List any steps you have taken: + +**Suggested fix for documentation** +Detail proposed changes to fix the documentation if you have any. + +--- + +## Report needed documentation + +**Report needed documentation** +A clear and concise description of what documentation you believe it is needed and why. + +**Describe the documentation you'd like** +A clear and concise description of what you want to happen. + +**Steps taken to search for needed documentation** +List any steps you have taken: diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100755 index 0000000000..9988a2a05d --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,20 @@ +--- +name: Feature request +about: Suggest an idea for RAFT +title: "[FEA]" +labels: "? - Needs Triage, feature request" +assignees: '' + +--- + +**Is your feature request related to a problem? Please describe.** +A clear and concise description of what the problem is. Ex. I wish I could use RAFT to do [...] + +**Describe the solution you'd like** +A clear and concise description of what you want to happen. + +**Describe alternatives you've considered** +A clear and concise description of any alternative solutions or features you've considered. + +**Additional context** +Add any other context, code examples, or references to existing implementations about the feature request here. diff --git a/.github/ISSUE_TEMPLATE/submit-question.md b/.github/ISSUE_TEMPLATE/submit-question.md new file mode 100755 index 0000000000..11a7f8ee20 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/submit-question.md @@ -0,0 +1,10 @@ +--- +name: Submit question +about: Ask a general question about RAFT +title: "[QST]" +labels: "? - Needs Triage, question" +assignees: '' + +--- + +**What is your question?** diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md new file mode 100755 index 0000000000..9c42cda720 --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,44 @@ + diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000000..ecc92d8dce --- /dev/null +++ b/.gitignore @@ -0,0 +1,46 @@ +## common +__pycache__ +*.pyc +*~ +\#* +.#* +*.o +*.so +*.dylib +.cache +.coverage +.vscode +*.swp +*.pytest_cache +htmlcov +build/ +build_prims/ +dist/ +python/**/**/*.cpp +python/external_repositories +python/record.txt +log +.ipynb_checkpoints +.DS_Store +dask-worker-space/ +## eclipse +.project +.cproject +.settings +.ptp-sync-folder + +## Pycharm +.idea + +## ccls +.ccls-cache +.ccls + +## profiling +*.qdrep +*.qdrep.cache +*.qdstrm +*.nvprof + +## doxygen build check inside ci/checks/style.sh +doxygen_check/ diff --git a/BUILD.md b/BUILD.md new file mode 100644 index 0000000000..99adf0f617 --- /dev/null +++ b/BUILD.md @@ -0,0 +1,152 @@ +# RAFT Build and Development Guide + +- [Usage of RAFT by downstream projects](usage-of-raft-by-downstream-projects) + - [C++ Integration](c-integration) + - [Python/Cython Integration](pythoncython-integration) +- [Building and running tests](building-and-running-tests) +- [CI Process](ci-process) +- [Development Guide](developer-guide) + - [Local Development](local-development) + - [Submitting PRs](submitting-prs) + + + +## Usage of RAFT by downstream projects + +### C++ Integration + +The C++ component of RAFT is header only, so it can be easily configured using CMake by consuming libraries. Since this repo is intended to be included by downstream repos, the recommended way of accomplishing that is using CMake's git cloning functionality: + + +```cmake +if(DEFINED ENV{RAFT_PATH}) + message(STATUS "RAFT_PATH environment variable detected.") + message(STATUS "RAFT_DIR set to $ENV{RAFT_PATH}") + set(RAFT_DIR ENV{RAFT_PATH}) + +else(DEFINED ENV{RAFT_PATH}) + message(STATUS "RAFT_PATH environment variable NOT detected, cloning RAFT") + set(RAFT_GIT_DIR ${CMAKE_CURRENT_BINARY_DIR}/raft CACHE STRING "Path to RAFT repo") + + ExternalProject_Add(raft + GIT_REPOSITORY git@github.com:dantegd/barge.git + GIT_TAG pinned_commit/git_tag/branch + PREFIX ${RAFT_GIT_DIR} + CONFIGURE_COMMAND "" + BUILD_COMMAND "" + INSTALL_COMMAND "") + + set(RAFT_INCLUDE_DIR ${RAFT_DIR}/src/raft/cpp/include CACHE STRING "RAFT include variable") +endif(DEFINED ENV{RAFT_PATH}) + +``` + +This create the variable `$RAFT_INCLUDE_DIR` variable that can be used in `include_directories`, and then the related header files can be included when needed. + +### Python/Cython Integration + +The Python and Cython code have been designed to be included in projects that use RAFT, as opposed to a distributable by itself. To use: + +- The file `setuputils.py` is included in RAFT's `python` folder. Copy the file to your repo, in a location where it can be imported by `setup.py` +- In your setup.py, use the function `use_raft_package`, for example for cuML: + + +```python +# Optional location of C++ build folder that can be configured by the user +libcuml_path = get_environment_option('CUML_BUILD_PATH') +# Optional location of RAFT that can be confugred by the user +raft_path = get_environment_option('RAFT_PATH') + +use_raft_package(raft_path, libcuml_path) +``` + +The usage of RAFT by the consuming repo's python code follows the rules: +1. If the environment variable `RAFT_PATH` points to the RAFT repo, then that will be used. +2. If there is a C++ build folder that has cloned RAFT already, setup.py will use that RAFT. +3. If none of the above happened, then setup.py will clone RAFT and use it directly. + +- After `setup.py` calls the `use_raft_package` function, the RAFT python code will be included (via a symlink) in the consuming repo package, under a raft subfolder. So for example, `cuml` python package includes RAFT in `cuml.raft`. + + +## Building and running tests + +Since RAFT is not meant to create any artifact on itself, but be included in other projects, the build infrastructure is focused only on testing. + +The base folder in the repository contains a `build.sh` script that builds both the C++ and Python code, which is the recommended way of building the tests. + +To run C++ tests: + +```bash +./test_raft +``` + +To run Python tests: + +```bash +cd python +python -m pytest +``` + +To build manually, you can also use `CMake` and setup.py directly. For C++: + +```bash +cd cpp +mkdir build +cd build +cmake .. +``` + +There is no `install` target currently. + +For python: + +```bash +cd python +python setup.py build_ext --inplace +``` + + +## CI Process + +PRs submitted to RAFT will always run the RAFT tests (once GPUCI is enabled). Additionally, RAFT has convenience functionality to run tests of the following projects that use RAFT: cuML and cuGraph. + +To run these other tests, turn `ON` the variables in `ci/prtest.config` in your PR: + +```bash +RUN_CUGRAPH_LIBCUGRAPH_TESTS=OFF +RUN_CUGRAPH_PYTHON_TESTS=OFF + +RUN_CUML_LIBCUML_TESTS=OFF +RUN_CUML_PRIMS_TESTS=OFF +RUN_CUML_PYTHON_TESTS=OFF +``` + +This will make it so that CI in the PR will clone and build the respective repository, but the repository **will be built using the fork/branch of RAFT in the PR**. This allows to test changes in RAFT without the need of opening PRs in the other repositories. + +Before merging the PR, those variables need to be returned to `OFF`. + + +## Developer Guide + +### Local Development + +To help working with RAFT and consuming projects as seamless as possible, this section describes how a typical workflow looks like and gives some guidelines for developers working in projects that affect code in both RAFT and at least one downstream repository. + +Using as an example developer working on cuML and RAFT, we recommend the following: + +- Create two working folders: one containing the cloned cuML repository and the other the cloned RAFT one. +- Create environment variable `RAFT_PATH` pointing to the location of the RAFT path. +- Work on same named branches in both repos/folders. + +This will facilitate development, and the `RAFT_PATH` variable will make it so that the downstream repository, in this case cuML, builds using the locally cloned RAFT (as descrbed in the first step). + +### Submitting PRs + +If you are submitting changes to RAFT itself, without changing downstream repos, you can use the config file located in `ci/prtest.config` to trigger RAFT's CI to run tests of downstream repositories. + +If you have changes to both RAFT and at least one downstream repo, then: + +- It is recommended to open a PR to both repositories (for visibility and CI tests). +- Change the pinned branch/commit in the downstream repo PR to point to the fork and branch used for the RAFT PR to make CI run tests +- If your changes might affect usage of RAFT by other downnstream repos, alert reviewers and open a github issue or PR in that downstream repo as approproate. +- The PR to RAFT will be merged first, so that the downstream repo PR pinned branch/commit can be returned to the main RAFT branch and run CI with it. diff --git a/CHANGELOG.md b/CHANGELOG.md new file mode 100644 index 0000000000..640b4c90bb --- /dev/null +++ b/CHANGELOG.md @@ -0,0 +1,10 @@ +# RAFT 0.14.0 (Date TBD) + + +## New Features +- Initial RAFT version + +## Improvements + + +## Bug Fixes diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100755 index 0000000000..41624274fb --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,56 @@ +# Contributing to RAFT + +If you are interested in contributing to RAFT, your contributions will fall +into three categories: +1. You want to report a bug, feature request, or documentation issue + - File an [issue](https://github.com/rapidsai/RAFT/issues/new/choose) + describing what you encountered or what you want to see changed. + - The RAPIDS team will evaluate the issues and triage them, scheduling + them for a release. If you believe the issue needs priority attention + comment on the issue to notify the team. +2. You want to propose a new Feature and implement it + - Post about your intended feature, and we shall discuss the design and + implementation. + - Once we agree that the plan looks good, go ahead and implement it, using + the [code contributions](#code-contributions) guide below. +3. You want to implement a feature or bug-fix for an outstanding issue + - Follow the [code contributions](#code-contributions) guide below. + - If you need more context on a particular issue, please ask and we shall + provide. + + +## Code contributions + +### Your first issue + +1. Read the project's [README.md](https://github.com/rapidsai/RAFT/blob/master/README.md) + to learn how to setup the development environment +2. Find an issue to work on. The best way is to look for the [good first issue](https://github.com/rapidsai/RAFT/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) + or [help wanted](https://github.com/rapidsai/RAFT/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) labels +3. Comment on the issue saying you are going to work on it +4. Code! Make sure to update unit tests! +5. When done, [create your pull request](https://github.com/rapidsai/RAFT/compare) +6. Verify that CI passes all [status checks](https://help.github.com/articles/about-status-checks/). Fix if needed +7. Wait for other developers to review your code and update code as needed +8. Once reviewed and approved, a RAPIDS developer will merge your pull request + +Remember, if you are unsure about anything, don't hesitate to comment on issues +and ask for clarifications! + +### Seasoned developers + +Once you have gotten your feet wet and are more comfortable with the code, you +can look at the prioritized issues of our next release in our [project boards](https://github.com/rapidsai/RAFT/projects). + +> **Pro Tip:** Always look at the release board with the highest number for +issues to work on. This is where RAPIDS developers also focus their efforts. + +Look at the unassigned issues, and find an issue you are comfortable with +contributing to. Start with _Step 3_ from above, commenting on the issue to let +others know you are working on it. If you have any questions related to the +implementation of the issue, ask them in the issue instead of the PR. + +## Attribution +Portions adopted from https://github.com/pytorch/pytorch/blob/master/CONTRIBUTING.md + + diff --git a/LICENSE b/LICENSE new file mode 100755 index 0000000000..1a89b9054d --- /dev/null +++ b/LICENSE @@ -0,0 +1,201 @@ + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "{}" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright 2020 NVIDIA Corporation + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. diff --git a/README.md b/README.md new file mode 100755 index 0000000000..9b13f5fef4 --- /dev/null +++ b/README.md @@ -0,0 +1,15 @@ +#
 RAFT: RAPIDS Analytics Frameworks Toolset
+ +RAFT is a repository containining shared utilities, mathematical operations and common functions for the analytics components of RAPIDS. Both the C++ and Python components can be included in consuming libraries. + +Refer to the [Build and Development Guide](Build.md) for details on RAFT's design, building, testing and development guidelines. + +## Folder Structure and Contents + +The folder structure mirrors the main RAPIDS repos (cuDF, cuML, cuGraph...), with the following folders: + +- `cpp`: Source code for all C++ code. The code is header only, therefore it is in the `include` folder (with no `src`). +- `python`: Source code for all Python source code. +- `ci`: Scripts for running CI in PRs + + diff --git a/build.sh b/build.sh new file mode 100755 index 0000000000..8f4b0afbc6 --- /dev/null +++ b/build.sh @@ -0,0 +1,169 @@ +#!/bin/bash + +# Copyright (c) 2020, NVIDIA CORPORATION. + +# cuml build script + +# This script is used to build the component(s) in this repo from +# source, and can be called with various options to customize the +# build as needed (see the help output for details) + +# Abort script on first error +set -e + +NUMARGS=$# +ARGS=$* + +# NOTE: ensure all dir changes are relative to the location of this +# script, and that this script resides in the repo dir! +REPODIR=$(cd $(dirname $0); pwd) + +VALIDARGS="clean cppraft pyraft -v -g --allgpuarch --nvtx --show_depr_warn -h" +HELP="$0 [ ...] [ ...] + where is: + clean - remove all existing build artifacts and configuration (start over) + cppraft - build the cuml C++ code only. Also builds the C-wrapper library + around the C++ code. + pyraft - build the cuml Python package + and is: + -v - verbose build mode + -g - build for debug + --allgpuarch - build for all supported GPU architectures + --nvtx - Enable nvtx for profiling support + --show_depr_warn - show cmake deprecation warnings + -h - print this text + + default action (no args) is to build both cppraft and pyraft targets +" +CPP_RAFT_BUILD_DIR=${REPODIR}/cpp/build +PY_RAFT_BUILD_DIR=${REPODIR}/python/build +PYTHON_DEPS_CLONE=${REPODIR}/python/external_repositories +BUILD_DIRS="${CPP_RAFT_BUILD_DIR} ${PY_RAFT_BUILD_DIR} ${PYTHON_DEPS_CLONE}" + +# Set defaults for vars modified by flags to this script +VERBOSE="" +BUILD_ALL_GPU_ARCH=0 +SINGLEGPU="" +NVTX=OFF +CLEAN=0 +BUILD_DISABLE_DEPRECATION_WARNING=ON + +# Set defaults for vars that may not have been defined externally +# FIXME: if INSTALL_PREFIX is not set, check PREFIX, then check +# CONDA_PREFIX, but there is no fallback from there! +INSTALL_PREFIX=${INSTALL_PREFIX:=${PREFIX:=${CONDA_PREFIX}}} +PARALLEL_LEVEL=${PARALLEL_LEVEL:=""} +BUILD_ABI=${BUILD_ABI:=ON} + +function hasArg { + (( ${NUMARGS} != 0 )) && (echo " ${ARGS} " | grep -q " $1 ") +} + +if hasArg -h || hasArg --help; then + echo "${HELP}" + exit 0 +fi + +# Check for valid usage +if (( ${NUMARGS} != 0 )); then + for a in ${ARGS}; do + if ! (echo " ${VALIDARGS} " | grep -q " ${a} "); then + echo "Invalid option: ${a}" + exit 1 + fi + done +fi + +# Process flags +if hasArg -v; then + VERBOSE=1 +fi +if hasArg -g; then + BUILD_TYPE=Debug +fi + +if hasArg --allgpuarch; then + BUILD_ALL_GPU_ARCH=1 +fi +if hasArg --singlegpu; then + SINGLEGPU="--singlegpu" +fi +if hasArg --nvtx; then + NVTX=ON +fi +if hasArg --show_depr_warn; then + BUILD_DISABLE_DEPRECATION_WARNING=OFF +fi +if hasArg clean; then + CLEAN=1 +fi + +# If clean given, run it prior to any other steps +if (( ${CLEAN} == 1 )); then + # If the dirs to clean are mounted dirs in a container, the + # contents should be removed but the mounted dirs will remain. + # The find removes all contents but leaves the dirs, the rmdir + # attempts to remove the dirs but can fail safely. + for bd in ${BUILD_DIRS}; do + if [ -d ${bd} ]; then + find ${bd} -mindepth 1 -delete + rmdir ${bd} || true + fi + + done + + cd ${REPODIR}/python + python setup.py clean --all + cd ${REPODIR} +fi + +################################################################################ +# Configure for building all C++ targets +if (( ${NUMARGS} == 0 )) || hasArg cppraft; then + if (( ${BUILD_ALL_GPU_ARCH} == 0 )); then + GPU_ARCH="" + echo "Building for the architecture of the GPU in the system..." + else + GPU_ARCH="-DGPU_ARCHS=ALL" + echo "Building for *ALL* supported GPU architectures..." + fi + + mkdir -p ${CPP_RAFT_BUILD_DIR} + cd ${CPP_RAFT_BUILD_DIR} + + cmake -DNVTX=${NVTX} \ + -DPARALLEL_LEVEL=${PARALLEL_LEVEL} \ + -DNCCL_PATH=${INSTALL_PREFIX} \ + -DDISABLE_DEPRECATION_WARNING=${BUILD_DISABLE_DEPRECATION_WARNING} \ + .. + +fi + +# Run all make targets at once + +MAKE_TARGETS= +if hasArg cppraft; then + MAKE_TARGETS="${MAKE_TARGETS} test_raft" +fi + + +# If `./build.sh pyraft` is called, don't build C/C++ components +if (( ${NUMARGS} == 0 )) || hasArg cppraft; then +# If there are no targets specified when calling build.sh, it will +# just call `make -j`. This avoids a lot of extra printing + cd ${CPP_RAFT_BUILD_DIR} + make -j${PARALLEL_LEVEL} ${MAKE_TARGETS} VERBOSE=${VERBOSE} + +fi + + +# Build and (optionally) install the cuml Python package +if (( ${NUMARGS} == 0 )) || hasArg cuml; then + + cd ${REPODIR}/python + if [[ ${INSTALL_TARGET} != "" ]]; then + python setup.py build_ext -j${PARALLEL_LEVEL:-1} --inplace ${SINGLEGPU} + else + python setup.py build_ext -j${PARALLEL_LEVEL:-1} --inplace --library-dir=${LIBCUML_BUILD_DIR} ${SINGLEGPU} + fi +fi diff --git a/ci/checks/black_lists.sh b/ci/checks/black_lists.sh new file mode 100755 index 0000000000..5ac645cf17 --- /dev/null +++ b/ci/checks/black_lists.sh @@ -0,0 +1,62 @@ +#!/bin/bash +# Copyright (c) 2020, NVIDIA CORPORATION. +########################################## +# cuML black listed function call Tester # +########################################## + +# PR_TARGET_BRANCH is set by the CI enviroment + +# Checkout master for comparison +git checkout --quiet $PR_TARGET_BRANCH + +# Switch back to tip of PR branch +git checkout --quiet current-pr-branch + +# Ignore errors during searching +set +e + +# Disable history expansion to enable use of ! in perl regex +set +H + +RETVAL=0 + +for black_listed in cudaDeviceSynchronize cudaMalloc cudaMallocManaged cudaFree cudaMallocHost cudaHostAlloc cudaFreeHost; do + TMP=`git --no-pager diff --ignore-submodules -w --minimal -U0 -S"$black_listed" $PR_TARGET_BRANCH | grep '^+' | grep -v '^+++' | grep "$black_listed"` + if [ "$TMP" != "" ]; then + for filename in `git --no-pager diff --ignore-submodules -w --minimal --name-only -S"$black_listed" $PR_TARGET_BRANCH`; do + basefilename=$(basename -- "$filename") + filext="${basefilename##*.}" + if [ "$filext" != "md" ] && [ "$filext" != "sh" ]; then + TMP2=`git --no-pager diff --ignore-submodules -w --minimal -U0 -S"$black_listed" $PR_TARGET_BRANCH -- $filename | grep '^+' | grep -v '^+++' | grep "$black_listed" | grep -vE "^\+[[:space:]]*/{2,}.*$black_listed"` + if [ "$TMP2" != "" ]; then + echo "=== ERROR: black listed function call $black_listed added to $filename ===" + git --no-pager diff --ignore-submodules -w --minimal -S"$black_listed" $PR_TARGET_BRANCH -- $filename + echo "=== END ERROR ===" + RETVAL=1 + fi + fi + done + fi +done + +for cond_black_listed in cudaMemcpy cudaMemset; do + TMP=`git --no-pager diff --ignore-submodules -w --minimal -U0 -S"$cond_black_listed" $PR_TARGET_BRANCH | grep '^+' | grep -v '^+++' | grep -P "$cond_black_listed(?!Async)"` + + if [ "$TMP" != "" ]; then + for filename in `git --no-pager diff --ignore-submodules -w --minimal --name-only -S"$cond_black_listed" $PR_TARGET_BRANCH`; do + basefilename=$(basename -- "$filename") + filext="${basefilename##*.}" + if [ "$filext" != "md" ] && [ "$filext" != "sh" ]; then + TMP2=`git --no-pager diff --ignore-submodules -w --minimal -U0 -S"$cond_black_listed" $PR_TARGET_BRANCH -- $filename | grep '^+' | grep -v '^+++' | grep -P "$cond_black_listed(?!Async)" | grep -vE "^\+[[:space:]]*/{2,}.*$cond_black_listed"` + if [ "$TMP2" != "" ]; then + echo "=== ERROR: black listed function call $cond_black_listed added to $filename ===" + git --no-pager diff --ignore-submodules -w --minimal -S"$cond_black_listed" $PR_TARGET_BRANCH -- $filename + echo "=== END ERROR ===" + RETVAL=1 + fi + fi + done + fi +done + +exit $RETVAL diff --git a/ci/checks/changelog.sh b/ci/checks/changelog.sh new file mode 100755 index 0000000000..165c3c16ed --- /dev/null +++ b/ci/checks/changelog.sh @@ -0,0 +1,39 @@ +#!/bin/bash +# Copyright (c) 2020, NVIDIA CORPORATION. +######################### +# cuML CHANGELOG Tester # +######################### + +# Checkout master for comparison +git checkout --quiet master + +# Switch back to tip of PR branch +git checkout --quiet current-pr-branch + +# Ignore errors during searching +set +e + +# Get list of modified files between matster and PR branch +CHANGELOG=`git diff --name-only master...current-pr-branch | grep CHANGELOG.md` +# Check if CHANGELOG has PR ID +PRNUM=`cat CHANGELOG.md | grep "$PR_ID"` +RETVAL=0 + +# Return status of check result +if [ "$CHANGELOG" != "" -a "$PRNUM" != "" ] ; then + echo -e "\n\n>>>> PASSED: CHANGELOG.md has been updated with current PR information.\n\nPlease ensure the update meets the following criteria.\n" +else + echo -e "\n\n>>>> FAILED: CHANGELOG.md has not been updated!\n\nPlease add a line describing this PR to CHANGELOG.md in the repository root directory. The line should meet the following criteria.\n" + RETVAL=1 +fi + +cat << EOF + It should be placed under the section for the appropriate release. + It should be placed under "New Features", "Improvements", or "Bug Fixes" as appropriate. + It should be formatted as '- PR # ' + Example format for #491 '- PR #491 Add CI test script to check for updates to CHANGELOG.md in PRs' + + +EOF + +exit $RETVAL diff --git a/ci/checks/copyright.py b/ci/checks/copyright.py new file mode 100644 index 0000000000..738eeb32dd --- /dev/null +++ b/ci/checks/copyright.py @@ -0,0 +1,104 @@ +# Copyright (c) 2020, NVIDIA CORPORATION. +# +# Licensed under the Apache License, Version 2.0 (the "License"); +# you may not use this file except in compliance with the License. +# You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +# + +import datetime +import re +import gitutils + + +FilesToCheck = [ + re.compile(r"[.](cmake|cpp|cu|cuh|h|hpp|sh|pxd|py|pyx)$"), + re.compile(r"CMakeLists[.]txt$"), + re.compile(r"CMakeLists_standalone[.]txt$"), + re.compile(r"setup[.]cfg$"), + re.compile(r"[.]flake8[.]cython$"), + re.compile(r"meta[.]yaml$") +] + + +def checkThisFile(f): + if gitutils.isFileEmpty(f): + return False + for checker in FilesToCheck: + if checker.search(f): + return True + return False + + +def getCopyrightYears(line): + res = re.search(r"Copyright \(c\) (\d{4}), NVIDIA CORPORATION", line) + if res: + return (int(res.group(1)), int(res.group(1))) + res = re.search(r"Copyright \(c\) (\d{4})-(\d{4}), NVIDIA CORPORATION", + line) + if res: + return (int(res.group(1)), int(res.group(2))) + return (None, None) + + +def checkCopyright(f): + """ + Checks for copyright headers and their years + """ + errs = [] + thisYear = datetime.datetime.now().year + lineNum = 0 + crFound = False + yearMatched = False + fp = open(f, "r") + for line in fp.readlines(): + lineNum += 1 + start, end = getCopyrightYears(line) + if start is None: + continue + crFound = True + if thisYear < start or thisYear > end: + errs.append((f, lineNum, + "Current year not included in the copyright header")) + else: + yearMatched = True + fp.close() + # copyright header itself not found + if not crFound: + errs.append((f, 0, + "Copyright header missing or formatted incorrectly")) + # even if the year matches a copyright header, make the check pass + if yearMatched: + errs = [] + return errs + + +def checkCopyrightForAll(): + """ + Checks for copyright headers in all the modified files. In case of local + repo, this script will just look for uncommitted files and in case of CI + it compares between branches "$PR_TARGET_BRANCH" and "current-pr-branch" + """ + files = gitutils.modifiedFiles(filter=checkThisFile) + errors = [] + for f in files: + errors += checkCopyright(f) + if len(errors) > 0: + print("Copyright headers incomplete in some of the files!") + for e in errors: + print(" %s:%d Issue: %s" % (e[0], e[1], e[2])) + print("") + raise Exception("Copyright check failed! Check above to know more") + else: + print("Copyright check passed") + + +if __name__ == "__main__": + checkCopyrightForAll() diff --git a/ci/checks/style.sh b/ci/checks/style.sh new file mode 100644 index 0000000000..160c3a2c69 --- /dev/null +++ b/ci/checks/style.sh @@ -0,0 +1,85 @@ +#!/bin/bash +# Copyright (c) 2020, NVIDIA CORPORATION. +##################### +# cuML Style Tester # +##################### + +# Ignore errors and set path +set +e +PATH=/conda/bin:$PATH + +# Activate common conda env +source activate gdf + +# Run flake8 and get results/return code +FLAKE=`flake8 --exclude=cpp,thirdparty,__init__.py,versioneer.py && flake8 --config=python/.flake8.cython` +RETVAL=$? + +# Output results if failure otherwise show pass +if [ "$FLAKE" != "" ]; then + echo -e "\n\n>>>> FAILED: flake8 style check; begin output\n\n" + echo -e "$FLAKE" + echo -e "\n\n>>>> FAILED: flake8 style check; end output\n\n" +else + echo -e "\n\n>>>> PASSED: flake8 style check\n\n" +fi + +# Check for copyright headers in the files modified currently +COPYRIGHT=`env PYTHONPATH=cpp/scripts python ci/checks/copyright.py 2>&1` +CR_RETVAL=$? +if [ "$RETVAL" = "0" ]; then + RETVAL=$CR_RETVAL +fi + +# Output results if failure otherwise show pass +if [ "$CR_RETVAL" != "0" ]; then + echo -e "\n\n>>>> FAILED: copyright check; begin output\n\n" + echo -e "$COPYRIGHT" + echo -e "\n\n>>>> FAILED: copyright check; end output\n\n" +else + echo -e "\n\n>>>> PASSED: copyright check\n\n" +fi + +# Check for a consistent #include syntax +# TODO: keep adding more dirs as and when we update the syntax +HASH_INCLUDE=`python cpp/scripts/include_checker.py \ + cpp/bench \ + cpp/comms/mpi/include \ + cpp/comms/mpi/src \ + cpp/comms/std/include \ + cpp/comms/std/src \ + cpp/include \ + cpp/examples \ + 2>&1` +HASH_RETVAL=$? +if [ "$RETVAL" = "0" ]; then + RETVAL=$HASH_RETVAL +fi + +# Output results if failure otherwise show pass +if [ "$HASH_RETVAL" != "0" ]; then + echo -e "\n\n>>>> FAILED: #include check; begin output\n\n" + echo -e "$HASH_INCLUDE" + echo -e "\n\n>>>> FAILED: #include check; end output\n\n" +else + echo -e "\n\n>>>> PASSED: #include check\n\n" +fi + +# Check for a consistent code format +# TODO: keep adding more dirs when we add more source folders in cuml +FORMAT=`python cpp/scripts/run-clang-format.py 2>&1` +FORMAT_RETVAL=$? +if [ "$RETVAL" = "0" ]; then + RETVAL=$FORMAT_RETVAL +fi + +# Output results if failure otherwise show pass +if [ "$FORMAT_RETVAL" != "0" ]; then + echo -e "\n\n>>>> FAILED: clang format check; begin output\n\n" + echo -e "$FORMAT" + echo -e "\n\n>>>> FAILED: clang format check; end output\n\n" +else + echo -e "\n\n>>>> PASSED: clang format check\n\n" +fi + +exit $RETVAL diff --git a/ci/gpu/build.sh b/ci/gpu/build.sh new file mode 100644 index 0000000000..6d50ad0159 --- /dev/null +++ b/ci/gpu/build.sh @@ -0,0 +1,206 @@ +#!/bin/bash +# Copyright (c) 2020, NVIDIA CORPORATION. +######################################### +# cuML GPU build and test script for CI # +######################################### + +set -e +NUMARGS=$# +ARGS=$* + +# Logger function for build status output +function logger() { + echo -e "\n>>>> $@\n" +} + +# Arg parsing function +function hasArg { + (( ${NUMARGS} != 0 )) && (echo " ${ARGS} " | grep -q " $1 ") +} + +# Set path and build parallel level +export PATH=/conda/bin:/usr/local/cuda/bin:$PATH +export PARALLEL_LEVEL=4 +export CUDA_REL=${CUDA_VERSION%.*} + +# Set home to the job's workspace +export HOME=$WORKSPACE + +# Parse git describei +cd $WORKSPACE +export GIT_DESCRIBE_TAG=`git describe --tags` +export MINOR_VERSION=`echo $GIT_DESCRIBE_TAG | grep -o -E '([0-9]+\.[0-9]+)'` + +# Read options for cloning/running downstream repo tests +source $WORKSPACE/ci/prtest.config + +################################################################################ +# SETUP - Check environment +################################################################################ + +logger "Check environment..." +env + +logger "Check GPU usage..." +nvidia-smi + +# temporary usage of conda install with packages listed here, looking into +# using the repos yaml files for this +logger "Activate conda env..." +source activate gdf +logger "Installing packages needed for RAFT..." +conda install -c conda-forge -c rapidsai -c rapidsai-nightly -c nvidia \ + "cupy>=7,<8.0.0a0" \ + "cudatoolkit=${CUDA_REL}" \ + "cudf=${MINOR_VERSION}" \ + "rmm=${MINOR_VERSION}" \ + "cmake==3.14.3" \ + "nccl>=2.5" \ + "dask>=2.12.0" \ + "distributed>=2.12.0" \ + "dask-cudf=${MINOR_VERSION}" \ + "dask-cuda=${MINOR_VERSION}" \ + "ucx-py=${MINOR_VERSION}" + +if [ "$RUN_CUML_LIBCUML_TESTS" = "ON" ] || [ "$RUN_CUML_PRIMS_TESTS" = "ON" ] || [ "$RUN_CUML_PYTHON_TESTS" = "ON" ]; then + conda install -c conda-forge -c rapidsai -c rapidsai-nightly -c nvidia \ + "nvstrings=${MINOR_VERSION}" \ + "libcumlprims=${MINOR_VERSION}" \ + "lapack" \ + "umap-learn" \ + "nccl>=2.5" \ + "statsmodels" \ + "xgboost====1.0.2dev.rapidsai0.13" \ + "lightgbm" +fi + +if [ "$RUN_CUGRAPH_LIBCUGRAPH_TESTS" = "ON" ] || [ "$RUN_CUGRAPH_PYTHON_TESTS" = "ON" ]; then + conda install -c nvidia -c rapidsai -c rapidsai-nightly -c conda-forge -c defaults \ + "networkx>=2.3" \ + "python-louvain" \ + "libcypher-parser" \ + "ipython=7.3*" \ + "jupyterlab" +fi + +# Install the master version of dask, distributed, and dask-ml +logger "pip install git+https://github.com/dask/distributed.git --upgrade --no-deps" +pip install "git+https://github.com/dask/distributed.git" --upgrade --no-deps +logger "pip install git+https://github.com/dask/dask.git --upgrade --no-deps" +pip install "git+https://github.com/dask/dask.git" --upgrade --no-deps + + +logger "Check versions..." +python --version +$CC --version +$CXX --version +conda list + +################################################################################ +# BUILD - Build RAFT tests +################################################################################ + +logger "Adding ${CONDA_PREFIX}/lib to LD_LIBRARY_PATH" + +export LD_LIBRARY_PATH_CACHED=$LD_LIBRARY_PATH +export LD_LIBRARY_PATH=$CONDA_PREFIX/lib:$LD_LIBRARY_PATH + +logger "Build libcuml, cuml, prims and bench targets..." +$WORKSPACE/build.sh cppraft pyraft -v + +logger "Resetting LD_LIBRARY_PATH..." + +export LD_LIBRARY_PATH=$LD_LIBRARY_PATH_CACHED +export LD_LIBRARY_PATH_CACHED="" + +logger "Build treelite for GPU testing..." + +cd $WORKSPACE + + +################################################################################ +# TEST - Run GoogleTest and py.tests for RAFT +################################################################################ + +if hasArg --skip-tests; then + logger "Skipping Tests..." + exit 0 +fi + +logger "Check GPU usage..." +nvidia-smi + +logger "GoogleTest for raft..." +cd $WORKSPACE/cpp/build +GTEST_OUTPUT="xml:${WORKSPACE}/test-results/raft_cpp/" ./test/ml + +logger "Python pytest for cuml..." +cd $WORKSPACE/python + +pytest --cache-clear --junitxml=${WORKSPACE}/junit-cuml.xml -v -s + + +################################################################################ +# cuML CI +################################################################################ + +if [ "$RUN_CUML_LIBCUML_TESTS" = "ON" ] || [ "$RUN_CUML_PRIMS_TESTS" = "ON" ] || [ "$RUN_CUML_PYTHON_TESTS" = "ON" ] || [ "$RUN_CUGRAPH_LIBCUGRAPH_TESTS" = "ON" ] || [ "$RUN_CUGRAPH_PYTHON_TESTS" = "ON" ]; then + cd $WORKSPACE + mkdir $WORKSPACE/test_downstream_repos + cd $WORKSPACE/test_downstream_repos + export RAFT_PATH=$WORKSPACE +fi + +if [ "$RUN_CUML_LIBCUML_TESTS" = "ON" ] || [ "$RUN_CUML_PRIMS_TESTS" = "ON" ] || [ "$RUN_CUML_PYTHON_TESTS" = "ON" ]; then + cd $WORKSPACE/test_downstream_repos + + ## Change fork and branch to be tested here: + git clone https://github.com/rapidsai/cuml.git -b branch-0.14 + + + ## Build cuML and run tests, uncomment the tests you want to run + $WORKSPACE/test_downstream_repos/cuml/build.sh + + if [ "$RUN_CUML_LIBCUML_TESTS" = "ON" ]; then + logger "GoogleTest for libcuml..." + cd $WORKSPACE/cpp/build + GTEST_OUTPUT="xml:${WORKSPACE}/test-results/libcuml_cpp/" ./test/ml + fi + + if [ "$RUN_CUML_PYTHON_TESTS" = "ON" ]; then + logger "Python pytest for cuml..." + cd $WORKSPACE/python + pytest --cache-clear --junitxml=${WORKSPACE}/junit-cuml.xml -v -s -m "not memleak" + fi + + if [ "$RUN_CUML_PRIMS_TESTS" = "ON" ]; then + logger "Run ml-prims test..." + cd $WORKSPACE/cpp/build + GTEST_OUTPUT="xml:${WORKSPACE}/test-results/prims/" ./test/prims + fi +fi + + +################################################################################ +# cuGraph CI +################################################################################ + +if [ "$RUN_CUGRAPH_LIBCUGRAPH_TESTS" = "ON" ] || [ "$RUN_CUGRAPH_PYTHON_TESTS" = "ON" ]; then + cd $WORKSPACE/test_downstream_repos + + ## Change fork and branch to be tested here: + git clone https://github.com/rapidsai/cugraph.git -b branch-0.14 + + $WORKSPACE/test_downstream_repos/cugraph/build.sh clean libcugraph cugraph + + if [ "$RUN_CUGRAPH_LIBCUGRAPH_TESTS" = "ON" ]; then + logger "GoogleTest for libcugraph..." + cd $WORKSPACE/cpp/build + ${WORKSPACE}/ci/test.sh ${TEST_MODE_FLAG} | tee testoutput.txt + fi + + if [ "$RUN_CUGRAPH_PYTHON_TESTS" = "ON" ]; then + logger "Python pytest for cugraph..." + cd $WORKSPACE/python + fi +fi diff --git a/ci/local/README.md b/ci/local/README.md new file mode 100644 index 0000000000..87976b26c2 --- /dev/null +++ b/ci/local/README.md @@ -0,0 +1,57 @@ +## Purpose + +This script is designed for developer and contributor use. This tool mimics the actions of gpuCI on your local machine. This allows you to test and even debug your code inside a gpuCI base container before pushing your code as a GitHub commit. +The script can be helpful in locally triaging and debugging RAPIDS continuous integration failures. + +## Requirements + +``` +nvidia-docker +``` + +## Usage + +``` +bash build.sh [-h] [-H] [-s] [-r ] [-i ] +Build and test your local repository using a base gpuCI Docker image + +where: + -H Show this help text + -r Path to repository (defaults to working directory) + -i Use Docker image (default is gpuci/rapidsai-base:cuda10.0-ubuntu16.04-gcc5-py3.6) + -s Skip building and testing and start an interactive shell in a container of the Docker image +``` + +Example Usage: +`bash build.sh -r ~/rapids/cuml -i gpuci/rapidsai-base:cuda9.2-ubuntu16.04-gcc5-py3.6` + +For a full list of available gpuCI docker images, visit our [DockerHub](https://hub.docker.com/r/gpuci/rapidsai-base/tags) page. + +Style Check: +```bash +$ bash ci/local/build.sh -r ~/rapids/cuml -s +$ source activate gdf #Activate gpuCI conda environment +$ cd rapids +$ flake8 python +``` + +## Information + +There are some caveats to be aware of when using this script, especially if you plan on developing from within the container itself. + + +### Docker Image Build Repository + +The docker image will generate build artifacts in a folder on your machine located in the `root` directory of the repository you passed to the script. For the above example, the directory is named `~/rapids/cuml/build_rapidsai-base_cuda9.2-ubuntu16.04-gcc5-py3.6/`. Feel free to remove this directory after the script is finished. + +*Note*: The script *will not* override your local build repository. Your local environment stays in tact. + + +### Where The User is Dumped + +The script will build your repository and run all tests. If any tests fail, it dumps the user into the docker container itself to allow you to debug from within the container. If all the tests pass as expected the container exits and is automatically removed. Remember to exit the container if tests fail and you do not wish to debug within the container itself. + + +### Container File Structure + +Your repository will be located in the `/rapids/` folder of the container. This folder is volume mounted from the local machine. Any changes to the code in this repository are replicated onto the local machine. The `cpp/build` and `python/build` directories within your repository is on a separate mount to avoid conflicting with your local build artifacts. diff --git a/ci/local/build.sh b/ci/local/build.sh new file mode 100644 index 0000000000..5bd81fa042 --- /dev/null +++ b/ci/local/build.sh @@ -0,0 +1,128 @@ +#!/bin/bash + +DOCKER_IMAGE="gpuci/rapidsai-base:cuda10.0-ubuntu16.04-gcc5-py3.6" +REPO_PATH=${PWD} +RAPIDS_DIR_IN_CONTAINER="/rapids" +CPP_BUILD_DIR="cuML/build" +PYTHON_BUILD_DIR="python/build" +CONTAINER_SHELL_ONLY=0 + +SHORTHELP="$(basename "$0") [-h] [-H] [-s] [-r ] [-i ]" +LONGHELP="${SHORTHELP} +Build and test your local repository using a base gpuCI Docker image + +where: + -H Show this help text + -r Path to repository (defaults to working directory) + -i Use Docker image (default is ${DOCKER_IMAGE}) + -s Skip building and testing and start an interactive shell in a container of the Docker image +" + +# Limit GPUs available to container based on CUDA_VISIBLE_DEVICES +if [[ -z "${CUDA_VISIBLE_DEVICES}" ]]; then + NVIDIA_VISIBLE_DEVICES="all" +else + NVIDIA_VISIBLE_DEVICES=${CUDA_VISIBLE_DEVICES} +fi + +while getopts ":hHr:i:s" option; do + case ${option} in + r) + REPO_PATH=${OPTARG} + ;; + i) + DOCKER_IMAGE=${OPTARG} + ;; + s) + CONTAINER_SHELL_ONLY=1 + ;; + h) + echo "${SHORTHELP}" + exit 0 + ;; + H) + echo "${LONGHELP}" + exit 0 + ;; + *) + echo "ERROR: Invalid flag" + echo "${SHORTHELP}" + exit 1 + ;; + esac +done + +REPO_PATH_IN_CONTAINER="${RAPIDS_DIR_IN_CONTAINER}/$(basename "${REPO_PATH}")" +CPP_BUILD_DIR_IN_CONTAINER="${RAPIDS_DIR_IN_CONTAINER}/$(basename "${REPO_PATH}")/${CPP_BUILD_DIR}" +PYTHON_BUILD_DIR_IN_CONTAINER="${RAPIDS_DIR_IN_CONTAINER}/$(basename "${REPO_PATH}")/${PYTHON_BUILD_DIR}" + + +# BASE_CONTAINER_BUILD_DIR is named after the image name, allowing for +# multiple image builds to coexist on the local filesystem. This will +# be mapped to the typical BUILD_DIR inside of the container. Builds +# running in the container generate build artifacts just as they would +# in a bare-metal environment, and the host filesystem is able to +# maintain the host build in BUILD_DIR as well. +# shellcheck disable=SC2001,SC2005,SC2046 +BASE_CONTAINER_BUILD_DIR=${REPO_PATH}/build_$(echo $(basename "${DOCKER_IMAGE}")|sed -e 's/:/_/g') +CPP_CONTAINER_BUILD_DIR=${BASE_CONTAINER_BUILD_DIR}/cpp +PYTHON_CONTAINER_BUILD_DIR=${BASE_CONTAINER_BUILD_DIR}/python + + +BUILD_SCRIPT="#!/bin/bash +set -e +WORKSPACE=${REPO_PATH_IN_CONTAINER} +PREBUILD_SCRIPT=${REPO_PATH_IN_CONTAINER}/ci/gpu/prebuild.sh +BUILD_SCRIPT=${REPO_PATH_IN_CONTAINER}/ci/gpu/build.sh +cd \${WORKSPACE} +if [ -f \${PREBUILD_SCRIPT} ]; then + source \${PREBUILD_SCRIPT} +fi +yes | source \${BUILD_SCRIPT} +" + +if (( CONTAINER_SHELL_ONLY == 0 )); then + COMMAND="${CPP_BUILD_DIR_IN_CONTAINER}/build.sh || bash" +else + COMMAND="bash" +fi + +# Create the build dir for the container to mount, generate the build script inside of it +mkdir -p "${BASE_CONTAINER_BUILD_DIR}" +mkdir -p "${CPP_CONTAINER_BUILD_DIR}" +mkdir -p "${PYTHON_CONTAINER_BUILD_DIR}" +# Create build directories. This is to ensure correct owner for directories. If +# directories don't exist there is side effect from docker volume mounting creating build +# directories owned by root(volume mount point(s)) +mkdir -p "${REPO_PATH}/${CPP_BUILD_DIR}" +mkdir -p "${REPO_PATH}/${PYTHON_BUILD_DIR}" + +echo "${BUILD_SCRIPT}" > "${CPP_CONTAINER_BUILD_DIR}/build.sh" +chmod ugo+x "${CPP_CONTAINER_BUILD_DIR}/build.sh" +PASSWD_FILE="/etc/passwd" +GROUP_FILE="/etc/group" + +USER_FOUND=$(grep -wc "$(whoami)" < "$PASSWD_FILE") +if [ "$USER_FOUND" == 0 ]; then + echo "Local User not found, LDAP WAR for docker mounts activated. Creating dummy passwd and group" + echo "files to allow docker resolve username and group" + cp "$PASSWD_FILE" /tmp/passwd + PASSWD_FILE="/tmp/passwd" + cp "$GROUP_FILE" /tmp/group + GROUP_FILE="/tmp/group" + echo "$(whoami):x:$(id -u):$(id -g):$(whoami),,,:$HOME:$SHELL" >> "$PASSWD_FILE" + echo "$(whoami):x:$(id -g):" >> "$GROUP_FILE" +fi + +# Run the generated build script in a container +docker pull "${DOCKER_IMAGE}" +docker run --runtime=nvidia --rm -it -e NVIDIA_VISIBLE_DEVICES="${NVIDIA_VISIBLE_DEVICES}" \ + --user "$(id -u)":"$(id -g)" \ + -v "${REPO_PATH}:${REPO_PATH_IN_CONTAINER}" \ + -v "${CPP_CONTAINER_BUILD_DIR}:${CPP_BUILD_DIR_IN_CONTAINER}" \ + -v "${PYTHON_CONTAINER_BUILD_DIR}:${PYTHON_BUILD_DIR_IN_CONTAINER}" \ + -v "$PASSWD_FILE":/etc/passwd:ro \ + -v "$GROUP_FILE":/etc/group:ro \ + --cap-add=SYS_PTRACE \ + "${DOCKER_IMAGE}" bash -c "${COMMAND}" + diff --git a/ci/prtest.config b/ci/prtest.config new file mode 100644 index 0000000000..08bdcaa3ab --- /dev/null +++ b/ci/prtest.config @@ -0,0 +1,6 @@ +RUN_CUGRAPH_LIBCUGRAPH_TESTS=OFF +RUN_CUGRAPH_PYTHON_TESTS=OFF + +RUN_CUML_LIBCUML_TESTS=OFF +RUN_CUML_PRIMS_TESTS=OFF +RUN_CUML_PYTHON_TESTS=OFF diff --git a/ci/release/update-version.sh b/ci/release/update-version.sh new file mode 100755 index 0000000000..18fb7a3d2a --- /dev/null +++ b/ci/release/update-version.sh @@ -0,0 +1,62 @@ +#!/bin/bash +# Copyright (c) 2020, NVIDIA CORPORATION. +######################## +# cuML Version Updater # +######################## + +## Usage +# bash update-version.sh +# where is either `major`, `minor`, `patch` + +set -e + +# Grab argument for release type +RELEASE_TYPE=$1 + +# Get current version and calculate next versions +CURRENT_TAG=`git tag | grep -xE 'v[0-9\.]+' | sort --version-sort | tail -n 1 | tr -d 'v'` +CURRENT_MAJOR=`echo $CURRENT_TAG | awk '{split($0, a, "."); print a[1]}'` +CURRENT_MINOR=`echo $CURRENT_TAG | awk '{split($0, a, "."); print a[2]}'` +CURRENT_PATCH=`echo $CURRENT_TAG | awk '{split($0, a, "."); print a[3]}'` +CURRENT_SHORT_TAG=${CURRENT_MAJOR}.${CURRENT_MINOR} +NEXT_MAJOR=$((CURRENT_MAJOR + 1)) +NEXT_MINOR=$((CURRENT_MINOR + 1)) +NEXT_PATCH=$((CURRENT_PATCH + 1)) +NEXT_FULL_TAG="" +NEXT_SHORT_TAG="" + +# Determine release type +if [ "$RELEASE_TYPE" == "major" ]; then + NEXT_FULL_TAG="${NEXT_MAJOR}.0.0" + NEXT_SHORT_TAG="${NEXT_MAJOR}.0" +elif [ "$RELEASE_TYPE" == "minor" ]; then + NEXT_FULL_TAG="${CURRENT_MAJOR}.${NEXT_MINOR}.0" + NEXT_SHORT_TAG="${CURRENT_MAJOR}.${NEXT_MINOR}" +elif [ "$RELEASE_TYPE" == "patch" ]; then + NEXT_FULL_TAG="${CURRENT_MAJOR}.${CURRENT_MINOR}.${NEXT_PATCH}" + NEXT_SHORT_TAG="${CURRENT_MAJOR}.${CURRENT_MINOR}" +else + echo "Incorrect release type; use 'major', 'minor', or 'patch' as an argument" + exit 1 +fi + +echo "Preparing '$RELEASE_TYPE' release [$CURRENT_TAG -> $NEXT_FULL_TAG]" + +# Inplace sed replace; workaround for Linux and Mac +function sed_runner() { + sed -i.bak ''"$1"'' $2 && rm -f ${2}.bak +} + +sed_runner 's/'"RAFT VERSION .* LANGUAGES"'/'"RAFT VERSION ${NEXT_FULL_TAG} LANGUAGES"'/g' cpp/CMakeLists.txt +# RTD update +sed_runner 's/version = .*/version = '"'${NEXT_SHORT_TAG}'"'/g' docs/source/conf.py +sed_runner 's/release = .*/release = '"'${NEXT_FULL_TAG}'"'/g' docs/source/conf.py + +for FILE in conda/environments/*.yml; do + sed_runner "s/cudf=${CURRENT_SHORT_TAG}/cudf=${NEXT_SHORT_TAG}/g" ${FILE}; + sed_runner "s/rmm=${CURRENT_SHORT_TAG}/rmm=${NEXT_SHORT_TAG}/g" ${FILE}; + sed_runner "s/dask-cuda=${CURRENT_SHORT_TAG}/dask-cuda=${NEXT_SHORT_TAG}/g" ${FILE}; + sed_runner "s/dask-cudf=${CURRENT_SHORT_TAG}/dask-cudf=${NEXT_SHORT_TAG}/g" ${FILE}; + sed_runner "s/ucx-py=${CURRENT_SHORT_TAG}/ucx-py=${NEXT_SHORT_TAG}/g" ${FILE}; + sed_runner "s/libcumlprims=${CURRENT_SHORT_TAG}/libcumlprims=${NEXT_SHORT_TAG}/g" ${FILE}; +done diff --git a/cpp/CMakeLists.txt b/cpp/CMakeLists.txt new file mode 100644 index 0000000000..7163b0dd77 --- /dev/null +++ b/cpp/CMakeLists.txt @@ -0,0 +1,180 @@ +#============================================================================= +# Copyright (c) 2020, NVIDIA CORPORATION. +# +# Licensed under the Apache License, Version 2.0 (the "License"); +# you may not use this file except in compliance with the License. +# You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +#============================================================================= + + +cmake_minimum_required(VERSION 3.14 FATAL_ERROR) + +project(CUML VERSION 0.14.0 LANGUAGES CXX CUDA) + +############################################################################## +# - build type --------------------------------------------------------------- + +# Set a default build type if none was specified +set(DEFAULT_BUILD_TYPE "Release") + +if(NOT CMAKE_BUILD_TYPE AND NOT CMAKE_CONFIGURATION_TYPES) + message(STATUS "Setting build type to '${DEFAULT_BUILD_TYPE}' since none specified.") + set(CMAKE_BUILD_TYPE "${DEFAULT_BUILD_TYPE}" CACHE + STRING "Choose the type of build." FORCE) + # Set the possible values of build type for cmake-gui + set_property(CACHE CMAKE_BUILD_TYPE PROPERTY STRINGS + "Debug" "Release") +endif() + +############################################################################## +# - User Options ------------------------------------------------------------ + +option(EMPTY_MARKER_KERNEL "Enable empty marker kernel after nvtxRangePop" ON) + +option(KERNEL_INFO "Enable kernel resource usage info" OFF) + +option(LINE_INFO "Enable lineinfo in nvcc" OFF) + +option(NVTX "Enable nvtx markers" OFF) + +set(PARALLEL_LEVEL "" CACHE STRING + "Sub-projects parallel level for compilation. Currently only affects FAISS" ) + +set(GPU_ARCHS "" CACHE STRING + "List of GPU architectures (semicolon-separated) to be compiled for. + Pass 'ALL' if you want to compile for all supported GPU architectures. + Empty string means to auto-detect the GPUs on the current system") + + +############################################################################## +# - Requirements ------------------------------------------------------------- + +find_package(CUDA 10.0 REQUIRED) + +############################################################################## +# - Compiler Options -------------------------------------------------------- + +set(CMAKE_CXX_STANDARD 14) +set(CMAKE_CXX_STANDARD_REQUIRED ON) + +if(CMAKE_CUDA_HOST_COMPILER) + # If CMAKE_CUDA_HOST_COMPILER is set to a nonempty string cmake was called with the environment variable CUDAHOSTCXX set or -DCMAKE_CUDA_HOST_COMPILER + if(NOT CMAKE_CUDA_HOST_COMPILER STREQUAL CMAKE_CXX_COMPILER) + message(WARNING "CMAKE_CUDA_HOST_COMPILER=${CMAKE_CUDA_HOST_COMPILER} and CMAKE_CXX_COMPILER=${CMAKE_CXX_COMPILER} are inconsistent!") + endif(NOT CMAKE_CUDA_HOST_COMPILER STREQUAL CMAKE_CXX_COMPILER) +else() + # No attempt to set CMAKE_CUDA_HOST_COMPILER has been made. Make sure CMAKE_CXX_COMPILER is used as CUDA host compiler. + set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} -ccbin ${CMAKE_CXX_COMPILER}") +endif(CMAKE_CUDA_HOST_COMPILER) + +if(OPENMP_FOUND) + message(STATUS "Building with OpenMP support") + find_package(Threads REQUIRED) + set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} -Xcompiler ${OpenMP_CXX_FLAGS}") + set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${OpenMP_CXX_FLAGS}") +endif(OPENMP_FOUND) + +set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} --expt-extended-lambda") + +if(${CMAKE_VERSION} VERSION_LESS "3.17.0") + set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} --std=c++11") +endif(${CMAKE_VERSION} VERSION_LESS "3.17.0") + +if(LINE_INFO) + set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} -lineinfo") +endif(LINE_INFO) + +if(KERNEL_INFO) + set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} -Xptxas=-v") +endif(KERNEL_INFO) + +if(NVTX) + set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} -DNVTX_ENABLED") + set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -DNVTX_ENABLED") + if(EMPTY_MARKER_KERNEL) + set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} -DENABLE_EMPTY_MARKER_KERNEL") + endif(EMPTY_MARKER_KERNEL) +endif(NVTX) + +if(CMAKE_BUILD_TYPE MATCHES Debug) + set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} -G -g") + set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -g") +endif() + +if("${GPU_ARCHS}" STREQUAL "") + include(cmake/EvalGpuArchs.cmake) + evaluate_gpu_archs(GPU_ARCHS) +endif() + +if("${GPU_ARCHS}" STREQUAL "ALL") + set(GPU_ARCHS "60") + if((CUDA_VERSION_MAJOR EQUAL 9) OR (CUDA_VERSION_MAJOR GREATER 9)) + set(GPU_ARCHS "${GPU_ARCHS};70") + endif() + if((CUDA_VERSION_MAJOR EQUAL 10) OR (CUDA_VERSION_MAJOR GREATER 10)) + set(GPU_ARCHS "${GPU_ARCHS};75") + endif() +endif() + +message("-- Building for GPU_ARCHS = ${GPU_ARCHS}") + +foreach(arch ${GPU_ARCHS}) + set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} -gencode arch=compute_${arch},code=sm_${arch}") + set(FAISS_GPU_ARCHS "${FAISS_GPU_ARCHS} -gencode arch=compute_${arch},code=sm_${arch}") +endforeach() + +list(GET GPU_ARCHS -1 ptx) +set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} -gencode arch=compute_${ptx},code=compute_${ptx}") +set(FAISS_GPU_ARCHS "${FAISS_GPU_ARCHS} -gencode arch=compute_${ptx},code=compute_${ptx}") + +if(CMAKE_COMPILER_IS_GNUCXX) + if(NOT CMAKE_CXX11_ABI) + message(STATUS "Disabling the GLIBCXX11 ABI") + set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -D_GLIBCXX_USE_CXX11_ABI=0") + set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -D_GLIBCXX_USE_CXX11_ABI=0") + set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} -Xcompiler -D_GLIBCXX_USE_CXX11_ABI=0") + elseif(CMAKE_CXX11_ABI) + message(STATUS "Enabling the GLIBCXX11 ABI") + endif(NOT CMAKE_CXX11_ABI) +endif(CMAKE_COMPILER_IS_GNUCXX) + +set(CMAKE_CUDA_FLAGS + "${CMAKE_CUDA_FLAGS} -Xcudafe --diag_suppress=unrecognized_gcc_pragma") + + + + +############################################################################## +# - include paths ------------------------------------------------------------ + +set(RAFT_INCLUDE_DIR ${CMAKE_CURRENT_SOURCE_DIR}/include CACHE STRING + "Path to RAFT include directories") + +set(RAFT_INCLUDE_DIRECTORIES + ${RAFT_INCLUDE_DIR} +) + +############################################################################## +# - build test executables --------------------------------------------------- + +add_executable(test_raft + test/test.cpp) + +target_include_directories(test_raft PRIVATE + ${RAFT_INCLUDE_DIRECTORIES}) + +############################################################################## +# - doxygen targets ---------------------------------------------------------- + +include(cmake/doxygen.cmake) +add_doxygen_target(IN_DOXYFILE Doxyfile.in + OUT_DOXYFILE ${CMAKE_CURRENT_BINARY_DIR}/Doxyfile + CWD ${CMAKE_CURRENT_BINARY_DIR}) diff --git a/cpp/Doxyfile.in b/cpp/Doxyfile.in new file mode 100644 index 0000000000..8a6a8e731e --- /dev/null +++ b/cpp/Doxyfile.in @@ -0,0 +1,2436 @@ +# Doxyfile 1.8.11 + +# This file describes the settings to be used by the documentation system +# doxygen (www.doxygen.org) for a project. +# +# All text after a double hash (##) is considered a comment and is placed in +# front of the TAG it is preceding. +# +# All text after a single hash (#) is considered a comment and will be ignored. +# The format is: +# TAG = value [value, ...] +# For lists, items can also be appended using: +# TAG += value [value, ...] +# Values that contain spaces should be placed between quotes (\" \"). + +#--------------------------------------------------------------------------- +# Project related configuration options +#--------------------------------------------------------------------------- + +# This tag specifies the encoding used for all characters in the config file +# that follow. The default is UTF-8 which is also the encoding used for all text +# before the first occurrence of this tag. Doxygen uses libiconv (or the iconv +# built into libc) for the transcoding. See http://www.gnu.org/software/libiconv +# for the list of possible encodings. +# The default value is: UTF-8. + +DOXYFILE_ENCODING = UTF-8 + +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded by +# double-quotes, unless you are using Doxywizard) that should identify the +# project for which the documentation is generated. This name is used in the +# title of most generated pages and in a few other places. +# The default value is: My Project. + +PROJECT_NAME = "RAFT C++ API" + +# The PROJECT_NUMBER tag can be used to enter a project or revision number. This +# could be handy for archiving the generated documentation or if some version +# control system is used. + +PROJECT_NUMBER = @RAFT_VERSION@ + +# 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 +# quick idea about the purpose of the project. Keep the description short. + +PROJECT_BRIEF = + +# With the PROJECT_LOGO tag one can specify a logo or an icon that is included +# in the documentation. The maximum height of the logo should not exceed 55 +# pixels and the maximum width should not exceed 200 pixels. Doxygen will copy +# the logo to the output directory. + +PROJECT_LOGO = + +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path +# into which the generated documentation will be written. If a relative path is +# entered, it will be relative to the location where doxygen was started. If +# left blank the current directory will be used. + +OUTPUT_DIRECTORY = @CMAKE_CURRENT_BINARY_DIR@ + +# If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub- +# directories (in 2 levels) under the output directory of each output format and +# will distribute the generated files over these directories. Enabling this +# option can be useful when feeding doxygen a huge amount of source files, where +# putting all generated files in the same directory would otherwise causes +# performance problems for the file system. +# The default value is: NO. + +CREATE_SUBDIRS = NO + +# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII +# characters to appear in the names of generated files. If set to NO, non-ASCII +# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode +# U+3044. +# The default value is: NO. + +ALLOW_UNICODE_NAMES = NO + +# The OUTPUT_LANGUAGE tag is used to specify the language in which all +# documentation generated by doxygen is written. Doxygen will use this +# information to generate all constant output in the proper language. +# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese, +# Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States), +# Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian, +# Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages), +# Korean, Korean-en (Korean with English messages), Latvian, Lithuanian, +# Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian, +# Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish, +# Ukrainian and Vietnamese. +# The default value is: English. + +OUTPUT_LANGUAGE = English + +# If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member +# descriptions after the members that are listed in the file and class +# documentation (similar to Javadoc). Set to NO to disable this. +# The default value is: YES. + +BRIEF_MEMBER_DESC = YES + +# If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief +# description of a member or function before the detailed description +# +# Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the +# brief descriptions will be completely suppressed. +# The default value is: YES. + +REPEAT_BRIEF = YES + +# This tag implements a quasi-intelligent brief description abbreviator that is +# used to form the text in various listings. Each string in this list, if found +# as the leading text of the brief description, will be stripped from the text +# and the result, after processing the whole list, is used as the annotated +# text. Otherwise, the brief description is used as-is. If left blank, the +# following values are used ($name is automatically replaced with the name of +# the entity):The $name class, The $name widget, The $name file, is, provides, +# specifies, contains, represents, a, an and the. + +ABBREVIATE_BRIEF = + +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then +# doxygen will generate a detailed section even if there is only a brief +# description. +# The default value is: NO. + +ALWAYS_DETAILED_SEC = NO + +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all +# inherited members of a class in the documentation of that class as if those +# members were ordinary class members. Constructors, destructors and assignment +# operators of the base classes will not be shown. +# The default value is: NO. + +INLINE_INHERITED_MEMB = NO + +# If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path +# before files name in the file list and in the header files. If set to NO the +# shortest path that makes the file name unique will be used +# The default value is: YES. + +FULL_PATH_NAMES = YES + +# The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path. +# Stripping is only done if one of the specified strings matches the left-hand +# part of the path. The tag can be used to show relative paths in the file list. +# If left blank the directory from which doxygen is run is used as the path to +# strip. +# +# Note that you can specify absolute paths here, but also relative paths, which +# will be relative from the directory where doxygen is started. +# This tag requires that the tag FULL_PATH_NAMES is set to YES. + +STRIP_FROM_PATH = + +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the +# path mentioned in the documentation of a class, which tells the reader which +# header file to include in order to use a class. If left blank only the name of +# the header file containing the class definition is used. Otherwise one should +# specify the list of include paths that are normally passed to the compiler +# using the -I flag. + +STRIP_FROM_INC_PATH = + +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but +# less readable) file names. This can be useful is your file systems doesn't +# support long names like on DOS, Mac, or CD-ROM. +# The default value is: NO. + +SHORT_NAMES = NO + +# If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the +# first line (until the first dot) of a Javadoc-style comment as the brief +# description. If set to NO, the Javadoc-style will behave just like regular Qt- +# style comments (thus requiring an explicit @brief command for a brief +# description.) +# The default value is: NO. + +JAVADOC_AUTOBRIEF = NO + +# If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first +# line (until the first dot) of a Qt-style comment as the brief description. If +# set to NO, the Qt-style will behave just like regular Qt-style comments (thus +# requiring an explicit \brief command for a brief description.) +# The default value is: NO. + +QT_AUTOBRIEF = NO + +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a +# multi-line C++ special comment block (i.e. a block of //! or /// comments) as +# a brief description. This used to be the default behavior. The new default is +# to treat a multi-line C++ comment block as a detailed description. Set this +# tag to YES if you prefer the old behavior instead. +# +# Note that setting this tag to YES also means that rational rose comments are +# not recognized any more. +# The default value is: NO. + +MULTILINE_CPP_IS_BRIEF = NO + +# If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the +# documentation from any documented member that it re-implements. +# The default value is: YES. + +INHERIT_DOCS = YES + +# If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new +# page for each member. If set to NO, the documentation of a member will be part +# of the file/class/namespace that contains it. +# The default value is: NO. + +SEPARATE_MEMBER_PAGES = NO + +# The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen +# uses this value to replace tabs by spaces in code fragments. +# Minimum value: 1, maximum value: 16, default value: 4. + +TAB_SIZE = 4 + +# This tag can be used to specify a number of aliases that act as commands in +# the documentation. An alias has the form: +# name=value +# For example adding +# "sideeffect=@par Side Effects:\n" +# will allow you to put the command \sideeffect (or @sideeffect) in the +# documentation, which will result in a user-defined paragraph with heading +# "Side Effects:". You can put \n's in the value part of an alias to insert +# newlines. + +ALIASES = + +# This tag can be used to specify a number of word-keyword mappings (TCL only). +# A mapping has the form "name=value". For example adding "class=itcl::class" +# will allow you to use the command class in the itcl::class meaning. + +TCL_SUBST = + +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources +# only. Doxygen will then generate output that is more tailored for C. For +# instance, some of the names that are used will be different. The list of all +# members will be omitted, etc. +# The default value is: NO. + +OPTIMIZE_OUTPUT_FOR_C = NO + +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or +# Python sources only. Doxygen will then generate output that is more tailored +# for that language. For instance, namespaces will be presented as packages, +# qualified scopes will look different, etc. +# The default value is: NO. + +OPTIMIZE_OUTPUT_JAVA = NO + +# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran +# sources. Doxygen will then generate output that is tailored for Fortran. +# The default value is: NO. + +OPTIMIZE_FOR_FORTRAN = NO + +# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL +# sources. Doxygen will then generate output that is tailored for VHDL. +# The default value is: NO. + +OPTIMIZE_OUTPUT_VHDL = NO + +# Doxygen selects the parser to use depending on the extension of the files it +# parses. With this tag you can assign which parser to use for a given +# extension. Doxygen has a built-in mapping, but you can override or extend it +# using this tag. The format is ext=language, where ext is a file extension, and +# language is one of the parsers supported by doxygen: IDL, Java, Javascript, +# C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran: +# FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran: +# Fortran. In the later case the parser tries to guess whether the code is fixed +# or free formatted code, this is the default for Fortran type files), VHDL. For +# instance to make doxygen treat .inc files as Fortran files (default is PHP), +# and .f files as C (default is Fortran), use: inc=Fortran f=C. +# +# Note: For files without extension you can use no_extension as a placeholder. +# +# Note that for custom extensions you also need to set FILE_PATTERNS otherwise +# the files are not read by doxygen. + +EXTENSION_MAPPING = + +# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments +# according to the Markdown format, which allows for more readable +# documentation. See http://daringfireball.net/projects/markdown/ for details. +# The output of markdown processing is further processed by doxygen, so you can +# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in +# case of backward compatibilities issues. +# The default value is: YES. + +MARKDOWN_SUPPORT = YES + +# When enabled doxygen tries to link words that correspond to documented +# classes, or namespaces to their corresponding documentation. Such a link can +# be prevented in individual cases by putting a % sign in front of the word or +# globally by setting AUTOLINK_SUPPORT to NO. +# The default value is: YES. + +AUTOLINK_SUPPORT = YES + +# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want +# to include (a tag file for) the STL sources as input, then you should set this +# tag to YES in order to let doxygen match functions declarations and +# definitions whose arguments contain STL classes (e.g. func(std::string); +# versus func(std::string) {}). This also make the inheritance and collaboration +# diagrams that involve STL classes more complete and accurate. +# The default value is: NO. + +BUILTIN_STL_SUPPORT = NO + +# If you use Microsoft's C++/CLI language, you should set this option to YES to +# enable parsing support. +# The default value is: NO. + +CPP_CLI_SUPPORT = NO + +# Set the SIP_SUPPORT tag to YES if your project consists of sip (see: +# http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen +# will parse them like normal C++ but will assume all classes use public instead +# of private inheritance when no explicit protection keyword is present. +# The default value is: NO. + +SIP_SUPPORT = NO + +# For Microsoft's IDL there are propget and propput attributes to indicate +# getter and setter methods for a property. Setting this option to YES will make +# doxygen to replace the get and set methods by a property in the documentation. +# This will only work if the methods are indeed getting or setting a simple +# type. If this is not the case, or you want to show the methods anyway, you +# should set this option to NO. +# The default value is: YES. + +IDL_PROPERTY_SUPPORT = YES + +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC +# tag is set to YES then doxygen will reuse the documentation of the first +# member in the group (if any) for the other members of the group. By default +# all members of a group must be documented explicitly. +# The default value is: NO. + +DISTRIBUTE_GROUP_DOC = NO + +# If one adds a struct or class to a group and this option is enabled, then also +# any nested class or struct is added to the same group. By default this option +# is disabled and one has to add nested compounds explicitly via \ingroup. +# The default value is: NO. + +GROUP_NESTED_COMPOUNDS = NO + +# Set the SUBGROUPING tag to YES to allow class member groups of the same type +# (for instance a group of public functions) to be put as a subgroup of that +# type (e.g. under the Public Functions section). Set it to NO to prevent +# subgrouping. Alternatively, this can be done per class using the +# \nosubgrouping command. +# The default value is: YES. + +SUBGROUPING = YES + +# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions +# are shown inside the group in which they are included (e.g. using \ingroup) +# instead of on a separate page (for HTML and Man pages) or section (for LaTeX +# and RTF). +# +# Note that this feature does not work in combination with +# SEPARATE_MEMBER_PAGES. +# The default value is: NO. + +INLINE_GROUPED_CLASSES = NO + +# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions +# with only public data fields or simple typedef fields will be shown inline in +# the documentation of the scope in which they are defined (i.e. file, +# namespace, or group documentation), provided this scope is documented. If set +# to NO, structs, classes, and unions are shown on a separate page (for HTML and +# Man pages) or section (for LaTeX and RTF). +# The default value is: NO. + +INLINE_SIMPLE_STRUCTS = NO + +# When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or +# enum is documented as struct, union, or enum with the name of the typedef. So +# typedef struct TypeS {} TypeT, will appear in the documentation as a struct +# with name TypeT. When disabled the typedef will appear as a member of a file, +# namespace, or class. And the struct will be named TypeS. This can typically be +# useful for C code in case the coding convention dictates that all compound +# types are typedef'ed and only the typedef is referenced, never the tag name. +# The default value is: NO. + +TYPEDEF_HIDES_STRUCT = NO + +# The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This +# cache is used to resolve symbols given their name and scope. Since this can be +# an expensive process and often the same symbol appears multiple times in the +# code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small +# doxygen will become slower. If the cache is too large, memory is wasted. The +# cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range +# is 0..9, the default is 0, corresponding to a cache size of 2^16=65536 +# symbols. At the end of a run doxygen will report the cache usage and suggest +# the optimal cache size from a speed point of view. +# Minimum value: 0, maximum value: 9, default value: 0. + +LOOKUP_CACHE_SIZE = 0 + +#--------------------------------------------------------------------------- +# Build related configuration options +#--------------------------------------------------------------------------- + +# If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in +# documentation are documented, even if no documentation was available. Private +# class members and static file members will be hidden unless the +# EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES. +# Note: This will also disable the warnings about undocumented members that are +# normally produced when WARNINGS is set to YES. +# The default value is: NO. + +EXTRACT_ALL = YES + +# If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will +# be included in the documentation. +# The default value is: NO. + +EXTRACT_PRIVATE = NO + +# If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal +# scope will be included in the documentation. +# The default value is: NO. + +EXTRACT_PACKAGE = NO + +# If the EXTRACT_STATIC tag is set to YES, all static members of a file will be +# included in the documentation. +# The default value is: NO. + +EXTRACT_STATIC = NO + +# If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined +# locally in source files will be included in the documentation. If set to NO, +# only classes defined in header files are included. Does not have any effect +# for Java sources. +# The default value is: YES. + +EXTRACT_LOCAL_CLASSES = NO + +# This flag is only useful for Objective-C code. If set to YES, local methods, +# which are defined in the implementation section but not in the interface are +# included in the documentation. If set to NO, only methods in the interface are +# included. +# The default value is: NO. + +EXTRACT_LOCAL_METHODS = NO + +# If this flag is set to YES, the members of anonymous namespaces will be +# extracted and appear in the documentation as a namespace called +# 'anonymous_namespace{file}', where file will be replaced with the base name of +# the file that contains the anonymous namespace. By default anonymous namespace +# are hidden. +# The default value is: NO. + +EXTRACT_ANON_NSPACES = NO + +# If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all +# undocumented members inside documented classes or files. If set to NO these +# members will be included in the various overviews, but no documentation +# section is generated. This option has no effect if EXTRACT_ALL is enabled. +# The default value is: NO. + +HIDE_UNDOC_MEMBERS = NO + +# If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all +# undocumented classes that are normally visible in the class hierarchy. If set +# to NO, these classes will be included in the various overviews. This option +# has no effect if EXTRACT_ALL is enabled. +# The default value is: NO. + +HIDE_UNDOC_CLASSES = NO + +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend +# (class|struct|union) declarations. If set to NO, these declarations will be +# included in the documentation. +# The default value is: NO. + +HIDE_FRIEND_COMPOUNDS = NO + +# If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any +# documentation blocks found inside the body of a function. If set to NO, these +# blocks will be appended to the function's detailed documentation block. +# The default value is: NO. + +HIDE_IN_BODY_DOCS = NO + +# The INTERNAL_DOCS tag determines if documentation that is typed after a +# \internal command is included. If the tag is set to NO then the documentation +# will be excluded. Set it to YES to include the internal documentation. +# The default value is: NO. + +INTERNAL_DOCS = NO + +# If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file +# names in lower-case letters. If set to YES, upper-case letters are also +# allowed. This is useful if you have classes or files whose names only differ +# in case and if your file system supports case sensitive file names. Windows +# and Mac users are advised to set this option to NO. +# The default value is: system dependent. + +CASE_SENSE_NAMES = YES + +# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with +# their full class and namespace scopes in the documentation. If set to YES, the +# scope will be hidden. +# The default value is: NO. + +HIDE_SCOPE_NAMES = NO + +# If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will +# append additional text to a page's title, such as Class Reference. If set to +# YES the compound reference will be hidden. +# The default value is: NO. + +HIDE_COMPOUND_REFERENCE= NO + +# If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of +# the files that are included by a file in the documentation of that file. +# The default value is: YES. + +SHOW_INCLUDE_FILES = YES + +# If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each +# grouped member an include statement to the documentation, telling the reader +# which file to include in order to use the member. +# The default value is: NO. + +SHOW_GROUPED_MEMB_INC = NO + +# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include +# files with double quotes in the documentation rather than with sharp brackets. +# The default value is: NO. + +FORCE_LOCAL_INCLUDES = NO + +# If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the +# documentation for inline members. +# The default value is: YES. + +INLINE_INFO = YES + +# If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the +# (detailed) documentation of file and class members alphabetically by member +# name. If set to NO, the members will appear in declaration order. +# The default value is: YES. + +SORT_MEMBER_DOCS = YES + +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief +# descriptions of file, namespace and class members alphabetically by member +# name. If set to NO, the members will appear in declaration order. Note that +# this will also influence the order of the classes in the class list. +# The default value is: NO. + +SORT_BRIEF_DOCS = NO + +# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the +# (brief and detailed) documentation of class members so that constructors and +# destructors are listed first. If set to NO the constructors will appear in the +# respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS. +# Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief +# member documentation. +# Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting +# detailed member documentation. +# The default value is: NO. + +SORT_MEMBERS_CTORS_1ST = NO + +# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy +# of group names into alphabetical order. If set to NO the group names will +# appear in their defined order. +# The default value is: NO. + +SORT_GROUP_NAMES = NO + +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by +# fully-qualified names, including namespaces. If set to NO, the class list will +# be sorted only by class name, not including the namespace part. +# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. +# Note: This option applies only to the class list, not to the alphabetical +# list. +# The default value is: NO. + +SORT_BY_SCOPE_NAME = NO + +# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper +# type resolution of all parameters of a function it will reject a match between +# the prototype and the implementation of a member function even if there is +# only one candidate or it is obvious which candidate to choose by doing a +# simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still +# accept a match between prototype and implementation in such cases. +# The default value is: NO. + +STRICT_PROTO_MATCHING = NO + +# The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo +# list. This list is created by putting \todo commands in the documentation. +# The default value is: YES. + +GENERATE_TODOLIST = YES + +# The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test +# list. This list is created by putting \test commands in the documentation. +# The default value is: YES. + +GENERATE_TESTLIST = YES + +# The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug +# list. This list is created by putting \bug commands in the documentation. +# The default value is: YES. + +GENERATE_BUGLIST = YES + +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO) +# the deprecated list. This list is created by putting \deprecated commands in +# the documentation. +# The default value is: YES. + +GENERATE_DEPRECATEDLIST= YES + +# The ENABLED_SECTIONS tag can be used to enable conditional documentation +# sections, marked by \if ... \endif and \cond +# ... \endcond blocks. + +ENABLED_SECTIONS = + +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the +# initial value of a variable or macro / define can have for it to appear in the +# documentation. If the initializer consists of more lines than specified here +# it will be hidden. Use a value of 0 to hide initializers completely. The +# appearance of the value of individual variables and macros / defines can be +# controlled using \showinitializer or \hideinitializer command in the +# documentation regardless of this setting. +# Minimum value: 0, maximum value: 10000, default value: 30. + +MAX_INITIALIZER_LINES = 30 + +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated at +# the bottom of the documentation of classes and structs. If set to YES, the +# list will mention the files that were used to generate the documentation. +# The default value is: YES. + +SHOW_USED_FILES = YES + +# Set the SHOW_FILES tag to NO to disable the generation of the Files page. This +# will remove the Files entry from the Quick Index and from the Folder Tree View +# (if specified). +# The default value is: YES. + +SHOW_FILES = YES + +# Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces +# page. This will remove the Namespaces entry from the Quick Index and from the +# Folder Tree View (if specified). +# The default value is: YES. + +SHOW_NAMESPACES = YES + +# The FILE_VERSION_FILTER tag can be used to specify a program or script that +# doxygen should invoke to get the current version for each file (typically from +# the version control system). Doxygen will invoke the program by executing (via +# popen()) the command command input-file, where command is the value of the +# FILE_VERSION_FILTER tag, and input-file is the name of an input file provided +# by doxygen. Whatever the program writes to standard output is used as the file +# version. For an example see the documentation. + +FILE_VERSION_FILTER = + +# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed +# by doxygen. The layout file controls the global structure of the generated +# output files in an output format independent way. To create the layout file +# that represents doxygen's defaults, run doxygen with the -l option. You can +# optionally specify a file name after the option, if omitted DoxygenLayout.xml +# will be used as the name of the layout file. +# +# Note that if you run doxygen from a directory containing a file called +# DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE +# tag is left empty. + +LAYOUT_FILE = + +# The CITE_BIB_FILES tag can be used to specify one or more bib files containing +# the reference definitions. This must be a list of .bib files. The .bib +# extension is automatically appended if omitted. This requires the bibtex tool +# to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info. +# For LaTeX the style of the bibliography can be controlled using +# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the +# search path. See also \cite for info how to create references. + +CITE_BIB_FILES = + +#--------------------------------------------------------------------------- +# Configuration options related to warning and progress messages +#--------------------------------------------------------------------------- + +# The QUIET tag can be used to turn on/off the messages that are generated to +# standard output by doxygen. If QUIET is set to YES this implies that the +# messages are off. +# The default value is: NO. + +QUIET = NO + +# The WARNINGS tag can be used to turn on/off the warning messages that are +# generated to standard error (stderr) by doxygen. If WARNINGS is set to YES +# this implies that the warnings are on. +# +# Tip: Turn warnings on while writing the documentation. +# The default value is: YES. + +WARNINGS = YES + +# If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate +# warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag +# will automatically be disabled. +# The default value is: YES. + +WARN_IF_UNDOCUMENTED = YES + +# If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for +# potential errors in the documentation, such as not documenting some parameters +# in a documented function, or documenting parameters that don't exist or using +# markup commands wrongly. +# The default value is: YES. + +WARN_IF_DOC_ERROR = YES + +# This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that +# are documented, but have no documentation for their parameters or return +# value. If set to NO, doxygen will only warn about wrong or incomplete +# parameter documentation, but not about the absence of documentation. +# The default value is: NO. + +WARN_NO_PARAMDOC = YES + +# If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when +# a warning is encountered. +# The default value is: NO. + +WARN_AS_ERROR = YES + +# The WARN_FORMAT tag determines the format of the warning messages that doxygen +# can produce. The string should contain the $file, $line, and $text tags, which +# will be replaced by the file and line number from which the warning originated +# and the warning text. Optionally the format may contain $version, which will +# be replaced by the version of the file (if it could be obtained via +# FILE_VERSION_FILTER) +# The default value is: $file:$line: $text. + +WARN_FORMAT = "$file:$line: $text" + +# The WARN_LOGFILE tag can be used to specify a file to which warning and error +# messages should be written. If left blank the output is written to standard +# error (stderr). + +WARN_LOGFILE = + +#--------------------------------------------------------------------------- +# Configuration options related to the input files +#--------------------------------------------------------------------------- + +# The INPUT tag is used to specify the files and/or directories that contain +# documented source files. You may enter file names like myfile.cpp or +# directories like /usr/src/myproject. Separate the files or directories with +# spaces. See also FILE_PATTERNS and EXTENSION_MAPPING +# Note: If this tag is empty the current directory is searched. + +INPUT = @CMAKE_CURRENT_SOURCE_DIR@/comms \ + @CMAKE_CURRENT_SOURCE_DIR@/include \ + @CMAKE_CURRENT_SOURCE_DIR@/src \ + @CMAKE_CURRENT_SOURCE_DIR@/src_prims + +# This tag can be used to specify the character encoding of the source files +# that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses +# libiconv (or the iconv built into libc) for the transcoding. See the libiconv +# documentation (see: http://www.gnu.org/software/libiconv) for the list of +# possible encodings. +# The default value is: UTF-8. + +INPUT_ENCODING = UTF-8 + +# If the value of the INPUT tag contains directories, you can use the +# FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and +# *.h) to filter out the source-files in the directories. +# +# Note that for custom extensions or not directly supported extensions you also +# need to set EXTENSION_MAPPING for the extension otherwise the files are not +# read by doxygen. +# +# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp, +# *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, +# *.hh, *.hxx, *.hpp, *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, +# *.m, *.markdown, *.md, *.mm, *.dox, *.py, *.pyw, *.f90, *.f, *.for, *.tcl, +# *.vhd, *.vhdl, *.ucf, *.qsf, *.as and *.js. + +FILE_PATTERNS = *.cpp \ + *.h \ + *.hpp \ + *.hxx \ + *.cu \ + *.cuh + +# The RECURSIVE tag can be used to specify whether or not subdirectories should +# be searched for input files as well. +# The default value is: NO. + +RECURSIVE = YES + +# The EXCLUDE tag can be used to specify files and/or directories that should be +# excluded from the INPUT source files. This way you can easily exclude a +# subdirectory from a directory tree whose root is specified with the INPUT tag. +# +# Note that relative paths are relative to the directory from which doxygen is +# run. + +EXCLUDE = + +# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or +# directories that are symbolic links (a Unix file system feature) are excluded +# from the input. +# The default value is: NO. + +EXCLUDE_SYMLINKS = NO + +# If the value of the INPUT tag contains directories, you can use the +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude +# certain files from those directories. +# +# Note that the wildcards are matched against the file with absolute path, so to +# exclude all test directories for example use the pattern */test/* + +EXCLUDE_PATTERNS = columnWiseSort.h \ + smoblocksolve.h + +# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names +# (namespaces, classes, functions, etc.) that should be excluded from the +# output. The symbol name can be a fully qualified name, a word, or if the +# wildcard * is used, a substring. Examples: ANamespace, AClass, +# AClass::ANamespace, ANamespace::*Test +# +# Note that the wildcards are matched against the file with absolute path, so to +# exclude all test directories use the pattern */test/* + +EXCLUDE_SYMBOLS = + +# The EXAMPLE_PATH tag can be used to specify one or more files or directories +# that contain example code fragments that are included (see the \include +# command). + +EXAMPLE_PATH = + +# If the value of the EXAMPLE_PATH tag contains directories, you can use the +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and +# *.h) to filter out the source-files in the directories. If left blank all +# files are included. + +EXAMPLE_PATTERNS = + +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be +# searched for input files to be used with the \include or \dontinclude commands +# irrespective of the value of the RECURSIVE tag. +# The default value is: NO. + +EXAMPLE_RECURSIVE = NO + +# The IMAGE_PATH tag can be used to specify one or more files or directories +# that contain images that are to be included in the documentation (see the +# \image command). + +IMAGE_PATH = @CMAKE_CURRENT_SOURCE_DIR@/doxygen/images + +# The INPUT_FILTER tag can be used to specify a program that doxygen should +# invoke to filter for each input file. Doxygen will invoke the filter program +# by executing (via popen()) the command: +# +# +# +# where is the value of the INPUT_FILTER tag, and is the +# name of an input file. Doxygen will then use the output that the filter +# program writes to standard output. If FILTER_PATTERNS is specified, this tag +# will be ignored. +# +# Note that the filter must not add or remove lines; it is applied before the +# code is scanned, but not when the output code is generated. If lines are added +# or removed, the anchors will not be placed correctly. +# +# Note that for custom extensions or not directly supported extensions you also +# need to set EXTENSION_MAPPING for the extension otherwise the files are not +# properly processed by doxygen. + +INPUT_FILTER = + +# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern +# basis. Doxygen will compare the file name with each pattern and apply the +# filter if there is a match. The filters are a list of the form: pattern=filter +# (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how +# filters are used. If the FILTER_PATTERNS tag is empty or if none of the +# patterns match the file name, INPUT_FILTER is applied. +# +# Note that for custom extensions or not directly supported extensions you also +# need to set EXTENSION_MAPPING for the extension otherwise the files are not +# properly processed by doxygen. + +FILTER_PATTERNS = + +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using +# INPUT_FILTER) will also be used to filter the input files that are used for +# producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES). +# The default value is: NO. + +FILTER_SOURCE_FILES = NO + +# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file +# pattern. A pattern will override the setting for FILTER_PATTERN (if any) and +# it is also possible to disable source filtering for a specific pattern using +# *.ext= (so without naming a filter). +# This tag requires that the tag FILTER_SOURCE_FILES is set to YES. + +FILTER_SOURCE_PATTERNS = + +# If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that +# is part of the input, its contents will be placed on the main page +# (index.html). This can be useful if you have a project on for instance GitHub +# and want to reuse the introduction page also for the doxygen output. + +USE_MDFILE_AS_MAINPAGE = + +#--------------------------------------------------------------------------- +# Configuration options related to source browsing +#--------------------------------------------------------------------------- + +# If the SOURCE_BROWSER tag is set to YES then a list of source files will be +# generated. Documented entities will be cross-referenced with these sources. +# +# Note: To get rid of all source code in the generated output, make sure that +# also VERBATIM_HEADERS is set to NO. +# The default value is: NO. + +SOURCE_BROWSER = NO + +# Setting the INLINE_SOURCES tag to YES will include the body of functions, +# classes and enums directly into the documentation. +# The default value is: NO. + +INLINE_SOURCES = NO + +# Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any +# special comment blocks from generated source code fragments. Normal C, C++ and +# Fortran comments will always remain visible. +# The default value is: YES. + +STRIP_CODE_COMMENTS = YES + +# If the REFERENCED_BY_RELATION tag is set to YES then for each documented +# function all documented functions referencing it will be listed. +# The default value is: NO. + +REFERENCED_BY_RELATION = NO + +# If the REFERENCES_RELATION tag is set to YES then for each documented function +# all documented entities called/used by that function will be listed. +# The default value is: NO. + +REFERENCES_RELATION = NO + +# If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set +# to YES then the hyperlinks from functions in REFERENCES_RELATION and +# REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will +# link to the documentation. +# The default value is: YES. + +REFERENCES_LINK_SOURCE = YES + +# If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the +# source code will show a tooltip with additional information such as prototype, +# brief description and links to the definition and documentation. Since this +# will make the HTML file larger and loading of large files a bit slower, you +# can opt to disable this feature. +# The default value is: YES. +# This tag requires that the tag SOURCE_BROWSER is set to YES. + +SOURCE_TOOLTIPS = YES + +# If the USE_HTAGS tag is set to YES then the references to source code will +# point to the HTML generated by the htags(1) tool instead of doxygen built-in +# source browser. The htags tool is part of GNU's global source tagging system +# (see http://www.gnu.org/software/global/global.html). You will need version +# 4.8.6 or higher. +# +# To use it do the following: +# - Install the latest version of global +# - Enable SOURCE_BROWSER and USE_HTAGS in the config file +# - Make sure the INPUT points to the root of the source tree +# - Run doxygen as normal +# +# Doxygen will invoke htags (and that will in turn invoke gtags), so these +# tools must be available from the command line (i.e. in the search path). +# +# The result: instead of the source browser generated by doxygen, the links to +# source code will now point to the output of htags. +# The default value is: NO. +# This tag requires that the tag SOURCE_BROWSER is set to YES. + +USE_HTAGS = NO + +# If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a +# verbatim copy of the header file for each class for which an include is +# specified. Set to NO to disable this. +# See also: Section \class. +# The default value is: YES. + +VERBATIM_HEADERS = YES + +# If the CLANG_ASSISTED_PARSING tag is set to YES then doxygen will use the +# clang parser (see: http://clang.llvm.org/) for more accurate parsing at the +# cost of reduced performance. This can be particularly helpful with template +# rich C++ code for which doxygen's built-in parser lacks the necessary type +# information. +# Note: The availability of this option depends on whether or not doxygen was +# generated with the -Duse-libclang=ON option for CMake. +# The default value is: NO. + +CLANG_ASSISTED_PARSING = NO + +# If clang assisted parsing is enabled you can provide the compiler with command +# line options that you would normally use when invoking the compiler. Note that +# the include paths will already be set by doxygen for the files and directories +# specified with INPUT and INCLUDE_PATH. +# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES. + +CLANG_OPTIONS = + +#--------------------------------------------------------------------------- +# Configuration options related to the alphabetical class index +#--------------------------------------------------------------------------- + +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all +# compounds will be generated. Enable this if the project contains a lot of +# classes, structs, unions or interfaces. +# The default value is: YES. + +ALPHABETICAL_INDEX = YES + +# The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in +# which the alphabetical index list will be split. +# Minimum value: 1, maximum value: 20, default value: 5. +# This tag requires that the tag ALPHABETICAL_INDEX is set to YES. + +COLS_IN_ALPHA_INDEX = 5 + +# In case all classes in a project start with a common prefix, all classes will +# be put under the same header in the alphabetical index. The IGNORE_PREFIX tag +# can be used to specify a prefix (or a list of prefixes) that should be ignored +# while generating the index headers. +# This tag requires that the tag ALPHABETICAL_INDEX is set to YES. + +IGNORE_PREFIX = + +#--------------------------------------------------------------------------- +# Configuration options related to the HTML output +#--------------------------------------------------------------------------- + +# If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output +# The default value is: YES. + +GENERATE_HTML = YES + +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a +# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of +# it. +# The default directory is: html. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_OUTPUT = html + +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for each +# generated HTML page (for example: .htm, .php, .asp). +# The default value is: .html. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_FILE_EXTENSION = .html + +# The HTML_HEADER tag can be used to specify a user-defined HTML header file for +# each generated HTML page. If the tag is left blank doxygen will generate a +# standard header. +# +# To get valid HTML the header file that includes any scripts and style sheets +# that doxygen needs, which is dependent on the configuration options used (e.g. +# the setting GENERATE_TREEVIEW). It is highly recommended to start with a +# default header using +# doxygen -w html new_header.html new_footer.html new_stylesheet.css +# YourConfigFile +# and then modify the file new_header.html. See also section "Doxygen usage" +# for information on how to generate the default header that doxygen normally +# uses. +# Note: The header is subject to change so you typically have to regenerate the +# default header when upgrading to a newer version of doxygen. For a description +# of the possible markers and block names see the documentation. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_HEADER = + +# The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each +# generated HTML page. If the tag is left blank doxygen will generate a standard +# footer. See HTML_HEADER for more information on how to generate a default +# footer and what special commands can be used inside the footer. See also +# section "Doxygen usage" for information on how to generate the default footer +# that doxygen normally uses. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_FOOTER = + +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading style +# sheet that is used by each HTML page. It can be used to fine-tune the look of +# the HTML output. If left blank doxygen will generate a default style sheet. +# See also section "Doxygen usage" for information on how to generate the style +# sheet that doxygen normally uses. +# Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as +# it is more robust and this tag (HTML_STYLESHEET) will in the future become +# obsolete. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_STYLESHEET = + +# The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined +# cascading style sheets that are included after the standard style sheets +# created by doxygen. Using this option one can overrule certain style aspects. +# This is preferred over using HTML_STYLESHEET since it does not replace the +# standard style sheet and is therefore more robust against future updates. +# Doxygen will copy the style sheet files to the output directory. +# Note: The order of the extra style sheet files is of importance (e.g. the last +# style sheet in the list overrules the setting of the previous ones in the +# list). For an example see the documentation. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_EXTRA_STYLESHEET = + +# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or +# other source files which should be copied to the HTML output directory. Note +# that these files will be copied to the base HTML output directory. Use the +# $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these +# files. In the HTML_STYLESHEET file, use the file name only. Also note that the +# files will be copied as-is; there are no commands or markers available. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_EXTRA_FILES = + +# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen +# will adjust the colors in the style sheet and background images according to +# this color. Hue is specified as an angle on a colorwheel, see +# http://en.wikipedia.org/wiki/Hue for more information. For instance the value +# 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300 +# purple, and 360 is red again. +# Minimum value: 0, maximum value: 359, default value: 220. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_COLORSTYLE_HUE = 220 + +# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors +# in the HTML output. For a value of 0 the output will use grayscales only. A +# value of 255 will produce the most vivid colors. +# Minimum value: 0, maximum value: 255, default value: 100. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_COLORSTYLE_SAT = 100 + +# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the +# luminance component of the colors in the HTML output. Values below 100 +# gradually make the output lighter, whereas values above 100 make the output +# darker. The value divided by 100 is the actual gamma applied, so 80 represents +# a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not +# change the gamma. +# Minimum value: 40, maximum value: 240, default value: 80. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_COLORSTYLE_GAMMA = 80 + +# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML +# page will contain the date and time when the page was generated. Setting this +# to YES can help to show when doxygen was last run and thus if the +# documentation is up to date. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_TIMESTAMP = NO + +# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML +# documentation will contain sections that can be hidden and shown after the +# page has loaded. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_DYNAMIC_SECTIONS = NO + +# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries +# shown in the various tree structured indices initially; the user can expand +# and collapse entries dynamically later on. Doxygen will expand the tree to +# such a level that at most the specified number of entries are visible (unless +# a fully collapsed tree already exceeds this amount). So setting the number of +# entries 1 will produce a full collapsed tree by default. 0 is a special value +# representing an infinite number of entries and will result in a full expanded +# tree by default. +# Minimum value: 0, maximum value: 9999, default value: 100. +# This tag requires that the tag GENERATE_HTML is set to YES. + +HTML_INDEX_NUM_ENTRIES = 100 + +# If the GENERATE_DOCSET tag is set to YES, additional index files will be +# generated that can be used as input for Apple's Xcode 3 integrated development +# environment (see: http://developer.apple.com/tools/xcode/), introduced with +# OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a +# Makefile in the HTML output directory. Running make will produce the docset in +# that directory and running make install will install the docset in +# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at +# startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html +# for more information. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. + +GENERATE_DOCSET = NO + +# This tag determines the name of the docset feed. A documentation feed provides +# an umbrella under which multiple documentation sets from a single provider +# (such as a company or product suite) can be grouped. +# The default value is: Doxygen generated docs. +# This tag requires that the tag GENERATE_DOCSET is set to YES. + +DOCSET_FEEDNAME = "Doxygen generated docs" + +# This tag specifies a string that should uniquely identify the documentation +# set bundle. This should be a reverse domain-name style string, e.g. +# com.mycompany.MyDocSet. Doxygen will append .docset to the name. +# The default value is: org.doxygen.Project. +# This tag requires that the tag GENERATE_DOCSET is set to YES. + +DOCSET_BUNDLE_ID = org.doxygen.Project + +# The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify +# the documentation publisher. This should be a reverse domain-name style +# string, e.g. com.mycompany.MyDocSet.documentation. +# The default value is: org.doxygen.Publisher. +# This tag requires that the tag GENERATE_DOCSET is set to YES. + +DOCSET_PUBLISHER_ID = org.doxygen.Publisher + +# The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher. +# The default value is: Publisher. +# This tag requires that the tag GENERATE_DOCSET is set to YES. + +DOCSET_PUBLISHER_NAME = Publisher + +# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three +# additional HTML index files: index.hhp, index.hhc, and index.hhk. The +# index.hhp is a project file that can be read by Microsoft's HTML Help Workshop +# (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on +# Windows. +# +# The HTML Help Workshop contains a compiler that can convert all HTML output +# generated by doxygen into a single compiled HTML file (.chm). Compiled HTML +# files are now used as the Windows 98 help format, and will replace the old +# Windows help format (.hlp) on all Windows platforms in the future. Compressed +# HTML files also contain an index, a table of contents, and you can search for +# words in the documentation. The HTML workshop also contains a viewer for +# compressed HTML files. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. + +GENERATE_HTMLHELP = NO + +# The CHM_FILE tag can be used to specify the file name of the resulting .chm +# file. You can add a path in front of the file if the result should not be +# written to the html output directory. +# This tag requires that the tag GENERATE_HTMLHELP is set to YES. + +CHM_FILE = + +# The HHC_LOCATION tag can be used to specify the location (absolute path +# including file name) of the HTML help compiler (hhc.exe). If non-empty, +# doxygen will try to run the HTML help compiler on the generated index.hhp. +# The file has to be specified with full path. +# This tag requires that the tag GENERATE_HTMLHELP is set to YES. + +HHC_LOCATION = + +# The GENERATE_CHI flag controls if a separate .chi index file is generated +# (YES) or that it should be included in the master .chm file (NO). +# The default value is: NO. +# This tag requires that the tag GENERATE_HTMLHELP is set to YES. + +GENERATE_CHI = NO + +# The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc) +# and project file content. +# This tag requires that the tag GENERATE_HTMLHELP is set to YES. + +CHM_INDEX_ENCODING = + +# The BINARY_TOC flag controls whether a binary table of contents is generated +# (YES) or a normal table of contents (NO) in the .chm file. Furthermore it +# enables the Previous and Next buttons. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTMLHELP is set to YES. + +BINARY_TOC = NO + +# The TOC_EXPAND flag can be set to YES to add extra items for group members to +# the table of contents of the HTML help documentation and to the tree view. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTMLHELP is set to YES. + +TOC_EXPAND = NO + +# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and +# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that +# can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help +# (.qch) of the generated HTML documentation. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. + +GENERATE_QHP = NO + +# If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify +# the file name of the resulting .qch file. The path specified is relative to +# the HTML output folder. +# This tag requires that the tag GENERATE_QHP is set to YES. + +QCH_FILE = + +# The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help +# Project output. For more information please see Qt Help Project / Namespace +# (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace). +# The default value is: org.doxygen.Project. +# This tag requires that the tag GENERATE_QHP is set to YES. + +QHP_NAMESPACE = org.doxygen.Project + +# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt +# Help Project output. For more information please see Qt Help Project / Virtual +# Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual- +# folders). +# The default value is: doc. +# This tag requires that the tag GENERATE_QHP is set to YES. + +QHP_VIRTUAL_FOLDER = doc + +# If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom +# filter to add. For more information please see Qt Help Project / Custom +# Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- +# filters). +# This tag requires that the tag GENERATE_QHP is set to YES. + +QHP_CUST_FILTER_NAME = + +# The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the +# custom filter to add. For more information please see Qt Help Project / Custom +# Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- +# filters). +# This tag requires that the tag GENERATE_QHP is set to YES. + +QHP_CUST_FILTER_ATTRS = + +# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this +# project's filter section matches. Qt Help Project / Filter Attributes (see: +# http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes). +# This tag requires that the tag GENERATE_QHP is set to YES. + +QHP_SECT_FILTER_ATTRS = + +# The QHG_LOCATION tag can be used to specify the location of Qt's +# qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the +# generated .qhp file. +# This tag requires that the tag GENERATE_QHP is set to YES. + +QHG_LOCATION = + +# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be +# generated, together with the HTML files, they form an Eclipse help plugin. To +# install this plugin and make it available under the help contents menu in +# Eclipse, the contents of the directory containing the HTML and XML files needs +# to be copied into the plugins directory of eclipse. The name of the directory +# within the plugins directory should be the same as the ECLIPSE_DOC_ID value. +# After copying Eclipse needs to be restarted before the help appears. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. + +GENERATE_ECLIPSEHELP = NO + +# A unique identifier for the Eclipse help plugin. When installing the plugin +# the directory name containing the HTML and XML files should also have this +# name. Each documentation set should have its own identifier. +# The default value is: org.doxygen.Project. +# This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES. + +ECLIPSE_DOC_ID = org.doxygen.Project + +# If you want full control over the layout of the generated HTML pages it might +# be necessary to disable the index and replace it with your own. The +# DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top +# of each HTML page. A value of NO enables the index and the value YES disables +# it. Since the tabs in the index contain the same information as the navigation +# tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. + +DISABLE_INDEX = NO + +# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index +# structure should be generated to display hierarchical information. If the tag +# value is set to YES, a side panel will be generated containing a tree-like +# index structure (just like the one that is generated for HTML Help). For this +# to work a browser that supports JavaScript, DHTML, CSS and frames is required +# (i.e. any modern browser). Windows users are probably better off using the +# HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can +# further fine-tune the look of the index. As an example, the default style +# sheet generated by doxygen has an example that shows how to put an image at +# the root of the tree instead of the PROJECT_NAME. Since the tree basically has +# the same information as the tab index, you could consider setting +# DISABLE_INDEX to YES when enabling this option. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. + +GENERATE_TREEVIEW = NO + +# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that +# doxygen will group on one line in the generated HTML documentation. +# +# Note that a value of 0 will completely suppress the enum values from appearing +# in the overview section. +# Minimum value: 0, maximum value: 20, default value: 4. +# This tag requires that the tag GENERATE_HTML is set to YES. + +ENUM_VALUES_PER_LINE = 4 + +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used +# to set the initial width (in pixels) of the frame in which the tree is shown. +# Minimum value: 0, maximum value: 1500, default value: 250. +# This tag requires that the tag GENERATE_HTML is set to YES. + +TREEVIEW_WIDTH = 250 + +# If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to +# external symbols imported via tag files in a separate window. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. + +EXT_LINKS_IN_WINDOW = NO + +# Use this tag to change the font size of LaTeX formulas included as images in +# the HTML documentation. When you change the font size after a successful +# doxygen run you need to manually remove any form_*.png images from the HTML +# output directory to force them to be regenerated. +# Minimum value: 8, maximum value: 50, default value: 10. +# This tag requires that the tag GENERATE_HTML is set to YES. + +FORMULA_FONTSIZE = 10 + +# Use the FORMULA_TRANPARENT tag to determine whether or not the images +# generated for formulas are transparent PNGs. Transparent PNGs are not +# supported properly for IE 6.0, but are supported on all modern browsers. +# +# Note that when changing this option you need to delete any form_*.png files in +# the HTML output directory before the changes have effect. +# The default value is: YES. +# This tag requires that the tag GENERATE_HTML is set to YES. + +FORMULA_TRANSPARENT = YES + +# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see +# http://www.mathjax.org) which uses client side Javascript for the rendering +# instead of using pre-rendered bitmaps. Use this if you do not have LaTeX +# installed or if you want to formulas look prettier in the HTML output. When +# enabled you may also need to install MathJax separately and configure the path +# to it using the MATHJAX_RELPATH option. +# The default value is: NO. +# This tag requires that the tag GENERATE_HTML is set to YES. + +USE_MATHJAX = YES + +# When MathJax is enabled you can set the default output format to be used for +# the MathJax output. See the MathJax site (see: +# http://docs.mathjax.org/en/latest/output.html) for more details. +# Possible values are: HTML-CSS (which is slower, but has the best +# compatibility), NativeMML (i.e. MathML) and SVG. +# The default value is: HTML-CSS. +# This tag requires that the tag USE_MATHJAX is set to YES. + +MATHJAX_FORMAT = HTML-CSS + +# When MathJax is enabled you need to specify the location relative to the HTML +# output directory using the MATHJAX_RELPATH option. The destination directory +# should contain the MathJax.js script. For instance, if the mathjax directory +# is located at the same level as the HTML output directory, then +# MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax +# Content Delivery Network so you can quickly see the result without installing +# MathJax. However, it is strongly recommended to install a local copy of +# MathJax from http://www.mathjax.org before deployment. +# The default value is: http://cdn.mathjax.org/mathjax/latest. +# This tag requires that the tag USE_MATHJAX is set to YES. + +MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest + +# The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax +# extension names that should be enabled during MathJax rendering. For example +# MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols +# This tag requires that the tag USE_MATHJAX is set to YES. + +MATHJAX_EXTENSIONS = + +# The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces +# of code that will be used on startup of the MathJax code. See the MathJax site +# (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an +# example see the documentation. +# This tag requires that the tag USE_MATHJAX is set to YES. + +MATHJAX_CODEFILE = + +# When the SEARCHENGINE tag is enabled doxygen will generate a search box for +# the HTML output. The underlying search engine uses javascript and DHTML and +# should work on any modern browser. Note that when using HTML help +# (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET) +# there is already a search function so this one should typically be disabled. +# For large projects the javascript based search engine can be slow, then +# enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to +# search using the keyboard; to jump to the search box use + S +# (what the is depends on the OS and browser, but it is typically +# , /