This outlines how to propose a change to torch. For more detailed info about contributing to this, and other tidyverse packages, please see the development contributing guide.
You can fix typos, spelling mistakes, or grammatical errors in the documentation directly using the GitHub web interface, as long as the changes are made in the source file. This generally means you’ll need to edit roxygen2 comments in an
.R, not a
.Rd file. You can find the
.R file that generates the
.Rd by reading the comment in the first line.
See also the [Documentation] section.
Feel free to open issues here and add the
feature-request tag. Try searching if there’s already an open issue for your
feature-request, in this case it’s better to comment or upvote it intead 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 be an .R file and a .Rmd file with the same name that just renders the code.
One must be able to run the example without manually downloading any dataset/file. You should also add an entry to the
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.
devtools as the toolchain for development, but a few steps must be done before setiing up.
The first time you clone the repository, you must run:
This will compile Lantern binaries and download LibTorch and copy the binaries to
deps folder in the working directory.
This command must be run everytime you modify lantern code. ie. code that lives in
You can the run
To load torch and test interactively. Or
To run the test suite.