Place sampling subpackage into an mclmc package

[martin-millon]

I am trying to integrate your sampler in my code, but when I pip install the package locally, I need to do
import sampling to access the package.

This seems a bit dangerous if you have another local module called sampling.py. It would maybe be better to do:
import mclmc.sampling to follow package naming convention

[reubenharry]

Thanks for pointing that out! We can change that in the future. Also feel free to change it yourself and submit a PR.

[reubenharry]

(Should be done soon)

[samueldmcdermott]

agree! On this note, I'd also suggest migrating to pyproject.toml rather than setup.py in compliance PEP 518 and 621 (more detail here on allowed specifications). And it might be good to standardize the branch structure as well (eg, main vs dev vs numbered branches for issues).

I'm happy to pitch in if there's a need -- the pyproject.toml part would be easy and non-invasive

[reubenharry]

Sounds good! I added the mclmc/sampling structure (thought haven't exported to pip), but the pyproject.toml is very welcome (currently I'm working on porting the codebase to BlackJax, but feel free to submit a PR).

[samueldmcdermott]

ok -- I should have a chance to get to this by the end of the week. What branch should I fork from?

[reubenharry]

I'd recommend forking from master (I should rename to main too), as that is serving effectively as the dev branch. Once it's done, I can re-export to pip.

[samueldmcdermott]

sorry to ask a potentially silly question, but do you prefer the name mchmc or mclmc for the package? The about and the readme both refer to MCHMC, and the only place mclmc seems to appear is in the directory

[samueldmcdermott]

made a PR #41 feel free to edit within that as you see fit. I assume the relative paths will be addressed in some other branch you're working on; I just did the minimal amount to pass tests currently

[JakobRobnik]

Thanks! Both MCLMC and MCHMC are fine. To be precise, code is now MCLMC, but we probably don't want to rename the repo? I think we can just stick with MCHMC. Jakob

…

On Fri, Nov 17, 2023, 19:45 samueldmcdermott ***@***.***> wrote: made a PR #41 <#41> feel free to edit within that as you see fit. I assume the relative paths will be addressed in some other branch you're working on; I just did the minimal amount to pass tests currently — Reply to this email directly, view it on GitHub <#39 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKIPD4GESMK2XBZBKYPHNWDYE6WDVAVCNFSM6AAAAAA7FOHBPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJWHEYTQMRXGU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[samueldmcdermott]

sounds good -- I pushed code and made a PR already so I'll leave it to you or @reubenharry to make edits in the obvious places as necessary. Thanks!