Put agenda, discussion, minutes, and action items here.
Meeting will be at 2 PM CDT, on BlueJeans:
Minutes of the meeting:
We discussed real-time user interactions. One issue is to avoid excessive communication.
@gpdf lists three 3 scenarios:
When mouse is moving. Example: coordinate readout in realtime
When mouse is paused: Evaluate pixel value (from server). This is a
bit more expensive.
Select a region: Invoke an action by clicking.
We need use cases.
Do we want, for example recompute a histogram in real-time as a line is dragged by the mouse (during mouse moving), rather than on mouse pause?
When is additional “zoom level” image data sent? This would enable more client side functionality for previously specified algorithms (eg, aperture photometry, or noise, or pixel min/max). FF enhancements of this sort are not likely before January, because they are busy refactoring FF to use more modern libraries (get rid of some Google code?).
a) @tatianag, or other FF people: Document the FF algorithm that generates the browser image.
An upgrade suggestion: Let the user select the algorithm. (eg, min or max pixel).
b) @tatianag: Find out if FF can do this.
Action: @marshall and @tony_johnson will work on specify the desired header keywords. @tony_johnson has begun this (a note in the community). None of us knows what the on-disk format will be, and what is the best way to preserve (for example) the amplifier locations in a single-extension mosaic-ed image. One possibility: Do the mosaic-ing (at browser level) during DAQ at BNL. Clicking on a spot pulls up the appropriate sensor-level image at full resolution.
Action: @victor_ren (and others) Find out how DS9 knows which extension the current mouse position is in. @victor_ren and the FF team will sit in on a demo by @marshall (and @tony_johnson).
What does DS9 do with overscans? We think that DS9 will reserve screen space, but the display can be suppressed - shown as black. Is that right?
Action: @dyue2: Is FF an adequate server, or do we need another? It will be instructive for the FF folks to know what functionality is desired.
a) @JJT: Sketch some typical user activities How do they get started, find out where the data is, etc? How much is menu driven, how much is cmd line? Eg, should they browse a list of image files? What other UI features will the users want? Ask Heather and Homer for user input.
b) @tatianag: Show FF image browsing to Heather and Homer. Tatiana will send a pointer to a demo.