1553-combined-object-filter

[k034b363]

Describe your changes Taking the logic of existing filter on eccentricity, this function expands to allow filtering on any numeric (float or int) object property calculated by skimage.measure.regionprops. The default threshold is 0 and cut_side="upper", which will filter nothing for most (but not all) properties. Users can also specify keeping objects below the given threshold by setting cut_side to "lower".

Type of update Is this a:

• New feature or feature enhancement

Associated issues This closes #1553

Additional context Add any other context about the problem here.

For the reviewer See this page for instructions on how to review the pull request.

• [x] PR functionality reviewed in a Jupyter Notebook
• [x] All tests pass
• [x] Test coverage remains 100%
• [x] Documentation tested
• [x] New documentation pages added to plantcv/mkdocs.yml
• [x] Changes to function input/output signatures added to updating.md
• [x] Code reviewed
• [x] PR approved

[deepsource-io[bot]]

Here's the code health analysis summary for commits 1672a95..49753e0. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Test coverage	✅ Success		View Check ↗

Code Coverage Report

Metric	Aggregate	Python
Branch Coverage	100%	100%
Composite Coverage	100%	100%
Line Coverage	100%	100%
New Branch Coverage	100%	100%
New Composite Coverage	100%	100%
New Line Coverage	100%, ✅ Above Threshold	100%, ✅ Above Threshold

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[k034b363]

Sample image and notebook for testing in data_science drive in jupyter/filter_objs

[nfahlgren]

@k034b363 is the updated function name okay? I figure since it is in the filters submodule we can exclude filter in the function name. So now it would "read" pcv.filters.obj_props

[k034b363]

@k034b363 is the updated function name okay? I figure since it is in the filters submodule we can exclude filter in the function name. So now it would "read" pcv.filters.obj_props

Yep, that makes sense! I didn't choose the name with any reasoning or logic, I like the change better