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.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #5214 (new)

Opened 13 years ago

Last modified 8 years ago

ROI model 3D proposal evolution

Reported by: jburel Owned by:
Priority: minor Milestone: ROI
Component: General Version: 4.4.8
Keywords: schema Cc: jamoore, ajpatterson, cxallan
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description (last modified by ajpatterson)

This ticket will become the work to integrate the changes coming from the scijava work.
Full details of the proposed model can be found at:

http://www.scijava.org/roi-model/


A few semi-random comments I can share:

Wouldn't a few well chosen 3D primitive be useful as well? Like, sphere/ellipsoid, tube (=line with a 3D width)... And I am guessing input/output of VertexArray into standard format for viewing or processing (CGAL for computational geometry comes to mind, openGL stuff as well I guess) would be useful too, although that may be more for scripts/outside clients...

What about shapes intrinsically in 4D or even 5D? It might be a pain to deal with but one can think of cases where it may come in handy (tracking of stuff merging/splitting for example, or maybe sometime having one track=one shape could be useful; for channel: FRET pairs and photo-switchable protein, maybe?).

The other point is hierarchical roi: would it be possible to have nested roi (rois having some kind of RoiRoisSeq field for example)? it would allow for intra-cellular localisation in particular, but most likely other uses.


Change History (5)

comment:1 Changed 13 years ago by jburel

  • Description modified (diff)

comment:2 Changed 13 years ago by jmoore

  • Description modified (diff)

comment:3 Changed 13 years ago by ajpatterson

  • Keywords schema added

comment:4 Changed 11 years ago by ajpatterson

  • Description modified (diff)
  • Version set to 4.4.8

comment:5 Changed 8 years ago by jamoore

  • Milestone changed from Unscheduled to ROI
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.68325 sec.)

We're Hiring!