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"
FLIM
- tasks to get done
-- NDIM model
-- get ready for scripts in anger
-- get ready for new camera
-- encorporating Pieta's script
--- it's broken (mathematical, mixed variables)
--- will take work to get it working
--- basic version is running against OMERO
-- optimizations for values like SPImage
-- dealing with ROIs
--- drawing them, storing them on the server
--- some version of trunk (matches scripts)
--- Donald will work on ROIs today
-- visualization mechanism (heatmaps)
-- rolling back the fake FLIM
-- submissions
--- submitting 200 images to server
--- not running it on the server (nor in parallel)
- time scales
-- tried to talk to him 2 weeks ago (conference)
-- he's doing it now. (starts today)
- discuss NDIM Monday
-- won't be implementing anything right away
-- Donald: hacking something up
-- Jean-Marie: if data comes as now, we're fine
- tickets
-- roi
--- difference which rois for measurement and for viz
--- namespaces
- mongo
-- 3 days away from insight writing to mongo
-- omero pojos ok
-- was modifying insight gateway
-- Chris: means changing everything?
-- ROI is the starting point (drawing)
-- Jason: don't like the namespace "measurement"/"visualization" is something user needs to understand
--- from users POV, need "infinite flexibility" of tagging
--- Jean-Marie: is going to be extremely painful
-- Chris: starting with a single keyword (before alternative storage)
-- NB: tags don't have a namespace right now
-- combo box drop down with the various workflows
-- #namespace manager
- preview
-- john: get another nightshade
-- get a grid engine
- decisions
-- move alternative storage out of sprint
-- donald works on flim
-- discuss the plan for next mongo
-- next sprint: what else suffers?
- end of this iteration
-- good chance to have roi, flim working
-- good chance of some visualization
-- some heatmap, uploaded as an image or jpeg annotation
-- may not be fast (on cluster)
-- how much work to get scripting working?
- iteration 5
-- by end, flim done? no, but handing something to david by next week
-- on the cluster (or optimized)
-- (conservative and add a extra week, i.e. middle of week)
- docs for clients
-- Examples of different things in the scripts
- things that have to be maintained
-- matlab / cellprofiler
- shooting for a middle ground
-- have to decide what we're going for (4.2)
-- is there any technological middle ground?
--
Notes from discussion Mar. 11: