Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clearing memory via "remove objects" prevents measurement export in "output control" #188

Open
fiona-sievers opened this issue Mar 19, 2024 · 2 comments

Comments

@fiona-sievers
Copy link

In order to save memory space while batch processing, our workflows usually had a "clearing memory" step that uses the "remove objects" module. However, I just ran into the issue that objects cannot be removed without loosing the option to export measurements based on them in the "output control" (which makes sense), even if "retain measurements" is ticked. Removing images via the "remove images" works fine. Are objects and related measurements automatically removed between images in a batch and if not, is there a possibility to do that?

This is not an urgent issue, we can do without the memory clearing. Just wondering whether this might be a user error on my part or potential bug?

Thank you so much!

@sjcross
Copy link
Member

sjcross commented Mar 21, 2024

Hi Fiona,

Good spot; I'd not noticed this before! When you select "retain measurements" for an image or object, the measurements should be visible in Output Control as things that can be exported; however, it seems I never actually implemented this functionality. I'll try and get it added in for the next version of MIA.

As it happens, when running in batch mode, the images are objects are cleared at the end of each file's processing anyway. This process happens for all images and objects and runs independently of the "Remove images" and "Remove objects" modules, so should be working correctly already. The only information that's retained until all files have completed are the measurements, so these can be written to Excel file.

Cheers,
Stephen

@fiona-sievers
Copy link
Author

Hi Stephen,

Thank you very much for the quick response and for the info! Seems like the clearing memory step at this point in the pipeline is not necessary anyway then.

Best,
Fiona

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants