Personal tools
  • We're Hiring!

You are here: Home Community Minutes Conference Calls 2012 2012-02-07 Tuesday Meeting

2012-02-07 Tuesday Meeting

Attending: Josh (notes), Liza, Emma, Jason, Chris, Carlos, Melissa, Scott, Elwood (notes), Simon, Mark (14:30), Stick (14:30), Dom, Will (left 15:40 UK), Carlos (14:40 UK)

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

Housekeeping Pre-Meeting - 2pm Start

  1. Matters Arising (<10 mins)

    • Put in action points and PENDING items from last meeting.
    • Emma: provide list of calendar people
    • Elwood: move HIC meetings to OME-Scheduling. Done
    • Andrew: plan ROI discussion - Wed at 15:00
    • Andrew: plan DB alignment discussion - Tue (today) at 11:00
    • Andrew: upload to drupal
    • All: decide on new matlab version (Jean-Marie)
    • Stick: look into applet - FIXED
  2. Email and Forum Review - checked at 10:30 (5 mins)

  3. Scott: For the people in Dundee I need 8-10 people to test pfelts server. We will all need to login at the same time to check the slow down on the server.

    • For people in Dundee only

    • Enter the URL into your browser

    • http://ome-pfelts.openmicroscopy.org/webclient/

    • Log in using your ldap username and password

    • Your username must be in uppercase in the following way

    • saloynton = SALoynton

    • When logged into the web client click on data

    • When in the data manager click on your username in the drop down menu and change to group leader paul felts.

    • Click into the first set projection folder and open the 13th of February dataset.

    • Open and view one of the images in the list below and zoom in and pan round

      21_Foetal Skull.svs [Series 1]
      
      22_Foetal tibia.svs [Series 1]
      
      23_Adult Tibia.svs [Series 1]
      
      4_Trachea.svs [Series 1]
      

Agenda - 2:30pm Start

  1. Accepting minutes from last meeting

  2. Sprint Bug Report (5 mins)

    • Closed bugs: 5 (1 major, 4 minor)
    • New bugs: 9 (3 major, 6 minor)
    • Total bugs: 84 (4 blocker, 10 critical, 20 major, 50 minor)
  3. Change Group: Scott's presentation (10-15 mins)

  4. Sprint Tickets/bugs

  5. Recruiting Update (5 mins)

    • Support positions
    • Developer positions
    • NIH-NIA position - shortlist? Candidates
  6. Meetings (5 mins)

    • February Developer Meeting Agenda
    • Paris Meeting Dates (week starting 18th June)?
  7. Code from Sardinia (5 mins)

    • I'm attaching the code tarball. As stated in the HTML docs, it depends on Biodoop Core version 0.2: http://biodoop.sourceforge.net/core However, Pydoop is not required at this time.
  8. Any other business (<5 mins)

    • Scott: I need 8-10 people to test pfelts server. We will all need to login at the same time to check the effect on the server.

Notes

Attending

* Josh (notes), Liza, Emma, Jason, Chris, Carlos, Melissa, Scott, Elwood, Simon, Mark (14:30), Stick (14:30), Dom, Will (left 15:40 UK), Carlos (14:40 UK)

Housekeeping Pre-Meeting - 2pm Start

  1. Matters Arising (<10 mins)

    • Put in action points and PENDING items from last meeting.
    • Emma: provide list of calendar people
    • Elwood: move HIC meetings to OME-Scheduling. Done
    • Andrew: plan ROI discussion - Wed at 15:00
    • Andrew: plan DB alignment discussion - Tue (today) at 11:00
    • Andrew: upload to drupal problems; PENDING
    • All: decide on new matlab version (Jean-Marie) TABLED
    • Stick: look into applet - FIXED
  2. Email and Forum Review - checked at 10:30 (5 mins)

  3. Scott: For the people in Dundee I need 8-10 people to test pfelts server. We will all need to login at the same time to check the slow down on the server. (Started 14:08 UK)

    • For people in Dundee only
    • Enter the URL into your browser
    • http://ome-pfelts.openmicroscopy.org/webclient/
    • Log in using your ldap username and password
    • Your username must be in uppercase in the following way
    • saloynton = SALoynton
    • When logged into the web client click on data
    • When in the data manager click on your username in the drop down menu and change to group leader paul felts.
    • Click into the first set projection folder and open the 13th of February dataset.
    • Open and view one of the images in the list below and zoom in and pan round * 21_Foetal Skull.svs [Series 1] * 22_Foetal tibia.svs [Series 1]
      • 23_Adult Tibia.svs [Series 1]
        • 4_Trachea.svs [Series 1]
    • Conclusion: Slow.
  4. Done 15:20

Agenda - 2:30pm Start

  1. Accepting minutes from last meeting

    • Andrew: when posting the minutes, put the attending line at the top.
    • ACCEPTED
  2. Sprint Bug Report (5 mins)

    • Closed bugs: 5 (1 major, 4 minor)
    • New bugs: 9 (3 major, 6 minor)
    • Total bugs: 84 (4 blocker, 10 critical, 20 major, 50 minor)
    • Melissa and Will get a gold star
  3. Sprint Tickets/bugs

    • Not much.
  4. Recruiting Update (5 mins)

    • Developer/Support positions
      • Unofficially made an offer.
    • Upcoming interviews. Emails will be sent.
    • NIH-NIA position - shortlist? [Candidates] https://docs.google.com/spreadsheet/ccc?key=0AuqP9_Rq_HgldGJGNGYxaHMtZmZOUG1PMlhqMnlMcVE&hl=en_GB#gid=0
    • Done 14:42 UK
  5. Meetings (5 mins)

    • February Developer Meeting Agenda
      • Emma: Few tentative things
      • Need suggestions from people who want to get things done.
      • But could also be free-form if everyone is to be coding.
    • Paris Meeting Dates (week starting 18th June)?
      • Jason: any vetos? (works for Spencer)
      • Carlos: 18th is perfect. 25th is a no-go.
      • Liza: how long? 2.5 days
      • Melissa: for folks from the US, youre underway for a week.
  6. Change Group: Scotts presentation (10-15 mins; Started 14:45 UK)

    • Scott: Jean-Maries work, in-progress for last several weeks
    • Implement and allow users to work in multiple groups
    • Range of changes:
      • Import: into specific image
      • Jason: Cut-n-paste v. copy-n-paste
      • Chris: need to work on “add a user to the group display” UI
      • Josh: running against gretzky; no chgrp
      • Search across groups: thumbnails didnt show up
      • Jason: really complex territory.
        • Previously have had the advantage of only showing a dataset at once
        • Now: “Going to show you a lot more data”
        • Chris: had this discussion with Dom last night.
    • People like Iain have 100s of projects.
      • If someone like that is in your view, then hierarchy is polluted.
      • Jason: 2-3 years worth of work.
      • “Project” == “Experiment” (in Swedlow lab)
      • Good search / filter is part of the solution (to too much data in hierarchies)
      • Jason: (feeling) display looks like a small portal to a lot of data.
      • Only visible display of hierarchy is “Swedlow Group [2]”. Dont know who it belongs to if youve scrolled down. Previously context was up at the top of the window.
      • Josh: comparison to mailbox / app. 100s of folders dont know where I am.
      • Dom: how often will you come back to an experiment? Jason: rapidly decaying curve, but different for different experiments.
        • Discussed with Scott and Chris. Finish with experiment then “archive” it. (put it away)
        • Chris: show last 10 most recently accessed datasets. Jason: i.e. smart mailboxes.
        • Chris: if we start showing multiple users, its impossible to figure out where you are.
        • Jason: datasets are different conditions/perturbations. image is a sample.
        • NB: how do we get more details about what people do?
        • Emma: analogy, groupwise. Had archive functionality.
        • Jason: see dates under images. (But those are creation not access dates)
        • Emma: but when working on a paper, its not about access-dates anymore.
    • Jason: very advanced, but were going to need to backup and re-assess
      • Not just access
      • Verbal feedback, but also reporting from users
    • Chris: Users will say “show me everything”. Dom: definitely.
      • Or “only the things I want to see”
      • Competing with much larger teams now.
      • Make use of the metrics we do have. (top 25 users, etc.)
      • drag-n-drop doesnt scale
    • Jason + Chris: monash / Katie / Perkin Elmer
      • Dom: good metrics could absolutely alleviate some of the problems.



      • Jason: do we need the metadata on the right?
        • Doesnt have to be there, but opens by default.
        • Andrew: the folding tabs take a lot of space on the left.
        • Dom: something might come forward in a few weeks.
        • Will: one reason people have 100s of projects, is we only have 2 hierarchies
        • Dom: good system-wide search functionality. hierarchy is important, but everyone is using search.
        • Jason: Searching box with indexed data.
        • Will: different workflow when looking at someone elses data (search); but when looking at your own you know where it is.
        • Chris: 90% of usage is accessing your own data. Not facebook.
        • Jason: so Jean-Marie is showing your own data in its various context
        • Elwood: search could filter down to just the context youre looking for.
      • Chris: users are going to come and ask why cant I create my own group with people in.
        • Josh: background, motivation factor, creating a group is for PI usage.
    • Emma: to prevent secret science, but cater to your users as much as possible.
      • Chris: Data management is only at 2 levels, projects/dataset and tag/tag-set.
      • Cant go to a project and then filter by tag.
        • end up encoding information in proj/dataset names for sensible sorting.
    • Next steps/actions
    • Jason: 1. client and server working together.
      • Josh: works with change group branch (howe)
      • Jason: 2. Get Iain / Katarina / Michael (group working together)
        • Ask explicitly “is this presentation of data too complex?”
        • Will: data spread between groups? Chris: probably everything is in swedlow lab.
        • Perhaps Michael is slightly different.
        • Jason: Perhaps a consequence of not being able to use groups. Will: also dont need to, because that only provides permissions. Jason: Better place to get feedback? No.
      • Jason: 3. queries on nightshade, what access is like
      • Also:
      • Dom to give a presentation in a week or two
        • Discussion with Jean-Marie when he gets back.
    • Chris: also creates a session for each context. Complex environment not sustainable; cant support in the web.
    • Will:
      • https://trac.openmicroscopy.org.uk/ome/attachment/ticket/7705/BrowseGroups-MockUp.png
      • Not sure theres a need to be in multiple groups
      • Speed up access to groups
      • Could still open images from multiple.
      • Jason: lot of wasted whitespace on the left?
    • Emma: could hide.
    • Will: collapse whole left when youre not working in groups.
      • Dom: recent data that youre interested in, only work that youre working on.
      • Jason: could imagine opening two images and wanting to know that they come from two different groups.
      • Emma: when you want to move the data, youll need to know.
    • Dom: then thats another thing we need to solve.
    • Andrew: seems like we keep drawing divding lines through our rectangles. Getting complicated.
    • Andrew: separate windows? (MDI)
    • Chris: drag-n-drop only works on Mac OSX because popups are small. If you ask a Windows user, they would never do it. They maximize everything and then cut-n-paste.
    • Emma: I disagree with that statement.
    • Chris: Windows Explorer is just like our data manager.
      • Dom: could also use temporary basket.
      • Chris: no applications which work that way.
        • Will: screenshot partly based on Outlook365; email uses right-click move to folder.
        • Jason: like the outlook web interface.
    • Emma: more to discuss...
  7. Done: 15:36 UK

  8. Code from Sardinia (5 mins)

    • Im attaching the code tarball. As stated in the HTML docs, it depends on Biodoop Core version 0.2: http://biodoop.sourceforge.net/core However, Pydoop is not required at this time.
      • Josh: we had them talk through it at the last meeting, can we refactor some of it in to the main code base?
        • having them online with comments
      • Emma: git workflow after this might be starting
      • Josh: not a whole lot of steps integrating with them.
        • what part of the code do you want other people to utilise?
      • Josh: make time in a couple of weeks to look at it.
      • Emma: paper and visit in March?
  9. Any other business (<5 mins)

Actions

* Andrew: discuss drupal issues with Curtis
* Emma: provide list of calendar people
Document Actions