Closed ASeatonSpatial closed 1 year ago
Yes, the new code has tightened the requirements, so that it's not enough to provide a number sequence; "The number of domain integration points, or a full mesh specification, must be provided"
At the moment, that just means you can wrap the sequence in a call to inla.mesh.1d
;
distance_domain = inla.mesh.1d(seq(.Machine$double.eps, W, length.out = 30))
The reason is that in some cases it's impossible to distinguish between a "number of integration points" and "a domain that only has one point" (although I think there is a bug in inla.mesh.1d that might prevent it from creating such a mesh at the moment).
Ah okay I was assuming it was coordinates but it was the distance domain. The model fitted with distance_domain = inla.mesh.1d(seq(.Machine$double.eps, W, length.out = 30))
, might be wroth expanding on the documentation for the domain
argument in the lgcp
docs
I think I can make the error message include the name of the problem domain to make it easier. The integration code is still in some flux.
The relevant code has drastically changed, and the whole integration code is being rewritten, so this particular issue is no longer relevant.
I ran into a problem trying to refit a distance sampling model using the newest version of inlabru. I've created a reprex using the gorillas data.
When I call
lgcp
I get the following error:Reprex:
I actually have an old Rmd file with this something very similar to this code that used to work. The main difference is that now I must say
domain = list(coordinates = mesh,...)
explicitly, in the old version of inlabru I only needed to specify thedistance
domain and thecoordinates
domain was assumed. It seems like this is causing a problem,ipoints
doesn't seem to think I have supplied the mesh.Traceback is