CellProfiler/CellProfiler — Issue #149: JIRA [IMG-1032] Allow measurements of objects to be kept by filtered objects
Author: thouis
Created: 2011-11-23 20:50:23+00:00
State: open
Labels: current

Problem: Objects can get measured by measure modules, then filtered with FilterObjects, but these filtered objects have no measurements associated with them. The user is forced to re-measure these objects
Solutions that I see immediately:
* Leave it alone and force the user to remeasure -- (annoying)
* Automatically copy the measures from unfiltered to filtered object --(wasteful)
* Save only flags assigning filtered objects, keeping the filtered objects somehow related to their parents, then deal with the question of what measurements to save in the Export modules (seems the best, but requires the most coding)

Original reporter: dlogan
Jira link: https://jira.broadinstitute.org/browse/IMG-1032
Fix version: Current
Assignee: leek

**Comment from leek on Thu, 1 Jul 2010 13:39:52 -0400:**
The last (do it at export) is the best solution since measurements made
after filtering on the original measurement will be assigned to the
filtered objects. Probably the best thing would be to add options to the
Export modules to do this - a DB guru would say that the best way to get
the measurements for a filtered object would be through a join using the
Parent_XXX field.
David Logan (JIRA) wrote:
> Allow measurements of objects to be kept by filtered objects
> --------------------------------------------------------------
>
> Key:IMG-1032
> URL:http://jira.broadinstitute.org:8008/browse/IMG-1032
> Project: Imaging
> Issue Type: Improvement
> Components: CellProfiler
> Affects Versions: Current
> Reporter: David Logan
> Assignee: Lee Kamentsky
> Priority: Minor
> Fix For: Next
>
>
> Problem: Objects can get measured by measure modules, then filtered with FilterObjects, but these filtered objects have no measurements associated with them. The user is forced to re-measure these objects
>
> Solutions that I see immediately:
> * Leave it alone and force the user to remeasure -- (annoying)
> * Automatically copy the measures from unfiltered to filtered object --(wasteful)
> * Save only flags assigning filtered objects, keeping the filtered objects somehow related to their parents, then deal with the question of what measurements to save in the Export modules (seems the best, but requires the most coding)
>
>