Comment: Add entry for profiling.
|Deletions are marked like this.||Additions are marked like this.|
|Line 13:||Line 13:|
| * [[/CodeReview]]: how to use the Rietveld code review tool with our codebase
* [[/GkiGrid]]: how to run experiments on the GKI grid
| * [[/CodeReview]]: how to use Bitbucket code reviews or the Rietveld code review tool with our codebase
* [[/GkiGrid]]: how to run experiments on the GKI grid in Freiburg
Back to the HomePage.
Information for developers
/AddingSourceFiles: how to add new source files to the planner
/Mercurial: our Mercurial workflow and Mercurial tips and tricks
/CodingConventions: coding conventions for C++ code
/Whitespace: how to indent, where to break lines, where to put spaces etc. in C++ code
/Uncrustify: using the uncrustify source code pretty printer, including integration with Mercurial
/Includes: using include-what-you-use to find missing/redundant includes and forward declarations
/CodeReview: how to use Bitbucket code reviews or the Rietveld code review tool with our codebase
/GkiGrid: how to run experiments on the GKI grid in Freiburg
/BuildBot: buildbot information
/ImplementationDetails: more in-depth descriptions on how some classes are implemented
/CodeBasesToMerge: code from papers we want to merge in the (medium-term) future
/ReviewQueue: Malte's FIFO list of issues to review
/LongTermPlans: long-term wishlist of changes with broader scope
/ProblemTransformations: problem transformations performed by the planner that might trip up users interested in non-classical planning
/CmakeTipsAndTricks: tips and tricks for CMake
/Profiling: on using valgrind and friends
Other bits and pieces
Mailing lists: Core developers, please subscribe to both the public and the internal mailing lists mentioned on the HomePage.
Admin interface to the internal mailing list: https://www.maillist.unibas.ch/mailman/options/downward-dev/
Python code: We follow PEP 8 and support Python 2.7 and Python >= 3.2.