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
Looking over the recent paper here I noticed that a number of the models they outperform stan on need updated and are not really made for performance testing. I'll list out a few notes on these as I go
@t4c1 should we have a specialized version of normal_id_glm() that works for vector ~ normal_id_glm(vector, real, real , real)?
I doubt this would bring significant speedup over the code in the model. The performance bottleneck is computing the vector related stuff, so the differences in a few scalar operations is negligible.
Looking over the recent paper here I noticed that a number of the models they outperform stan on need updated and are not really made for performance testing. I'll list out a few notes on these as I go
earn_height.stan:
beta
into two realsalpha
andbeta
hmm_example:
kidscore_interaction
normal_id_glm
log10earn_height:
normal_id_glm()
that works forvector ~ normal_id_glm(vector, real, real , real)
?logearn_interaction
normal_id_glm()
logmesquite_logva
mesquite.stan
pretty much all of these can use normal_id_glm
arK
The text was updated successfully, but these errors were encountered: