Agenda

Remember: Agenda must be complete (with estimated times) on the day before the meeting. Any additions after that must go at the bottom (AOCB)

1. Accepting minutes from last meeting

2. Matters Arising (<10 mins)

   • Put in action points and PENDING items from last Thursday's meeting.
   • Andrew: Email about OME-TIFF exports in Imaris. [DONE] (Chris)
   • Chris: Email about exporting JPEG [DONE]
   • JMB: Ticket mporters bug issues (+others)
   • Andrew: add significant bits per pixel element to XML

3. Milestone planning

   • OMERO-Beta4.3.2 milestone
   • Tuesday presentation schedule? (August 16th?; OMERO.fs)

4. OME Model Work over the Summer: Andrew's presentation (15 mins)

5. Any other business (<5 mins)

In Attendance

Brian, Ola, Scott, Will, Andrew, Chris, Colin, Simon, Melissa, Curtis, Jason, Carlos

Notes

1. Accepting minutes from last meeting

   • Approved

2. Matters Arising (<10 mins)

   • Andrew: Email about OME-TIFF exports in Imaris. [DONE] (Chris)
     • User is aware that its an Imaris bug.
   • Chris: Email about exporting JPEG - [DONE]
     • User has been emailed, but this still needs testing
   • JMB: Ticket mporters bug issues (+others) - DONE
     • Won't be looked at till JMB returns from vacation
   • Andrew: add significant bits per pixel element to XML - PARTLY DONE
     • Still needs some tweaks to be put in the right place

3. Milestone planning

   • OMERO-Beta4.3.2 milestone

     • 6230 covers proposed Jpeg2000 changes

     • OMERO.web: planned to add running scripts. SPW changes, tree improvements, thumbnail improvements, big file fixes
     • Scott: Is testing built into this schedule?
       • Chris: Andrews model, documentation, bio-formats should. Permissions shouldn't doesn't need testing.
     • Model changes in 4.3.2?
       • Andrew: bits per pixel? Chris: Just having it in model is not that useful, needs client/server exposure
       • Chris: Don't see a point to add this without full implimentation
       • Jason: What we should really be doing here is allowing the spec for the specific camera to be set
         • This is very camera specific
         • Has to be determined by analysing the data
         • Chris: Just adding bitperpixel from bio-formats so its an api call then this gets much easier
           • Jason: This is an attribute of the camera and should go under detectors
           • Chris: Does mean a new schema release. Should be a minor optional non-breaking attribute
           • Does mean new database upgrade though
   • Tuesday presentation schedule? (August 16th?; OMERO.fs)
     • Only meeting where we have enough people around for this meeting
     • Have some synconization meetings planned to update missing folks
     • See ticket #909 for full story

4. OME Model Work over the Summer: Andrew's presentation (15 mins)

   • Whats happened with OME model before September
     • Valication/Tests
       • Curtis: Bio-formats validator crashing as well, maybe larger issue
       • Will put a notice up temporarily while this is being fixed
       • Jason: Do we want to just tell people to use bio-formats?
         • Andrew: That's one way to go
     • Exmample Files
     • Documentation
       • close ome-xml.org
       • create ome data model resource
       • curtis: concerned about removing ome-xml.org. Might be better to keep it.
         • Andrew: a lot of out dated information on that site
         • Jason: We need a single resource for this information
           • Need definitive defition of the schema
           • Need definitive validator
     • Model Additions
       • Need way for folks to write data
       • Now thinking of extensions at the top level for new data types (HIC, EM, SPIM, etc)
       • Build would have extensions added by command line during build process
       • n-dim stored as Z+modulus
         • Needs test implimentation
         • DImension order needs to be addressed or there will be issues with this method
         • Proposed extensions need more thought
         • Curtis: May also want to consider breaking out a non-microscopy centric core from the schema as well
         • Jason: No matter what, some stop gap is probably acceptable while we solidify our plan
         • Jason: For now we put together an EM 'structured annotation' + custom client

5. Any other business (<5 mins)

   • New paper should go out today/tomorrow.

Action Items

* Jason: Write to mark about bits-per-pixel proposed changes