Design the generalization for the reduction of higher order data to 1D/2D display data #1291
Labels
audience - developer
affects internal development or blocks another issue
effort - week
a week or less
f - data
f - displays
impact - critical
has no practical workaround and prevents regular use
priority - medium
automated priority tag
reach - all
affects all users weekly
skill - data
skill tag
skill - design
skill tag
skill level - expert
skill level tag
type - internal maintenance
Display ideas - user can have multiple displays; each display may have it's own sequence/collection/mask/etc.
One way to think about things: the slice interval is a function to reduce the data to 1d; the mask/integration is another function to reduce to 1d. Maybe the display data channel should track the "function to reduce to 1d" for collections; then the "graphics" should be used to edit that.
The text was updated successfully, but these errors were encountered: