Join GitHub today
Switching to a population level object #2
This looks pretty good!
The Travis CI run failed, and that is partly my fault as the setup is fairly rigid. The package now needs RcppArmadillo, and we have to add this.
That is as easy as:
1 file changed, 1 insertion(+), 1 deletion(-) .travis.yml | 2 +- modified .travis.yml @@ -13,7 +13,7 @@ before_install: - ./run.sh bootstrap install: - - ./run.sh install_aptget r-cran-rcpp + - ./run.sh install_aptget r-cran-rcpp r-cran-rcpparmaillo script: - ./run.sh run_tests
Can you please try this?
I think with that we're good. Let's wait for @adamjohansen to take a peek at it, but I think we got this one covered now. Yay!
(As for going forward: go to the travis-ci.org website and assign your rcppsmc (and/or other repos you want tested. You need to turn this one at a time for new repos. Forks usually work as is, but because you were not set up before it did not automagically work. This is hugely worth it so I recommend you look into it.)
You could revert these commits. Not yet saying you should, just saying you could.
If you want commits to be somewhere else, create a branch first. What happened here is perfectly logical and a feature -- one wants to be able to add to / augment a pull request.
@LeahPrice One thing you want to look into is defining your username and email:
"Unknown" is not the type of credit you want in the long run.