R C C++
Latest commit c786cbd Feb 22, 2017 @baddstats baddstats Bug fixes in sparse array code.
   kppm.R
	Added canonical parameters case for Palm and composite likelihood.
	Fixed bugs.

   sparsecommon.R
	Bug fix in mapSparseEntries in handling a sparse array with no entries.

   sparse3Dmatrix.R
	Bug fixes in [<-.sparse3Dmatrix when no entries are indexed.

   tests/sparse3Darrays.R
   tests/leverinf.R
	Added cases that may trigger the bugs above: zero cif, etc

   DESCRIPTION
   NEWS
   	updated as version 1.49-0.007

README.md

spatstat

CRAN_Status_Badge Research software impact

This repository holds a copy of the current development version of the contributed R-package spatstat.

This development version is more recent than the official release of spatstat on CRAN. Each official release of spatstat has a version number like 1.2-3 while the development version has a version number like 1.2-3.004. Official releases occur every 8 weeks (the minimum time permitted by CRAN policies) while the development code is updated almost every day.

The development version is also tracked by the software testing services Travis and Codecov, but these badges are currently not working correctly: Travis-CI Build Status codecov.io

Important Note

Recently we have started the process of splitting spatstat into several packages (to satisfy the requirements of CRAN). Currently there are two pieces, called spatstat.utils and spatstat. The current development version of spatstat.utils is here.

Installation

The easiest way to install the development version of spatstat from github is through the devtools package:

require(devtools)
install_github('spatstat/spatstat.utils')
install_github('spatstat/spatstat')

If you don't have devtools installed you should first run

install.packages('devtools')

Bug reports

Users are encouraged to report bugs here. Go to issues in the menu above, and press new issue to start a new bug report, documentation correction or feature request.

Please do not post questions on the Issues page because it's too clunky for correspondence.

Questions about spatstat

For questions about spatstat, first check the question-and-answer website stackoverflow. If your question is not listed, you can either post your question at stackoverflow, or email the authors.

Making your own changes

Feel free to fork spatstat, make changes to the code, and ask us to include them in the package by making a github pull request.

However, this repository is only a copy of the development code, so your pull request may not be implemented until the next official release.