The Run Definition Entry

There are 17 run definitions allocated in the database.dat file for the 17 possible runs that can be defined in the Collect tab in BLU-ICE.

An entry for a Run definition should be in the following generic format:

Line 1:runName
Line 2:8
Line 3:runStatus nextFrame runLabel fileroot directory startFrameLabel axisMotor startAngle endAngle delta wedgeSize exposureTime distance numEnergy energy1 energy2 energy3 energy4 energy5 modeIndex inverseOn

• The runName is usually run0 through run16.

• The runStatus can be collecting, paused or inactive. If DCSS is stopped, a run with a status of collecting should be manually changed to inactive or paused.

• The nextFrame parameter is a positive integer that indicates how much of the run has been collected.

• The runLabel parameter is the text that appears on the tab. It also is used to generate the filename.

• The fileroot parameter is the text that is used as the root for the filename.

• The directory parameter is the directory that the user wishes to write the files into.

• The startFrameLabel parameter is a numerical value that is used as a starting point to generate a unique file name per frame.

• The axisMotor parameter is the motor name that will used in the oscillation code. Usually this will be either gonio_phi or gonio_omega.

• The startAngle parameter is the starting angle of the axisMotor for the run definition.

• The endAngle parameter is the final ending angle for the axisMotor.

• The delta parameter is the distance that the axisMotor will travel per frame.

• The wedgeSize parameter is the angular distance that the axisMotor must travel before rotating 180 degrees and collecting the frames in the inverse wedge.

• The exposureTime parameter is the amount of time each frame will be exposed. This value is the requested time, and is not the dose corrected time.

• The distance parameter is the position for detector_z for each frame in the run.

• The numEnergy parameter is number of energy values that will be used during the collection of the run. This parameter should never exceed 5, as there are only 5 energy values that may be defined in a single run. A zero in this position would also be bad.

• The energy1...energy5 parameters are the values for energy that will be used.

• The modeIndex parameter is the detector mode in an integer format. This parameter can have different meanings depending on the detector type being used. For example, detector mode 0 for a MAR345 is different than detector mode 0 for a CCD.

• The inverseOn parameter is a boolean value (0=FALSE or 1=TRUE) indicating whether or not the inverse wedge should be collected or not.