Is your feature request related to a problem? Please describe.
There are currently (at least) 4 different ways of measuring cluster/object properties in PYME, each resulting in different column names and interpretations. Each has some functionality that the other lacks.
These are:
skimage.measure through `recipes.measurement.Measure2D) (2D, image based)DSView.modules.blobMeasure (3D, image based)Analysis.points.objectMeasure (2D, from points)Analysis.points.cluster_morphology (3D, from points - originally specced as 3D equiv of objectMeasure, but diverged significantly)
Describe the solution you'd like
A consistent naming scheme for measurement outputs, and a closer functional alignment. Ideally reducing the number of overlapping implementations.
Is your feature request related to a problem? Please describe.
There are currently (at least) 4 different ways of measuring cluster/object properties in PYME, each resulting in different column names and interpretations. Each has some functionality that the other lacks.
These are:
skimage.measurethrough `recipes.measurement.Measure2D) (2D, image based)DSView.modules.blobMeasure(3D, image based)Analysis.points.objectMeasure(2D, from points)Analysis.points.cluster_morphology(3D, from points - originally specced as 3D equiv of objectMeasure, but diverged significantly)Describe the solution you'd like
A consistent naming scheme for measurement outputs, and a closer functional alignment. Ideally reducing the number of overlapping implementations.