/GGIR forked from ucl-cls/mcs-acc

Code for R package GGIR
  1. R 99.2%
  2. Other 0.8%
R Other

Clone with HTTPS

Use Git or checkout with SVN using the web URL.

Download ZIP
Find file
Switch branches/tags
Nothing to show
Pull request Compare This branch is 278 commits ahead of ucl-cls:master.
Latest commit cdc6aa3 Jul 27, 2017 @vincentvanhees vincentvanhees committed on GitHub Merge pull request #45 from jhmigueles/master 
About issue #9
Permalink
Failed to load latest commit information.
R Update g.part3.R Jul 27, 2017
data moved subfolders to root of repo Dec 12, 2016
inst versions number and News.RD updated in preparation for new release Jul 12, 2017
man Update g.part3.Rd Jul 27, 2017
src bug fixed in cpp native routine registraction May 8, 2017
tests bug fixed in test_identify_levels Jul 24, 2017
vignettes Vignette clarificaiton on history of Genea accelerometer closes #29 Jul 12, 2017
.Rbuildignore contribution guidelines added and README removed from .Rbuildignore Apr 28, 2017
.gitignore gitignore updated May 7, 2017
.travis.yml codecov added to travis.yml Jul 22, 2017
DESCRIPTION Update DESCRIPTION Jul 24, 2017
LICENSE Change to LGPL licence Mar 11, 2016
NAMESPACE versions number and News.RD updated in preparation for new release Jul 12, 2017
README.md badge link updated to reference master branch Jul 24, 2017

README.md

Build Status codecov

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

Contribution guidelines:

Contributions are welcome.

For developers:

We work with GitHub Flow branching model.

Key steps:

  1. Create your own working branch
  2. Make your changes in that branch
  3. Commit your changes to your working branch as long as you are not finished with your development
  4. Once your work is finished, make a pull request, such that another developer can review your changes before merging them with the master branch

For end-users 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"