Skip to content
Branch: master
Clone or download
Latest commit cea3ecc Jul 11, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
R Fix issue 197 Jul 10, 2019
data size of example reduced to lower overall package size Apr 22, 2018
inst prepare new release 1.9-2 Jul 3, 2019
man prepare new release 1.9-2 Jul 3, 2019
src cpp code fixed to compile again Dec 23, 2017
tests skip night analysis if there is only one sustained inactiviy bout, an… May 21, 2019
vignettes updated example function call Jul 3, 2019
.Rbuildignore .ignore files updated May 9, 2019
.gitignore .ignore files updated May 9, 2019
.travis.yml
.zenodo.json package release date corrected Jan 11, 2019
CITATION.cff prepare new release 1.9-2 Jul 3, 2019
DESCRIPTION prepare new release 1.9-2 Jul 3, 2019
LICENSE Change to LGPL licence Mar 11, 2016
NAMESPACE improved available memory assessment because previous method did not … Jan 5, 2019
README.md badges added for download count May 9, 2019
prepareNewRelease.R minor edits to explanation of prepareNewRelease function Feb 20, 2019

README.md

Build Status codecov DOI

The code in this repository is the development version for the code in R-package GGIR on CRAN

Getting started:

The package vignette and this short tutorial video provide an introduction to GGIR, including: How it can be installed, Key software features, and where to get help.

Contribution guidelines:

We always welcome contributions to the package.

When you are familiar with GitHub:

We work with GitHub Flow branching model.

Key steps:

  1. Create a GitHub issue in this repository with description of the work that you plan to do.
  2. Assign yourself to the GitHub issue you are working on, to inform other developers that you are working on it.
  3. Create your own working branch or fork.
  4. Make your changes in that branch or fork.
  5. Commit your changes to your working branch/fork as long as you are not finished with your development.
  6. Make sure the release notes in NEWS.Rd are updated.
  7. Add your name to the contributors list in the DESCRIPTION file.
  8. Run the tests and checks as CRAN, make sure they pass.
  9. Once your work is finished, make a pull request, such that another developer can review your changes before merging them with the master branch.

When you are unfamiliar with GitHub:

If you would like to propose additional functionalities or report an issue. Go to issues and create a new issue.

If you would like to propose changes to the text of the manual this is possible.

  1. Please go to the man folder which holds all the parts of the manual.
  2. Go to the part of the manual you want to edit and click on edit button (little pencil symbol) and make your changes.
  3. Once you are finished, scroll down and describe you update and select the radio button "Create a new branch for this commit and start a pull request". One of the developers will then be able to review your changes and merge them in the master version of the code.
  4. Click the green button "Propose file changes"
You can’t perform that action at this time.