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 #5917 (closed)

Opened 13 years ago

Closed 12 years ago

Add support for IMOD (.mod) files

Reported by: mlinkert Owned by: mlinkert
Priority: minor Milestone: OMERO-4.4
Component: Bio-Formats Version: n.a.
Keywords: paris2011, dresden-hackathon-2011 Cc: johannes.schindelin@…, wmoore, jburel, cxallan, jamoore
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: 0.0d
Sprint: 2012-05-08 (14)

Description

See file in data/imod/jean-marc/.

Some documentation is also available at:

http://bio3d.colorado.edu/imod/doc/asciispec.html
http://bio3d.colorado.edu/imod/doc/binspec.html

Change History (19)

comment:1 Changed 13 years ago by mlinkert

  • Keywords paris2011 added

comment:2 Changed 13 years ago by mlinkert

  • Cc johannes.schindelin@… added

comment:3 Changed 12 years ago by mlinkert

  • Keywords dresden-hackathon-2011 added
  • Milestone changed from Unscheduled to OMERO-Beta4.4
  • Sprint set to 2011-12-13 (4)

comment:4 Changed 12 years ago by jburel

  • Sprint changed from 2011-12-13 (4) to 2011-12-27 (5)

Moved from sprint 2011-12-13 (4)

comment:5 Changed 12 years ago by mlinkert

  • Status changed from new to accepted

comment:6 Changed 12 years ago by mlinkert

  • Cc wmoore jburel cxallan jmoore added
  • Sprint changed from 2012-01-03 (5) to 2012-01-17 (6)

The tricky thing about this particular format is that the files don't contain raw pixel data, but rather shape data (a set of points + rendering information). There are a few ways to handle this:

  1. Store all of the shapes as OME Shape elements. This means that Bio-Formats will always return completely black image planes, and it is up to whatever client software to handle drawing the shapes correctly.
  2. Set the pixel data to correspond to whatever points and colors are stored, optionally storing the remaining shape information in Shape elements.
  3. Attempt to render the shapes into an image using all of the shape information. The images returned by Bio-Formats will then more or less match what is displayed in IMOD.

I suspect that (3) is nicest for users, but (1) or (2) is more appropriate from an implementation perspective. I really don't know enough about how this data is used, though. Any opinions?

comment:7 Changed 12 years ago by jmoore

Without knowing how they are used either, I would think 1+3 would be the best solution, i.e. pixel data should be generated but the shapes should be preserved.

comment:8 Changed 12 years ago by cxallan

Taking into account the intent of Bio-Formats, which is not to provide a visualization framework but a data access library I would argue that (3) and possibly even (2) is not its responsibility. Furthermore, even if (3) were attempted I would think the best we could hope for would be a rather trivial implementation, the number of potential features such an API would have to implement is staggering.

I do however think that given (1) a generic library that converted from OME ROI and Shape elements to Java2D instances for the purposes of drawing would be useful to Bio-Formats, OMERO and Bio-Formats ImageJ plugin users. Jean-Marie, does OMERO.insight currently translate the OME ROI and Shape instances to Java 2D instances, some sort of wrapper instances or to JHotDraw instances?

comment:9 Changed 12 years ago by wmoore

I would go for 1. Rendering is going to be meaningless since you'll have open shapes, lines, points etc that don't translate into volumes/voxels.

comment:10 Changed 12 years ago by jburel

  • Sprint changed from 2012-01-17 (6) to 2012-01-31 (7)

Moved from sprint 2012-01-17 (6)

comment:11 Changed 12 years ago by jmoore

  • Sprint changed from 2012-01-31 (7) to 2012-02-14 (8)

Moved from sprint 2012-01-31 (7)

comment:12 Changed 12 years ago by jburel

  • Sprint changed from 2012-02-14 (8) to 2012-02-28 (9)

Moved from sprint 2012-02-14 (8)

comment:13 Changed 12 years ago by mlinkert

  • Remaining Time set to 0.001

comment:14 Changed 12 years ago by jburel

  • Sprint changed from 2012-02-28 (9) to 2012-03-13 (10)

Moved from sprint 2012-02-28 (9)

comment:15 Changed 12 years ago by jburel

  • Sprint changed from 2012-03-13 (10) to 2012-03-27 (11)

Moved from sprint 2012-03-13 (10)

comment:16 Changed 12 years ago by jburel

  • Sprint changed from 2012-03-27 (11) to 2012-04-10 (12)

Moved from sprint 2012-03-27 (11)

comment:17 Changed 12 years ago by jburel

  • Sprint changed from 2012-04-10 (12) to 2012-04-24 (13)

Moved from sprint 2012-04-10 (12)

comment:18 Changed 12 years ago by jburel

  • Sprint changed from 2012-04-24 (13) to 2012-05-08 (14)

Moved from sprint 2012-04-24 (13)

comment:19 Changed 12 years ago by mlinkert

  • Remaining Time changed from 0.001 to 0
  • Resolution set to fixed
  • Status changed from accepted to closed
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.79281 sec.)

We're Hiring!