Contributing to torchSource:
Many thanks for wanting to contribute to
torch! We welcome all kinds of contributions, from correcting typos via bug fixes to feature additions.
To fix typos, spelling mistakes, or grammatical errors, you need to make changes in the source
.R file in question, not in the generated
.Rd file. Thereafter, run
tools/document.R to regenerate the documentation. (See Workflow below for why.)
Feel free to open issues here, and add the
feature-request tag. Also try searching if there’s already an open issue for your
feature-request – in this case it’s better to comment or upvote it instead of opening a new one.
We welcome contributed examples. Feel free to open a PR with new examples. The examples should be placed in the
The examples should consist of an
.R file and an
.Rmd with the same name that just renders the code.
It’s important that one can run the example without manually downloading any dataset/file. You should also add an entry to the
_pkgdown.yaml file for your example.
We have many open issues in the github repo. If there’s one item that you want to work on, you can comment on it and ask for directions.
New R code should follow the
tidyversestyle guide. You can use the styler package to apply these styles, or simply run the
tools/style.shscript, which also formats the code and removes whitespace. Please don’t re-style code that has nothing to do with your PR.
New C/C++ code should follow the
clang-formatto apply these styles, or simply run
tools/style.sh, which also formats the code and removes whitespace. Please don’t re-style code that has nothing to do with your PR.
We use testthat for unit tests. Contributions with test cases included are easier to accept.
- R installation
- R Tools for compilation (only on Windows)
- CMake to compile
devtools as the toolchain for development, but a few steps must be done before upfront.
The first time you clone the repository, run:
This will first download LibTorch and copy its binaries to the
deps folder in the working directory, and then, compile the
lantern binaries themselves.
This command must be run everytime you modify
lantern code, i.e., code that lives in
You can then run
torch, and test interactively. Alternatively, run
to execute the test suite.
Finally, it’s important to update the documentation. Please always use the custom
tools/document.R script instead of
devtools::document(), as we need to patch
roxygen2 to avoid running the examples on CRAN.
We’re looking forward to your contributions!