-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Labels
To discussRequires discussionRequires discussiontriageNew items to look at and decide what to doNew items to look at and decide what to do
Description
Note check.mono is actually in mrds
Len commented:
- I can't make sense of the plot that come from calling
check.mono(hn2$ddf, plot = TRUE)in that I expect the pink bar at the top to show where one of the constraints is broken, but it looks pink everywhere. I suspect there is a bug in thechpplyfunction, which is defined withincheck.monobut I have not looked into it. I can raise as a separate issue if that's helpful.
Originally posted by @lenthomas in #186
MRE
The following code uses these duiker data: DaytimeDistances.txt
DuikerCameraTraps <- read.csv(file="DaytimeDistances.txt", header=TRUE, sep="\t")
DuikerCameraTraps$Area <- DuikerCameraTraps$Area / (1000*1000)
DuikerCameraTraps$object <- NA
DuikerCameraTraps$object[!is.na(DuikerCameraTraps$distance)] <- 1:sum(!is.na(DuikerCameraTraps$distance))
library(Distance)
trunc.list <- list(left = 2, right = 15)
mybreaks <- c(seq(2, 8, 1), 10, 12, 15)
conversion <- convert_units("meter", NULL, "square kilometer")
hn2 <- ds(DuikerCameraTraps, transect = "point", key = "hn",
adjustment = "cos",
nadj=2, convert_units = conversion,
monotonicity = "none",
cutpoints = mybreaks, truncation = trunc.list)
plot(hn2)
check.mono(hn2$ddf, n.pts=10, plot = TRUE) # gives TRUE
Metadata
Metadata
Assignees
Labels
To discussRequires discussionRequires discussiontriageNew items to look at and decide what to doNew items to look at and decide what to do
