Kepler

What other visualization of data can we come up with in addition to plotting?

Thanks for the good screencast. I also played around with it and have some comments:

Plot Viewer:

- The initial ranges for the axes are too big. Removing the demo series and setting Auto Range for Both Axes would probably fix this.

Plot Designer:

- The table doesn't seem to update when changes are made. For example, when I drag and drop a sensor onto the table, the new row doesn't appear until I click elsewhere in the table. I also couldn't get the Delete Row button to work.

- It might be nice to automatically select a different point type and color for each new row.

- The default table that appears when there are no plots is a little confusing since it doesn't produce a plot in the viewer. Maybe get rid of it?

Other:

- The plot designer view only shows up in EV Model. It'd be great to be able to use it for regular workflows.

- I also noticed the addition of the SpanDataListeners to the Sensor actor. Is this how sensor values are fed to the plot? Alternatively, you could get the values from the input or output ports (e.g., Sensor's "data" port) using IOPortEventListener interface. This would allow any actor's (numerical) data to be plotted without having to modify the actor's code.

- Do the configurations of plots gets saved? It be might be nice to save the design in the KAR so they don't have to be reconfigured each time.

(In reply to comment #2)

Thanks for the good screencast. I also played around with it and have some
comments:

Plot Viewer:

- The initial ranges for the axes are too big. Removing the demo series and
setting Auto Range for Both Axes would probably fix this.

Plot Designer:

- The table doesn't seem to update when changes are made. For example, when I
drag and drop a sensor onto the table, the new row doesn't appear until I click
elsewhere in the table. I also couldn't get the Delete Row button to work.

- It might be nice to automatically select a different point type and color
for each new row.

- The default table that appears when there are no plots is a little confusing
since it doesn't produce a plot in the viewer. Maybe get rid of it?

Other:

- The plot designer view only shows up in EV Model. It'd be great to be able
to use it for regular workflows.

- I also noticed the addition of the SpanDataListeners to the Sensor actor. Is
this how sensor values are fed to the plot? Alternatively, you could get the
values from the input or output ports (e.g., Sensor's "data" port) using
IOPortEventListener interface. This would allow any actor's (numerical) data to
be plotted without having to modify the actor's code.

- Do the configurations of plots gets saved? It be might be nice to save the
design in the KAR so they don't have to be reconfigured each time.

All the points in this comment have been addressed except for the last, saving sensor configurations in the KAR file. That seems like a distinct enough task that if enough people want it, a separate bug can be filed. Closing.

changing bugs from REAP to Kepler product

Original Bugzilla ID was 4752