10. JOB FILES
10.1. Introduction
The GammaVision
.JOB
file consists of one or more lines of ASCII text representing a series of commands that can automate most of the functions described earlier in this manual. The details of the commands and the required syntax are given in this chapter. A
.JOB
file can be created within GammaVision using the Services/Job Control... command or in Windows Notepad or any other ASCII editor. A
.JOB
file can be started from Services/Job Control..., or by including the name of the
.JOB
file (e.g.,
GVDEMO.JOB
) on the command line when GammaVision is first started (see Section A.1).
.JOB
files can be used for the following types of functions:
! Performing a repetitive task, such as running a sequence of experiments without user intervention.
! Defining initial conditions at startup (useful in preloading presets after a power loss for the 916/916A/917/918/918A each time GammaVision is run).
This version of GammaVision is compatible with
.JOB
files written for previous versions of
GammaVision or MAESTRO. The text versions of these files will work on new Detectors as well as older models, with the exception of new or deleted commands.
10.1.1. JOB Command Functionality
10.1.1.1. Loops
GammaVision can run repetitive loops. Furthermore, the current loop count can be included as a variable in any string, including filenames, program parameters, and text. Data can thus be stored with unique filenames and labeled with unique descriptions.
In previous versions of GammaVision (and MAESTRO) JOB files, the macros $(Loop) and
$(Loop1) were used to embed the Loop counter (zero- and one-based) into text strings. As of v7,
GammaVision can add any offset to the loop counter with the $(LoopN) Macro.
For example, the following JOB commands:
LOOP 5
ASK_CONFIRM “The loop counters are: $(Loop), $(Loop10) and $(Loop25).”
END_LOOP produce the following output:
385
