Status

[kyleabeauchamp]

What's the status of this project? It seems like the API solves a major problem in pymc2/3, in which it's generally hard to make a model that supports passing through variables that are observed or unobserved. It seems like something like this ought to be integrated into pymc3 somehow, although it's unclear whether this is a standalone API for syntatic sugar or a feature enhancement for the existing Model API.

[ColCarroll]

I am happy to advocate for it to get merged into the main project (the mind boggles at the right name... pm.decorate?), though I still have never had a reason to use it, other than giving talks. Usually the right answer for me is a function that returns a pm.Model (though you're right: this solves a different problem).

If you have a use case, I can tag you in the main project and we can work on getting it in.

[kyleabeauchamp]

Thanks, it just seems like a nice clean api, but I haven't fully thought it out yet.

…

On Jan 15, 2018 6:18 PM, "Colin" ***@***.***> wrote: I am happy to advocate for it to get merged into the main project (the mind boggles at the right name... pm.decorate?), though I still have never had a reason to use it, other than giving talks. Usually the right answer for me is a function that returns a pm.Model (though you're right: this solves a different problem). If you have a use case, I can tag you in the main project and we can work on getting it in. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABz_q0h47mRxzV06JQykup4w2uEV9_uNks5tLAbmgaJpZM4RfJHW> .