-
Notifications
You must be signed in to change notification settings - Fork 53
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
Require boxsize if periodic=True #199
Conversation
Hello @lgarrison! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2021-06-09 17:57:16 UTC |
@lgarrison A check will need to be added to the API as well so that boxsize is required even when using the static library interface. Since this is a functional change, should we milestone it for v2.4 instead of v2.3.2? |
Okay, I'll take a look at the static interfaces. I actually think some of them don't even accept a boxsize at all right now! Versioning it as 2.4 is fine with me. |
That's true -- there is no option to pass the On a related note, what do you think about renaming |
* Add boxsize parameter to command line theory interfaces * Default boxsize in the C API is -1 so that users must specify the correct value or 0 for automatic detection * Update test results with correct boxsize
@lgarrison The checks might need to be tweaked a little. Within the |
We could add |
Sounds good - agree with your logic about keeping it simple. We are milestoning this for v2.4 with a (minor) change in calling convention - so the versioning is also fine. |
Oooo I actually did a review! |
Now that 2.3.2 is out, I think this can be merged. |
I think this is just about ready to merge. Want to do one last review? The student who originally asked me about the VPF is going to make a PR for that change, then we can get the ball rolling on the 2.4.0 release. |
Took another look at the code and added one comment about the version. Plus, there is the previous comment about the |
Hmm... I think I'm in favor of saying the Also, I am looking for your new review comment, but I cannot find it! Which line was it at? |
Heh - I don't think I had submitted the review! Oops |
If we are thinking of merging this in, perhaps would be good to have a think on how to accommodate #247 |
Everything look okay with this PR? I think I am not going to tackle #247 right now, but will probably revisit it in a few months. |
Sorry, it's taking me a while - I am currently swamped! I will do the review as soon as I have a second but will likely be next week at the earliest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looked through the entire changes and left some comments on the first counter (DD
?) but those same comments apply to all the other pair-counters too.
The most important comment is about moving the boxsize
parameter earlier in the list of parameters
…tion signature and docstring. A few other doc tweaks.
Thanks for the comments; I agree moving What do you think, ready to merge? |
Thanks for the changes. Yup - ready to merge |
From #198, require the user to specify
boxsize
if usingperiodic=True
. I can't imagine a situation where the user would want automatic detection of the particle extent, because that will nearly always be off by a small amount.If the user still wants that behavior for some reason,
boxsize=0.
will still trigger it. That was the old Python default value.