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
The current cf.cellwi(start, end) only matches cells that lie completely with the closed range [start, end].
Sometimes we would like to match cells that merely overlap the range.
I propose a new function cf.cell_overlaps(start, end) that does just this. It will be a constructor function for <CF Query: [upper_bounds(ge start) & lower_bounds(le end)]>
(Compare this with cf.cellwi, which is a constructor function for <CF Query: [lower_bounds(ge start) & upper_bounds(le end)]>)
The docstrings for the various Query constructor functions could also be improved to more accurately reflect what they do!
The text was updated successfully, but these errors were encountered:
Having chatted about this off-line, we're going to park this until v4.0.0, when we can think about the best approach to bringing other "cell" methods into the fold.
The current
cf.cellwi(start, end)
only matches cells that lie completely with the closed range[start, end]
.Sometimes we would like to match cells that merely overlap the range.
I propose a new function
cf.cell_overlaps(start, end)
that does just this. It will be a constructor function for<CF Query: [upper_bounds(ge start) & lower_bounds(le end)]>
(Compare this with
cf.cellwi
, which is a constructor function for<CF Query: [lower_bounds(ge start) & upper_bounds(le end)]>
)The docstrings for the various
Query
constructor functions could also be improved to more accurately reflect what they do!The text was updated successfully, but these errors were encountered: