SctGUI - Getting Started

Under normal circumstances, sctGUI will automatically be invoked as part of the SctRodDaq startup script, and will open in parallel with the main DAQ IGUI. Initially, sctGUI will open in an unconfigured state: the display is headed 'Display UNCONFIGURED' and no modules are visible on the display. By default, Barrel 3 is visible on the display. If you wish to change the default barrel or endcap view, use the Preferences->'Default SCT View' menu.

When the DAQ has moved to state 'Configured' as indicated in IGUI, sctGUI automatically configures, and the modules in the current module configuration become visible on the display. sctGUI automatically switches to 'Module Group Selection' display mode. You can straightaway switch to any other display mode, by choosing the appropriate Display menu or by right-mouse clicking on the display and selecting a display mode from the popup-menu.

CLASSPATH considerations

Your CLASSPATH is automatically set up from the SctRodDaq setup scripts, and all external jar files are automatically included in your SctRodDaq distribution IF you are using a binary release. However there is one exception: if you wish to upload any SctRodDaq test data to the SCT database, you need to download the SCTTEST_3_21_P.jar file from

and explicitly add it to your CLASSPATH. It is best added to your CLASSPATH in your logon script so that you do it once and can then forget about it.

If using a non-binary release of SctRodDaq, there are other external packages that you need to download, including '' from the Geneva database websire, JAIDA etc. These should be documented in the release notes.

Setting your Preferences

The first time you start SctGUI, you should set your Preferences. See the description of the Preferences menu for more details.

Exercising SctRodDaq without Hardware

SctGUI and the full SctRodDaq analysis chain can be run and exercised without any hardware present at all, and without running the main DAQ. SctRodDaq is distributed with a set of SCTDAQ raw data files which correspond to the SCTDAQ data for a module (specifically, a full SCTDAQ charcterisation of module 20220330200020 taken at Cambridge using SCTDAQ version 3.41). You can invoke tests from SctGUI for which the raw data is extracting from the SCTDAQ root files instead of from the RODs. The full SctRodDaq analysis chain and functionality runs as normal, regardless of the origin of the raw data.

To run without DAQ and hardware, you nonetheless need to start all necessary processes and IS servers,using a script or sequence of actions like the following:

ipc_server &

sleep 5

ipc_server -p SCT &

sleep 5

config_server &

sleep 5

is_server -p SCT -n EventData &
is_server -p SCT -n FittedData &
is_server -p SCT -n TestData &
is_server -p SCT -n ControlData &
is_server -p SCT -n SCTAPIServer &
is_server -p SCT -n ConfigurationServer &
is_server -p SCT -n SCTDBData &
is_server -p SCT -n SCTDCS_Data &
is_server -p SCT -n RetrievedData &

FittingService &
AnalysisService &
SctHighLevelTest &

rungui &

Once the above processes are running, you can restart SctGUI repeatedly by 'rungui &'.

To take some data, first make sure that module 20220330200020 is present in your barrel or endcap display. If it is not present, select the Options->Configuration->'Manual Configuration...' menus. Enter 20220330200020 as the serial number, and select any position in your barrel or endcap.

Then to invoke a test, select a test in the Tests->'SCTDAQ Exerciser' menu.

   Back to SctGUI User Manual Index