Task #10978 (closed)
Opened 11 years ago
Closed 8 years ago
OMERO.searcher doesn't handle multiple ContentDB scales for the same image very well
| 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
omero_searcher.view.contentsearch just takes the first scale for an image scale = pyslid.features.getScales(conn, i, str(ftset), True)[0] regardless of whether that is the best scale for comparing other images. Ideally it should either compare multiple scales, or take the scale which is most popular rather than the first.
Change History (4)
comment:1 Changed 11 years ago by spli
- Milestone changed from Unscheduled to OMERO-4.4.10
- Version set to 4.4.9
comment:2 Changed 11 years ago by spli
- Owner changed from spli to icao-berg-x
comment:3 Changed 10 years ago by spli
- Milestone changed from OMERO-4.4.10 to Partner-1
comment:4 Changed 8 years ago by jamoore
- Resolution set to wontfix
- Status changed from new to closed
Cleaning up searcher backlog.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
If we can't come up with a permanent solution we should at least work out an acceptable compromise before release.