1/31/2022 - submitted to CRAN
write_quadtree_ptr()
- this was causing a memory leak. I did not intend for users to ever use this function (it’s for my own use) so I simply removed it.1/13/2022 - CRAN version
find_lcp()
and lcp_finder()
.extract()
and extent()
from raster
rather than setting the generics in generics.R
- this is to reduce namespace conflicts with raster
.12/3/2021 - development version
new_points
parameter that accepts a matrix of points to be used instead of the cell centroids.use_original_end_points
parameter. This modified the end points after the LCP functionality had already been run. This is inferior to what I have now implemented, so I removed it. This can now be achieved using the new_points
parameter of lcp_finder()
.lcp_finder()
and find_lcp()
reduced the number of arguments used for method selection to one. I changed the name of the parameter no longer used for method selection to be more descriptive.find_lcp()
that accepts a Quadtree
. It allows for LCPs to be found in one step (rather than having to use lcp_finder()
and then find_lcp()
). While it means that the LcpFinder
object can’t be reused, it is more convenient in cases where only a single LCP needs to be calculated.find_lcp(<LcpFinder>)
, added the allow_same_cell_path
, which allows for paths to be found between points that fall in the same cell.11/30/2021 - development version
projection()
11/16/2021 - development version
assignNeighbors()
in QuadtreeWrapper::readQuadtree()
. Also added unit tests to detect this bug.write_quadtree_ptr()
for writing only the Quadtree
pointer to file (write_quadtree()
writes the QuadtreeWrapper
object to file). This is for my own use - the average user will never need to use this.Quadtree::serialize()
(previously, some attributes were not being serialized).NodeWrapper::toString()
and made it available to R - this simply prints a summary of a NodeWrapper
object.extent()
and projection()
generics from raster
. Relying on the extract
generic from raster
had caused the code to break (see news for previous version). I decided to stop importing generics from raster to avoid any future issues like this. This has the disadvantage of masking extent()
and projection()
from raster
. This means users will need to preface the functions with the package names when using both packages, but it’ll hopefully avoid issues caused by changes in raster
.11/9/2021 - development version
extract()
generic from raster
- instead, it is set via setGeneric()
in “R/generics.R”. This is an attempted fix for an error - in some cases the extract()
generic with signature “Quadtree”, “matrix” was not being found.development version
add_legend()
, added parameters for controlling text color, font, and size. Also renamed ticks_x_pct
parameter to text_x_pct
parameter for consistency.border_lwd
parameter of plot(<Quadtree>)
) to .4, since that typically looks nicer.split_method
parameter of quadtree()
is "cv"
)CRAN version
Responded to comments after CRAN submission. This led to the following changes:
plot(<Quadtree>)
, switched to resetting par()
using on.exit()
.par()
if it was changed.development version
#include
in Matrix.cpp
that appeared to be causing the CRAN build to fail.#include
s in C++ files - removed unnecessary #includes
and order them in a way that is more readable.PointUtilities.h
and PointUtilities.cpp
. Only a single function (distBtwPoints()
) in this namespace was being used (in LcpFinder.cpp
), and only once.Point
objects as parameters (rather than having double x
and double y
parameters).Point
.makeNeighborList()
(from QuadtreeWrapper
) - removed ambiguous hasChildren
column and instead added hasChildren0
and hasChildren1
columns. Modified plot_Quadtree.R
to work with the new columns.summary(<Quadtree>)
, summary(<LcpFinder>)
, lines(<LcpFinder>)
, and points(<LcpFinder>)
. Also added a unit test for search_by_centroid
option of lcp_finder()
.