Scope Trace Viewer

ScopeTraceViewer

Description

Scope Trace Viewer ia a tool for displaying traces. Scope Trace Viewer does not allow user to browse through the ENS but rather provide a set of configurations for each machine. These configurations define the trace channels which can be viewed in the Scope Trace Viewer.

There are three types of configurations supported by this application. The first type are normal configurations, where each configuration define one trace. User is allowed to browse among these configurations and to add the described traces to the chart. The second type are history configurations which define the history channel which is shown in the history trend if history mode is selected. The third type are predefined sets of traces. This type is available from the Comparison Tab. These configurations define several traces which can be placed in any of the three charts in the application.

The application can be used in two different modes: live and history. In live mode the user can inspect the live trace data, while in history mode the user has to first select a history configuration and the trend chart for the selected configuration will be shown. By clicking inside the chart, the trace history will be loaded for the timestamp at whcih the mouse click occured.

Scope Trace Viewer offers several features for trace examination, such as sequence, reference saving etc.

Start

Scope Trace Viewer can be started by running the java class.

de.desy.tine.apps.ScopeTraceViewer

This will start a plain Scope Trace Viewer, with the first available machine selected.

Run the Scope Trace Viewer with Java Webstart (only accessible from DESY internal network).

Start-up parameters

Scope Trace Viewer supports all start-up parameters listed in the common features section. In addition, the viewer supports the following parameters.

The list of start-up parameter tags
  • stv.machine - the name of the context that will be selected (if it exists)
  • stv.configuration - Scope Trace Viewer can work with several types of configurations. One type of such configurations is the type where several traces are defined, where each trace belongs to a single chart in the ScopeTraceViewer. By supplying the name of this configuration if it exists in the context supplied as the stv.machine parameter that configuration will be selected and the appropriate traces applied to the charts. The available configurations for this option are available for selection in the application under the tab Comparison.
  • stv.config - the second type of configurations for Scope Trace Viewer are configurations of the device server and property. User can specify the configuration which will be selected at start up. This configuration selection is otherwise available on the main screen in the Configurations list. Upon selecting such configuration user has the option to browse and select a desired device and add the trace to the chart.
  • stv.device - if the user supplies the this parameter and the value matches one of the devices for the selected configuration (stv.config) this device will be automatically added to the top chart.
  • stv.chartmode - the parameter which defines if the Scope Trace Viewer should be started in the 'chart mode'. This mode that the chart area for traces will be extended across the complete Scope Trace Window. The chart mode option can have values true or false.
  • stv.sequence - the parameter specifies if the sequence should be selected. There are two possible option for this parameter's value: linear and overlap. The appropriate sequence is selected. If the given value is none of the above, sequence is set off.

    Example: we want to start the scope trace viewer with selected context LINAC2 and want to load the configurations PIA Kickers (because we are loading configuration which has spaces in the name we have to provide quotation marks with the name).

    java -Dstv.machine=LINAC2 -Dstv.configuration="PIA Kickers"
     -cp [classpath] de.desy.tine.apps.ScopeTraceViewer