You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The resulting mismatch caused half of the transects to fall within a region where there were animals and the other half of the transects falling in a region without animals. Because I had not specified plot(size.cov.survey) to visualise this problem, I stupidly ran hundreds of simulations producing poor precision in my estimates because of the crazed encounter rate variance I had induced.
Suggested code change
Perhaps somewhere in make.simulation there could be a check of the region object from make.population.description matches the region object used in the specification of make.design
The text was updated successfully, but these errors were encountered:
Perhaps it could generate a warning if the region object does not match? That way the user could still proceed if they have some good reason for a mis-matched population and design region? (I can't think of a reason offhand, but I'm sure there are some!...)
I created a study region of non-default dimensions:
I used
risso.region
to specify the population descriptionHowever, I failed to specify
risso.region
when callingmake.design
The resulting mismatch caused half of the transects to fall within a region where there were animals and the other half of the transects falling in a region without animals. Because I had not specified
plot(size.cov.survey)
to visualise this problem, I stupidly ran hundreds of simulations producing poor precision in my estimates because of the crazed encounter rate variance I had induced.Suggested code change
Perhaps somewhere in
make.simulation
there could be a check of theregion
object frommake.population.description
matches theregion
object used in the specification ofmake.design
The text was updated successfully, but these errors were encountered: