-
Notifications
You must be signed in to change notification settings - Fork 0
tools for working with a variety of neuroimaging atlases
License
bbuchsbaum/neuroatlas
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
--- output: github_document --- <!-- README.md is generated from README.Rmd. Please edit that file --> ```{r, include = FALSE} knitr::opts_chunk$set( collapse = TRUE, comment = "#>", fig.path = file.path("man", "figures", "README-"), out.width = "100%" ) ``` <!-- badges: start --> [](https://www.repostatus.org/#concept) [](https://lifecycle.r-lib.org/articles/stages.html#experimental) [](https://www.gnu.org/licenses/gpl-3.0.html) [](https://github.com/inbo/neuroatlas/releases)  [](https://github.com/inbo/neuroatlas/actions)   [](https://app.codecov.io/gh/inbo/neuroatlas?branch=main)   <!-- badges: end --> # neuroatlas The goal of neuroatlas is to ... ## Installation You can install the development version from [GitHub](https://github.com/) with: ``` r # install.packages("remotes") remotes::install_github("inbo/neuroatlas") ``` ## Example This is a basic example which shows you how to solve a common problem: ```{r example} library(neuroatlas) ## basic example code ``` What is special about using `README.Rmd` instead of just `README.md`? You can include R chunks like so: ```{r cars} summary(cars) ``` You'll still need to render `README.Rmd` regularly, to keep `README.md` up-to-date. `devtools::build_readme()` is handy for this. You can also embed plots, for example: ```{r pressure, echo = FALSE, eval = FALSE} plot(pressure) ``` In that case, don't forget to commit and push the resulting figure files, so they display on GitHub and CRAN.
About
tools for working with a variety of neuroimaging atlases
Topics
Resources
License
Code of conduct
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published