Task #10933 (closed)
Opened 11 years ago
Closed 9 years ago
Reconsider optional feature table columns in PyCHRM
| Reported by: | spli | Owned by: | spli |
|---|---|---|---|
| Priority: | major | Milestone: | Partner-1 |
| Component: | Scripting | Version: | 4.4.9 |
| Keywords: | pychrm | Cc: | analysis@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.0d |
| Sprint: | n.a. |
Description
OmeroPychrm? currently uses a client side wrapper to implement optional columns for storing features: https://github.com/manics/omero-pychrm/blob/d60db5bda34cdc9f27aed441669e7e7499bb12f4/OmeroPychrm/TableConnection.py
This is implemented using DoubleArrayColumn?-BoolColumn? pairs where the Bool indicates whether the DoubleArray? is null or not. The original thinking was that PyCHRM might not always calculate the full set of features for efficiency reasons. Is this still necessary, or should it be removed before the first release and (in future) re-implemented in a better way?
Change History (3)
comment:1 Changed 10 years ago by jburel
comment:2 Changed 10 years ago by spli
- Milestone changed from OMERO-4.4.x to Partner-1
- Version set to 4.4.9
comment:3 Changed 9 years ago by spli
- Remaining Time changed from 1 to 0
- 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.
Referencing ticket #9946 has changed sprint.