Closed linzhp closed 10 years ago
I don't think it's a feature or a bug.
When running bootstrap_p
we have generated new data. Of course, m$xmin
will give you a clue what the value xmin
will be, but we still need to estimate it.
The user could use the value of m$xmin
to set reasonable bounds on the xmin
parameter scan, i.e.
xmins = m$xmin + (-50:50)
bootstrap_p(m, xmin = xmins)
It seems that
bootstrap_p
ignoresm$xmin
and estimates xmin on its own. Is this a bug or feature?