Details
-
Type:
Improvement
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: SUIT
-
Labels:
-
Epic Link:
-
Sprint:SUIT Sprint 2017-01, SUIT Sprint 2017-2, SUIT Sprint 2017-3, SUIT Sprint 2017-4
-
Team:Science User Interface
Description
There was a brief discussion today of the desirability of supporting multiple-pane displays of (small) plots (i.e., x-y plots and histograms) in the same way that we do for images, allowing the creation of grids of plots, as well as the use of some of the other concepts we have for multi-image viewing such as blinking and manual or auto-play stepping through a series of plots.
There's no doubt that this would be useful!
However, we have to think through what the use cases for this are, because this will affect the way that we allow users to create such displays and how we label them.
Converting this ticket to a story would be a request that we collect a set of use cases.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | David Ciardi [ ciardi ] |
Epic Link |
|
Story Points | 8 |
Sprint | SUIT Sprint 2017-01 [ 299 ] |
Sprint | SUIT Sprint 2017-01 [ 299 ] | SUIT Sprint 2017-01, SUIT Sprint 2017-2 [ 299, 309 ] |
Rank | Ranked higher |
Sprint | SUIT Sprint 2017-01, SUIT Sprint 2017-2 [ 299, 309 ] | SUIT Sprint 2017-01, SUIT Sprint 2017-2, SUIT Sprint 2017-3 [ 299, 309, 357 ] |
Rank | Ranked higher |
Sprint | SUIT Sprint 2017-01, SUIT Sprint 2017-2, SUIT Sprint 2017-3 [ 299, 309, 357 ] | SUIT Sprint 2017-01, SUIT Sprint 2017-2, SUIT Sprint 2017-3, SUIT Sprint 2017-4 [ 299, 309, 357, 603 ] |
Rank | Ranked higher |
Sprint | SUIT Sprint 2017-01, SUIT Sprint 2017-2, SUIT Sprint 2017-3, SUIT Sprint 2017-4 [ 299, 309, 357, 603 ] | SUIT Sprint 2017-01, SUIT Sprint 2017-2, SUIT Sprint 2017-3, SUIT Sprint 2017-4, SUIT Sprint 2017-5 [ 299, 309, 357, 603, 604 ] |
Rank | Ranked higher |
Story Points | 8 |
Assignee | David Ciardi [ ciardi ] |
Sprint | SUIT Sprint 2017-01, SUIT Sprint 2017-2, SUIT Sprint 2017-3, SUIT Sprint 2017-4, SUIT Sprint 2017-5 [ 299, 309, 357, 603, 604 ] | SUIT Sprint 2017-01, SUIT Sprint 2017-2, SUIT Sprint 2017-3, SUIT Sprint 2017-4 [ 299, 309, 357, 603 ] |
Sprint | SUIT Sprint 2017-01, SUIT Sprint 2017-2, SUIT Sprint 2017-3, SUIT Sprint 2017-4 [ 299, 309, 357, 603 ] | SUIT Sprint 2017-01, SUIT Sprint 2017-2, SUIT Sprint 2017-3, SUIT Sprint 2017-4, SUIT Sprint 2017-6 [ 299, 309, 357, 603, 609 ] |
Rank | Ranked higher |
Sprint | SUIT Sprint 2017-01, SUIT Sprint 2017-2, SUIT Sprint 2017-3, SUIT Sprint 2017-4, SUIT Sprint 2017-6 [ 299, 309, 357, 603, 609 ] | SUIT Sprint 2017-01, SUIT Sprint 2017-2, SUIT Sprint 2017-3, SUIT Sprint 2017-4 [ 299, 309, 357, 603 ] |
Remote Link | This issue links to "Page (Confluence)" [ 28025 ] |
Remote Link | This issue links to "Page (Confluence)" [ 31460 ] |
Example: a series of plots of a pair of variables x and y, or a series of histograms of a variable x, one per bin of a histogram on another variable z.
"How does the distribution of x and y change as you vary z?"
One can imagine this being interesting both for continuous-valued z variables (e.g., photometric redshift) and for category-valued z variables (e.g., an object classification, or the WISE variability codes). For a category-valued variable, no association with a histogram would be needed.
When coupled with the programmatic (Python) interface to Firefly it would be possible to drive a series of plots with a more complex selection (e.g., non-uniform bins in photo-z) than would be realistic to provide with direct UI control.
In this use case, the labeling of the plots in the grid would need to be able to indicate the values of z used in the selection.