Task #10737 (closed)
Opened 6 years ago
Closed 3 years ago
Choice of scales for calculating features
| Reported by: | spli | Owned by: | icao-berg-x |
|---|---|---|---|
| Priority: | minor | Milestone: | Partner-1 |
| Component: | General | Version: | 4.4.9 |
| Keywords: | searcher | Cc: | analysis@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
What resolutions should features be calculated at (see #10736).
E.g. If one image is 1um/pixel and another is 1.2um/pixel then one of them needs to be rescaled so that the calculated features are comparable. How do we decide what to resize it to?
Some possibilities:
- Resize images to be one of a predefined set of resolutions: What is this set? We could be dealing with anything from nanometers to meters.
- User-definable: More complicated for users, especially non-technical users, also means a fully automated workflow (calculated features and add to database at import) isn't possible.
- System-definable: Sys-admin defines it in a config file.
In addition are features calculated for a single scale, or multiple?
Change History (5)
comment:1 Changed 6 years ago by spli
- Milestone changed from Unscheduled to OMERO-4.4.10
- Version set to 4.4.9
comment:2 Changed 6 years ago by spli
- Owner changed from spli to icao-berg-x
comment:3 Changed 6 years ago by spli
- Keywords searcher added
comment:4 Changed 6 years ago by spli
- Milestone changed from OMERO-4.4.10 to Partner-1
comment:5 Changed 3 years ago by jamoore
- Resolution set to wontfix
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Cleaning up searcher backlog.