[Feature]: Allow sdlog (or scalar multiplier) as estimable #627
Labels
kind: feature
New feature or request
P3
low priority task
status: wishlist
this will be moved to a later milestone
theme: NLL refactor
Negative log likelihood
Milestone
With respect to needing to specify input uncertainty for catches and indices of abundance...
For future milestones may also be good to allow treating the sdlog (or a scalar multiplier) as an estimable parameter rather than an input for aggregate catch and indices. E.g., wham has a scalar parameter (that is fixed at 1 by default) that is multiplied with sdlog for the catch and indices. One benefit of that approach is that any information about relative sampling intensity over years can be used to configure the input sdlog. An analogous approach could be applied to precision parameters for composition data.
Originally posted by @timjmiller in #136 (comment)
The text was updated successfully, but these errors were encountered: