Closed barrettk closed 5 months ago
Thanks for filing this @barrettk
@kyleam do you see any issue with making this change? I discussed offline with @barrettk and I think it's worth it, given the likely use case (of wanting to join these two df's together). And, given that initial_estimates()
is so new, I don't have too much worry about this being a breaking change. That said, it is technically a breaking change. Any thoughts or input is welcome.
@kyleam do you see any issue with making this change?
No, I agree with your assessment.
As you can see below,
THETA
names as presented viaparam_estimates()
useTHETAX
as the identifier, whereas they are presented asTHETA(X)
viainitial_estimates()
:These should be the same so that users can more easily join these two tables together. Given how much longer
param_estimates()
has been an available function (and how records are specified in theyaml
spec files viapmparams
), it makes sense to changeinitial_estimates()
to match the names inparam_estimates()
.