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
As limits attribute is provided on top of the grid tuple, I would expect that it means that limits takes over precedence over the grid boundaries. so the lower bound should be the max(grid.min, limits[0]) and the upper bound should be min(grid.max, limits[1])
The text was updated successfully, but these errors were encountered:
The code is written as I originally intended (it's not a "bug" in the sense of an accident), but I think you're right that it probably shouldn't be that way (not being a bug doesn't make it not a mistake). I did think the notion of PDF-wide "limits" was problematic so circumvented it in the upcoming refactored version. I'll leave this issue open as a reminder, though I'm going to rename it for the sake of context. Thanks for your patience with this.
aimalz
changed the title
gridded limits incorrect?
Rethink "limits" from the qp.PDF object
May 31, 2018
aimalz
changed the title
Rethink "limits" from the qp.PDF object
Rethink qp.PDF.limits
May 31, 2018
qp/qp/pdf.py
Line 89 in 7a43a8f
As limits attribute is provided on top of the grid tuple, I would expect that it means that limits takes over precedence over the grid boundaries. so the lower bound should be the max(grid.min, limits[0]) and the upper bound should be min(grid.max, limits[1])
The text was updated successfully, but these errors were encountered: