README.Rmd

---
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 = "man/figures/README-",
  out.width = "100%"
)
```

# maceR

<!-- badges: start -->
[![Lifecycle: experimental](https://img.shields.io/badge/lifecycle-experimental-orange.svg)](https://lifecycle.r-lib.org/articles/stages.html#experimental)
[![R-CMD-check](https://github.com/cabaJr/MACE_golem/workflows/R-CMD-check/badge.svg)](https://github.com/cabaJr/MACE_golem/actions)
[![Travis build status](https://travis-ci.com/cabaJr/MACE_golem.svg?branch=master)](https://travis-ci.com/cabaJr/MACE_golem)
[![AppVeyor build status](https://ci.appveyor.com/api/projects/status/github/cabaJr/MACE_golem?branch=master&svg=true)](https://ci.appveyor.com/project/cabaJr/MACE_golem)
[![CircleCI build status](https://circleci.com/gh/cabaJr/MACE_golem.svg?style=svg)](https://circleci.com/gh/cabaJr/MACE_golem)
<!-- badges: end -->

The goal of MACE is to ...

## Installation

You can install the released version of maceR from [CRAN](https://CRAN.R-project.org) with:

``` r
install.packages("maceR")
```

## Example

This is a basic example which shows you how to solve a common problem:

```{r example}
library(maceR)
## 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 could also use GitHub Actions to re-render `README.Rmd` every time you push. An example workflow can be found here: <https://github.com/r-lib/actions/tree/master/examples>.

You can also embed plots, for example:

```{r pressure, echo = FALSE}
plot(pressure)
```

In that case, don't forget to commit and push the resulting figure files, so they display on GitHub and CRAN.