cogdebugger.ui.fieldvisualizations.scalar
StackedTimeSeriesPanel
Related Doc:
package scalar
A FieldType describing the shape of the ScalarField being visualized.
A list of properties that should be persisted when the app closes, and restored the next time it's launched.
A list of properties that should be persisted when the app closes, and restored the next time it's launched. A common example of a persistent is the zoom/magnification level of the viewer. Be sure to add any relevenant properties to this list in your Viewer subclasses!
Returns the XML representation of this viewer's properties, suitable for saving into a file.
Returns the XML representation of this viewer's properties, suitable for saving into a file.
Reset the visualization.
Reset the visualization. An optional operation; subclasses must override this method or else it does nothing.
Updates the visualization based on the contents of data.
Updates the visualization based on the contents of data.
The src argument was orignally meant to reference the
kernel/field/object that generated the data, in order to support
composite visualizations (that is, viewers that produce a visual based on
the data from several different sources), but launching such viewers in
the current UI is clunky at beset, so this feature isn't used. Viewers
that only visualize a single field's data can probably safely ignore this
arument (and indeed, most of the current ones do).
The field or object that generated the data argument
New field data that needs to be rendered by this viewer
Parses the XML tag produced by the propertiesTag method and restores
any saved valued to this Viewer.
Parses the XML tag produced by the propertiesTag method and restores
any saved valued to this Viewer.
A visualization for SalarFields of two or fewer dimensions that renders the field as a number of stacked timeseries plots, one per field element. This visaulization's performance is quite sensitive to the target field's size; it is not recommened for fields with a large number of elements, as it will render quite slowly.
This implementation keeps a fixed size history of the last 500 steps. The oldest value is at the left end of the chart, the most recent at the right. (This history is part of the reason this visualization can't handle large fields; the field size is effecitvely multiplied by 500.))
This visualization is based off the old Cog 3.x MultiXYPlot, which was not particularly efficient. This visualization also takes a long time to update, especially if its tracking many values from a large field. If the target field is updating more rapidly than the visualization, there will be gaps in the history. The most recently recorded value is extended into these gaps (which has the tendency to cause the timeseries to render as a stepped line).