Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
05/23/13 18:22:57 (11 years ago)
- Author:
-
spli
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
-
Property
Summary
changed from
OMERO.searcher features are stored in two places
to
OMERO.searcher features are stored in two places (server 500 error if not stored correctly)
-
|
initial
|
v1
|
|
| 3 | 3 | * The ContentDB |
| 4 | 4 | |
| 5 | | The ContentDB is used for most operations, however the per-image HDF5 tables are used to check the available feature scales for candidate images. It would be better to store everything in one place (and also avoids the situation where features have been stored in a table but the ContentDB update operation fails). |
| | 5 | The ContentDB is used for most operations, however the per-image HDF5 tables are used to check the available feature scales for candidate images. It would be better to store everything in one place. |
| | 6 | |
| | 7 | This would avoid the situation where features have been stored in a table but the ContentDB update operation fails- in this situation if you attempt to run a search you will end up with a 500 error. |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.11326 sec.)
