Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move SFGS, CSG and Elliptical Slice samplers to pymc3-experiments #3353

Closed
twiecki opened this issue Jan 24, 2019 · 22 comments
Closed

Move SFGS, CSG and Elliptical Slice samplers to pymc3-experiments #3353

twiecki opened this issue Jan 24, 2019 · 22 comments

Comments

@twiecki
Copy link
Member

twiecki commented Jan 24, 2019

These three samplers are not well supported and do not appear to really be used. They are mostly experimental and should be in the main software. Thus, they should be moved to https://github.com/pymc-devs/pymc3-experimental alongside any tests and docs (tests and docs do not need to compile/function). If someone picks them up and demonstrates their usefulness they can certainly make their way back, but they have lied dormant for too long.

@Akamoha
Copy link

Akamoha commented Jan 25, 2019

So this would mean removing all the work done in #2544?

@twiecki
Copy link
Member Author

twiecki commented Jan 25, 2019

@Akamoha Yes, alongside the SFGS.

@eigenfoo
Copy link
Member

#3233 and #3357 are both problems to do with the CSG sampler. Is the plan to simply remove CSG altogether? If so, then perhaps we should close those issues.

@junpenglao
Copy link
Member

Could we move to a new repo maybe? (pymc-devs/experiment?) Along with Elliptical Slice Sampling.

@twiecki
Copy link
Member Author

twiecki commented Jan 25, 2019

@junpenglao I like that.

@twiecki
Copy link
Member Author

twiecki commented Jan 25, 2019

I created https://github.com/pymc-devs/pymc3-experimental.

@twiecki twiecki changed the title Remove CSG sampler Move SFGS, CSG and Elliptical Slice samplers to pymc3-experiments Jan 25, 2019
@junpenglao
Copy link
Member

Awesome ;-)

@junpenglao
Copy link
Member

I can finally dump all my codes on Laplace approximation etc there :-|||||

@twiecki
Copy link
Member Author

twiecki commented Jan 25, 2019

@Akamoha Do you want to take this one on?

@harshitbansal05
Copy link

hey, @twiecki can I work on this one?

@twiecki
Copy link
Member Author

twiecki commented Feb 1, 2019 via email

@fonnesbeck
Copy link
Member

fonnesbeck commented Feb 17, 2019

ESS should not be experimental, and is useful for GPs. One of the demo notebooks uses it.

@ferrine
Copy link
Member

ferrine commented Feb 18, 2019

I remember @ColCarroll was working on this https://github.com/ColCarroll/l2hmc_pymc3
Its worth potring as well

@junpenglao
Copy link
Member

junpenglao commented Feb 18, 2019

@fonnesbeck In that case maybe we should have some more example of using ESS - eg how it is used with other Samplers

@ColCarroll
Copy link
Member

@ferrine just added a license so it can be copied/moved with or without my permission (whoever wants to move it has my permission, but prominent acknowledgments to the authors should stay close to the code!) I can also move it... soon.

@vbsinha
Copy link
Contributor

vbsinha commented Mar 2, 2019

Hi @twiecki, Can I work on this issue?
From the previous comments, it is not clear to me if I should move Elliptical Slice as well. Could you please clarify that? I did a quick grep for EllipticalSlice and found that only one notebook uses it in the entire repo. It is nowhere else mentioned apart from its definition and tests.
Moreover, should I simply move the classes SFGS, CSG and Elliptical Slice to pymc3-experimental? I mean that standalone classes in the experimental repo won't make much sense. So do I move all the other python files involved with these samplers to pymc3-experimental repo?

@twiecki
Copy link
Member Author

twiecki commented Mar 2, 2019

@vbsinha Definitely. You can leave Elliptical Slice here.

To the extend that whole files can be moved that's what I'd do. Ideally we can still retain the functionality in that repo, it should just require redirecting imports to pymc3 instead of relative imports.

@vbsinha
Copy link
Contributor

vbsinha commented Mar 3, 2019

@twiecki It seems that these notebooks (this and this) are using SGFS while this one is using CSG. Could you please suggest how should I proceed? Should we move these notebooks to pymc3-experimental repo as well or leave SGFS and CSG intact in this repo?

@twiecki
Copy link
Member Author

twiecki commented Mar 3, 2019

The NBs should be ported too. Basically the idea is that there is no mention of SGFS or CSG in pymc3, but if someone wants to try them, they can install pymc3-experimental.

@junpenglao
Copy link
Member

Would there be a way to index the doc on the website still? Maybe under a tab call Experimental?
Basically, it would show how to install the experimental feature, which NB example of how to use some of them.

@canyon289
Copy link
Member

canyon289 commented Mar 3, 2019

@junpenglao
I think(?) all you need to do is add an "Experimental api" header to the api.rst file and then add the relevant modules below

https://github.com/pymc-devs/pymc3/blob/master/docs/source/api.rst

@twiecki
Copy link
Member Author

twiecki commented Mar 4, 2019

Closed by #3391.

@twiecki twiecki closed this as completed Mar 4, 2019
@twiecki twiecki mentioned this issue Mar 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants