Personal tools
  • We're Hiring!

You are here: Home Community Minutes Conference Calls 2009 2009-02-20 Project-wide Conf Call

2009-02-20 Project-wide Conf Call

Attending:

Agenda

  • OMERO Summary

    • beta4
      • possible 4.0-Docs milestone?
      • most search tickets to 4.1
      • Database
      • FS - symbolic links? deleting on import?
      • sha1 = "pending" ?
  • LIMS discussion

  • Bio-Formats

Notes

  • Misc

    • T-Shirts will be ready at beginning of March.
    • Abstract being submitted to THE DYNAMIC CELL, EDINBURGH 1-4 April 2009 http://www.jointbscbbs2009.org/
  • Dundee CLS Omero week plan

    • Booking request in progress for Atrium (Morning Mon & Wed) and other room (Thu & Fri) - JBC2 for Thursday and JBCM for Friday
    • Approx. 27 T-Shirts ordered in range of sizes.
    • Have pull-up banner from enterprise event. Will look into getting a couple of poster boards to have further posters/artwork on. Looking at getting UsableImage poster content from David.
  • docs milestone ?

    • link to bioformats, etc.
    • no objections at least
  • beta4 status

    • blockers
      • 1176 sequences & atomikos
      • 1059 oom on import (general performance)
      • 1184 slow query
      • 1170 image->pixels index
      • 1191 database
    • ticket cleanup
      • by monday please. ticket cleanup
      • accurate : not umbrella tickets, but true tasks
      • blocker and critical only for the moment.
      • user name changes. might need to check CC/reporter etc. in your bugs
    • summary
      • well-tested release
      • ...but...there are lots of deeper inner workings that are still in flux
      • insight and importer are all quite stable
      • importer todos
        • sequence issue
        • rfloat return values
        • turning sha1 logic back on (also on insight)
      • web
        • few things to fix. plan on making mage ready over the weekend
        • storing bugs on webserver * things that are seen by user * can be optionally emailed and sent to us * turning on my default, opt out
      • PE
        • adding a few features
        • string comparison, searching
        • possibly a new type for protocol editors (beyond annotations)
    • need to say monday morning where we are
      • conference call notes
      • working on stability
      • decision by Friday
      • need criteria for deciding on what things we will fix
        • breakages in our clients
        • write up known-issues like in past versions
  • annotations / analysis

    • adding fields to the annotations? (Bernhard)
    • What's the real usability?
    • Will need to deal with sooner rather than later
    • What's the volume of data we want to handle?
    • cf. insight:#845 and the memory issues with java
      • things are coming faster from the server
      • as long as you aren't doing anything too complex, it's ok
      • possibly need to move on for the next version
      • re-writing the measurement tool for 4.2 might be bad timing
  • fs

    • importing via symlinks (for now: not 4.0, unclear) && deleting on import (for now: clean up your mess)
    • need to clearly define the "following" semantics
  • formats

    • testing over the last week; looking good
    • test suite run on all the data; no major failure
    • few imagej things to test
    • no memory leaks, no regression bugs : metadata and pixels the same as in previous releases
    • C++ code has been committed for Linux (using CMake)
    • some free bandwidth for testing after 4.0 release
    • Andrew/ImageJ: trying to build bf widgets, but not using all APIs to simplify things
  • lims

    • essentially full data management across hetergenous data sources (fast/flexible/...)
    • similar to "what is an image" question. what is a screen/reagent/etc.?
    • revamping some one of the milestones on priorities
    • also have postponed strongly typed additions to the database
    • almost the time to start reviewing that.
      • user configurable tables
      • more than just keys and values
      • but consistency across the languages, etc.
  • client ticket 845 - strategic solutions

    • take 2 weeks to investigate solutions?
    • 2 parts
      • server-side scaling
      • client-solution
    • were trying to avoid doing it twice, but ...
    • server Qt and client JOGL ?
    • pushing image manipulation code to server (split view)
    • for 4.0, leave server alone and review in 4.1
    • keep a good idea of watching the deployment story during 4.0
    • push 4.2 back and use that release for the re-architecture
    • using what Donald learns while experimenting
Document Actions