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

ROI Filtering: Before or After? #17

Open
pv33 opened this issue Feb 1, 2024 · 0 comments
Open

ROI Filtering: Before or After? #17

pv33 opened this issue Feb 1, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@pv33
Copy link
Member

pv33 commented Feb 1, 2024

If the ROI is known and small enough, or exists as a crop region, then shouldn't the ROI part come before the background/foreground estimation to save time? At minimum it avoids unnecessary computations.

This may be required for the current pilot study since the board used is a non-black plate. The processing for the pilot study should be different compared to what is done now due to the different setup.

The current setup may even require some form of updating Gaussian model. It will take some time to work out.

Most likely there needs to be a specification interface that indicates how to process things. Doing so might actually be useful for general robot tasks as it can create the specification, load it, then process. Permits flexible instantiation of computational modules.

@pv33 pv33 added the enhancement New feature or request label Feb 1, 2024
@pv33 pv33 self-assigned this Feb 1, 2024
@pv33 pv33 added this to the Pilot Study Processing milestone Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant