ADC 400F Manual descarregar pdf (Página 44)

Chapter 4. More information

If you are preparing a system that will be used many times, you may want to automate the startup as well

as run the Readout software under the control of a Readout Gui called ReadoutShell. Normally this

automation is done by:

• Writing scripts to start each of the components of the system.

• Attaching these scripts to icons on a KDE desktop.

It is a good idea to get all of your software debugged ﬁrst, as debugging programs run under desktop

icons can be challenging.

4.1. Scripting and desktop icons

The trickiest issue for creating scripts that will become desktop icons is that the environment in which

you are running your scripts and programs is not well known. You should ensure that each script sources

appropriate login scripts and sets the working directory you want your application to run in. We will

generate four scripts:

1. A script to run SpecTcl

2. A script to initialize SpecTcl, loading in our histogram deﬁnitions and connecting it to the

appropriate online system.

3. A script to run the ReadoutShell Readout GUI.

4. A script that will be used by the ReadoutShell to start the readout program.

Once these scripts are written we will create desktop icons for the ﬁrst two scripts so that you can start

SpecTcl and Readout by clicking on the desktop.

4.1.1. Scripts and a desktop shortcut for SpecTcl

The following script will be used to start SpecTcl:

Example 4-1. SpecTcl startup script.

#!/bin/bash

. /etc/profile # ➊

. ~/.bashrc

cd ~/experiment/spectcl # ➋

./SpecTcl <setup.tcl # ➌

1 2 ... 39 40 41 42 43 44 45 46 47 48 49 ... 73 74

Sem comentários

ADC 400F Manual Página 44