Personal tools
  • We're Hiring!

You are here: Home Community Minutes Conference Calls 2009 2009-11-19 Thursday Meeting

2009-11-19 Thursday Meeting

Notes

  • Release

    • Releasing before ASCB
      • By the end of next week
      • Several fixes today
      • Big image fix not coming: restricting on image size
        • Client or Server?
        • Happens on compression (thumbnails work)
        • @Jason will generate a 3072^2 image and test
        • @Chris adds note to troubleshooting on upping size
        • @Chris adds note to install page
        • @Chris puts check in RE
        • @Jean-Marie also puts check in insight; speaks to Ola
      • Separate discussion for OMX
    • Open
      • Delete: still open
    • Testing
      • Iain testing againt nightshade
      • Need to check: copy rendering settings, experimenter annotation bug, ...
    • tickets etc.
      • 4.1
        • Carlos looks at https://trac.openmicroscopy.org.uk/omero/ticket/1422
      • 4.x preview
        • Won't be closed out
        • Some tickets willl be worked on (#1652)
      • 4.1.1
        • finishing by end of middle of next week
        • solving all import changes by Monday at the latest; otherwise not time to test
        • @Chris tests build fun now.
  • Misc

    • TB import successful at EMBL. Moving forward
    • Polyline.points is 4.2 only
    • Prepairing an agenda for ASCB discussion
      • Things that keep sliding: perm & codegen
    • presentation from Colin week after ASCB on fs level integration
    • graffle: most tasks pushed back for work on 4.1.1 (QA started this week)
    • Scott going to Pasteur
    • Josh and Donald discuss delete
    • Will visiting on EM
  • OMX issue files

    • 2 problems: floating point and large dynamic range (-20K to +100K)
    • 3 channels
    • DV header mashes min/max/mean of 3 channels
    • softworx feature: save to another data type (16bit integer), scale to datatype
    • file on disk ~600MB; scaled is 6MB as .dv
  • HDF

    • http://queue.acm.org/detail.cfm?id=1628215
    • Adding an OMERO experiences response
Document Actions