EDF files contain one or more sets of data blocks consisting of an ASCII (characters 1-127) readable header and binary data. The header consists of keyword-value pairs. The header contains only ASCII text and is therefore easily readable. Nevertheless a dictionary is required to make full use of its information. It is not recommended to change the header manually with a text editor because it could change its fixed block length or corrupt the whole data file.

The header must start by a line feed '\n' and an opening curly brace '{'and must end after a closing curly braze '}' followed by a line feed '\n'. Files with similar but other start and stop patterns are not considered in this document.

Keywords are not case sensitive. A keyword is always followed by an equal sign that separates it from its value. Each value is terminated by a semicolon ';'.Values are trimmed, i.e. leading and trailing white space is removed. A single leading and a single trailing double prime (") is removed.

Important: An ASCII-zero('\0') is NEVER allowed inside a header, because it is used as an emergency stop if the header end is missing. Curly-braces and semicolons are not allowed inside a header and therefore also neither in keywords nor in values because they are used as control characters. Escape sequences starting with a backslash must be used instead ("\(" for "{", "\)" for "}", "\:" for ";" "\\" for "\" and "\l" for a new line (lf or cr/lf depending on the operating system), see section Backslash escape sequences).

For convenience, the header length is limited to multiples of 512 bytes (including start and end pattern). A cr/lf is inserted after each semicolon following each keyword-value pair since it allows the header section to be viewed with standard system utilities on a very wide range of operating systems.. cr´s and lf´s are generally ignored in values but they should not be used inside numbers.

The maximum significant length of a header value is 64 (MaxKeyLen) characters. Keywords are not case sensitive and white spaces are removed.

The maximum significant length of a header value is 512 characters (MaxValLen). String values should not exceed 256 characters (counting also backslash escape sequences (String Value) and final zero('\0') in the output string). Too long header values are truncated.

A string value is a sequence of ASCII characters that does not contain curly braces or a semicolon. These characters are expressed by backslash escape sequences. Carriage returns ('\r') and line feeds ('\n') are ignored. If the string value contains a backslash followed by an l ('\' 'l') it is translated to a line feed.

Backslash escape sequences

A single '\' at the end of a string is ignored.

Decimal number with or without a sign (+|-), example +1234567890. Currently only long integer values are used.

A decimal number with or without a sign (+|-), with a point ('.') as decimal separator and an 'e' as decimal exponent separator, example: -1.234e+2 for -123.4.

A Double Float Value can be followed by an underscore and a unit: <value>_<unit>, e.g. 32.5_deg. The following units can be used:

The form <a>_<b> corresponds internally to an immediate multiplication of <a> with <b>, e.g 2_deg corresponds to the multiplication of 2* pi/180 and 2_rad and 2_m to the multiplication 2*1. Currently only double float values and double float values with a unit are used.

Time values should be written in the following subset of the ISO time notation (YYYY = year, MM: month, DD: day, hh: hour (0-24), mm: minute (0-60), ss: seconds (0-61), ssssss: microseconds ([] optional)):

1. YYYY-MM-DD hh:mm:ss[.ssssss]

Example: "1998-01-02 12:34:56.000000" for 02-Jan-1998 12:34:56.

This keyword shows whether the more significant data bytes of a single data element are stored before or after the less significant data bytes.

Values

HighByteFirst (default), LowByteFirst

The binary data are stored in big endian format, e.g. the two byte integer value 1 is stored in two subsequent bytes as 0x00 0x01 ("Motorola type").

The binary data are stored in little endian format, e.g. the two byte integer value 1 is stored in two subsequent bytes as 0x01 0x00 ("Intel type").

Default

HighByteFirst

Description

This keyword describes the compression type of the binary data.

Remark: It should be distinguished from other types of compressions that are applied to specific data (e.g. 2d data) and that can only be applied after endian correction and reoordering. The latter might be called RasterDataCompression (proposal).

Values

None (default)

No compression

Description

The data type of each data element. It defines type and size of data elements. 16 data type values are currently defined. Not all data types are in use (see Tab. 3:). Aliases are used for backward compatibility.

Values

Unsigned8, Signed8, Unsigned16, Signed16, Unsigned32, Signed32, Unsigned64, Signed64, FloatIEEE32, DoubleIEEE64, UnAssigned, UnAssigned, FloatVAX32, DoubleVAX64, FloatConvex32, DoubleConvex64

Aliases

UnsignedByte, SignedByte, UnsignedShort, SignedShort, UnsignedInteger, SignedInteger, Unsigned64, Signed64, FloatValue, DoubleValue, UnAssigned, UnAssigned, FloatVAX32, DoubleVAX64, FloatConvex32, DoubleConvex64

Version

2.20

Description

DataValueOffset is used to shift the value range of a short integer data type (1 or 2 bytes) inside the value range of long integer values (machine dependend, usually at least 4 bytes). The actual data value is calculated from the binary data by the following transformation (c-type notation):

1. DataType Value;
2. long DataValueOffset;
3. Value = (DataType) ( (long) Data + (long) DataValueOffset );
4. Value = (float) Data + (float) (long) DataValueOffset ;
5. Value = (double) Data + (double) (long) DataValueOffset ;

The offset is added at the very end, after endian correction and binary decompression. The result must lie inside the value range of the target data type, otherwise the results are set to the nearest value of that data type.

Only for completeness, DataValueOffset is also defined for floating point data types (equations (5) and (6)).

Values

Long Integer Value

Default

0

Keys are indexed with an underscore followed by a number, e.g."Dim_3" for the array length Dim in direction 3. Keywords ending with an underscore followed by a number are automatically interpreted as a coordinate number and must not be used for other purposes, e.g. for other indexed data, like parameters of a multi channel counter.

Description

The keys Dim_1 to Dim_(n) are used to describe an n-dimensional raster array. Dim_(n) is the number of array elements in dimension n, where n is a positive integer larger than zero. DataRasterConfiguration defines the order of the array elements in the linear data buffer and Dim_(n) the number of array elements in direction n. If Dim_(J) is found in the header, but not Dim_(J+1) the array has the dimension J. The default for Dim_1 is zero, for all others 1. This allows to read the data array always as a n-dimensional array, e.g. to read a m-dimensional array A[Dim_1, ..., Dim_(m)] as a n-dimensional array A[Dim_1, ..., Dim_(m),1, 1, ..., 1] by setting the higher indizes to 1 or by shortening a m-dimensional array to its first n-dimensions. The values of the key DataRasterConfiguration are defined in such a way that this is easily possible.

One dimensional data can be stored in two dimensional arrays with Dim_2 = 1.

Values

Positive integer values (currently limited to Long Integer Value)

Default

The default for Dim_1 is 0, for all others 1.

Description

The data raster configuration describes the storage order of array elements in a binary data buffer. The data raster configuration is 1 when a change in a lower index corresponds to a smaller distance between corresponding data elements in the stored data. In other words: "a smaller index runs faster". The default data raster configuration is 1. DataRasterConfiguration is only used to convert between different ways of data storage and not to convert between different coordinate systems. In the second case all indexed keys (keys with an underscore and a number) must be reordered in a similar way as the indices, e.g. when the coordinates are swapped. This must be done in a later step because it requires specific knowledge about the specific coordinate sytem and its description. The corresponding key is RasterOrientation. It is defined similar to DataRasterConfiguration.

The data raster configuration of an N-dimensional stored array is defined recursively and has a value between 1 and 2^N*N! For example, the elements of a one-dimensional array can either be stored in ascending or in descending order. In the first case the r data raster configuration is 1 in the latter case 2.

In the two dimensional case the number of possible data raster configurations is 8. The two first cases are identical to the one dimensional case, only a second index is added after the first index. In the following two cases the storage direction of the second index is inversed. In the four last cases the data elements of the second index appear faster than the data elements of the first index.

The actual data raster configuration of an N-dimensional data array is given by an N-tupel of indices that corresponds to the order from fast to slow in which the data elements are stored, with a negative sign if the direction is inverted. When the second index is the fastest and the direction of the first index is inverted the corresponding tupel would be: (2,-1). This is data raster configuration number 6 (see following figure). The data raster configuration number and the n-tupel are equivalent.

1. Data raster configurations for N=2 (two-dimensional image).

Values

Long Integer Values from 1 to A(N)=2^N * N! where N is the dimension. Currently only long integer value are used. For N>9 the number of data raster configurations is larger than the value range of long integers. In these cases only data raster configurations from 1 to 2^9*9! are possible.

Default

1

RasterOrientation

Description

The keyword RasterOrientation correlates array indices and geometrical coordinates (see Fig. 2:). When data is swapped between different raster orientations all geometrical parameters, like dimension, offset, pixel size and center must also be swapped.

This concept can be extended to more than 2 dimensions.

It should be noted that in the cases 5 to 8 the order of the coordinates are swapped and that the array dimensions must be swapped in the same way. Data with a horizontal dimension 500 and a vertical dimension 600 in raster orientation 1 to 4 have a horizontal dimension of 600 and a vertical dimension of 500 after swapping to raster orientation 5 to 8. Dim_1, Dim_2 and all other index dependend parameters must be changed correspondingly.

Values

Long Integer Values from 1 to A(N)=2^N * N! where N is the dimension.

Default

1



2. Raster Orientations for N=2 (two-dimensional image). Raster orientation number 1 is used as reference. It is defined as the orientation where the geometrical origin of the image is at the lower left corner, where index 1 corresponds to the horizontal coordinate (x_1) and where index 2 corresponds to the vertical coordinate (x_2). All other orientations are derived from orientation 1 by swapping and exchanging the coordinates. In raster orientation 5 index 1 corresponds to the vertical and index 2 to the horizontal coordinate.

Pixel Coordinates

The pixel (or data) coordinate along each direction is expressed by a float type number rather than an integer pixel number. The coordinates start with p0=0.0 at the lower edge of the first pixel (with pixel number 1) and end at the upper edge of pixel number n with the coordinate n. Read access to coordinates outside these limits should not cause an error but should return a dummy values as result. Write access to these coordinates will be ignored.



3. Pixel coordinates

The geometry is only defined for two dimensional scattering data. One dimensional data can be represented by setting the second index to 1.

1. Two dimensional detector coordinate system. The detector is seen from the sample.

Currently the following reference system are defined. All reference systems are defined for the same data set.

The simplest description is ARRAY. It uses only the pixel coordinates without any additional keyword.

The standard coordinate system is the IMAGE coordinate system. It consist of the ARRAY coordinates plus an offset.

CENTER coordinates consist of IMAGE coordinates minus the center.

REGION coordinates consist of IMAGE coordinates multiplied with the binning size.

REAL coordinates consist of IMAGE coordinates multiplied with the pixel size.

NORMAL coordinates consist of CENTER coordinates multiplied by the pixel size.

In the SAXS coordinate system the coordinates are oriented around a center. The distance from the center is given by tan(2Theta)/(WaveLength/WaveLength0), where WaveLength0=1e-9 has been chosen for convenience. For small 2-theta angles the resulting coordinate can be approximated by s=2sin(Theta)/WaveLength [nm], where s is the scattering vector in nanometers. At large scattering angles this coordinate system is still exact, but the coordinates cannot be interpreted directly as scattering vectors. The tan(2*Theta) must be converted into 2*sin(Theta).

The SAXS coordinate system allows the (exact) combination of scattering data from different detectors (small and wide angle), which are mounted perpendicular to the primary beam. Or from the same detector placed at different distances from the sample.

1. SAXS coordinate s = normal coordinate/sample distance ´ (WaveLength0/WaveLength)

Scattering patterns on detectors which are mounted under different angles with respect to the primary beam must be projected into the reciprocal space before they can be combined. This transformation will be called WAXS projection. The transformation requires three additional parameters:

2. DetectorRotation_1, DetectorRotation_2, DetectorRotation_3.

WAXS projections are independent of the wavelength, the sample distance and the detector rotations. WAXS projections of different detectors or detector positions can be superposed using SAXS coordinates.

Binning

A binning of the regular raster array by an integer factor B (1,2, ...) in one direction leads to the following parameter transformations:

3. 

The detector data is described by the pixel size p [m], an offset [pixel] and a center coordinate. Because the coordinate system was chosen in such a way that p0=0.0 (see Fig. 3:), the transformation of the offset simplifies to:

4. 

The principal SAXS geometry is shown in Fig. 5:. The data is described with an origin in the lower left corner. The detector is seen from the sample ("with the beam"). The data can be treated in one of the reference systems that are shown in Eq. (7).

If possible the same base unit is used for parameters of the same physical quantity, i.e.

It is possible to add explicitely one of the defined units to some type of values (see Double Float Value with Unit). This does not change the default unit that is used when no unit is given explicitly.

Description

Describes the version of the definitions

Values

current version 2.4

Default

0

Description

Offset of coordinate 1 and 2 of the data array as shown in Fig. 4:

Unit

array coordinate (pixel)

Value

Double Float Value

Default

0.0, 0.0

Description

Binning sizes of coordinate 1 and 2. BSize_1 and BSize_2 are pixel sizes that are measured relative to the pixel size of the original image. BSize_1 and BSize_2 are used alternativelely to pixel size to combine differently binned images as long as real pixel sizes are not known. They are used to calculate Region coordinates.

Unit

image coordinate

Value

Double Float Value

Default

1.0

Description

Pixel size of coordinate 1 and 2 of the data array as shown in Fig. 4:

Default Unit

meter

Value

Double Float Value with Unit

Default

no default

Description

Coordinate 1 and 2 of the normal incidence point of the beam on the detector as shown in Fig. 5: If the detector surface is perpendicular to the beam Center_1 and Center_2 are identical to the point where the primar beam would hit the detector.

Unit

image coordinate (pixel)

Value

Double Float Value

Default

no default

Description

Monochromatic wavelength of the beam.

Default Unit

meter

Value

Double Float Value with Unit

Default

no default

Description

Distance between the sample and the normal incidence point (Center_1, Center_2) of the beam on the detector.

Default Unit

meter

Value

Double Float Value with Unit

Default

no default

Description

Rotation of the detector surface normal relative to the surface normal of the standard detector which is antiparallel to the primary beam. The detector normal at the point of normal incidence (Center_1, Center_2) crosses the sample at SampleDistance.

The rotations are done in counter-clockwise direction around the axes of the unrotated NORMAL coordinate system. The rotations are done in ascending order: DetectorRotation_1 around axis 1, DetectorRotation_2 around axis 2 and DetectorRotation_3 around axis 3. This can be generalized to N dimensions.

Default Unit

The default unit is radian.

radian

Value

Double Float Value with Unit

Default

0

Example

DetectorRotation_1 = 0_deg ;

DetectorRotation_2 = 32.5_deg ;

DetectorRotation_3 = 0_deg ;

In analogy to detector rotations sample rotations are defined by three sample rotations: SampleRotation_1, SampleRotation_2 and SampleRotation_3.

Default Unit

The default unit is radian.

radian

Value

Double Float Value with Unit

Default

0

Example

SampleRotation_1 = 5.576_deg ;

SampleRotation_2 = 23.233_deg ;

SampleRotation_3 = 8.973_deg ;

Description

Currently the following projection types are defined:

Saxs: Scattering pattern that is observed on a plane detector surface as described below (SAXS Geometry). The detector can be rotated. The specific keywords are: Offset_1, Offset_2, PSize_1, PSize_2, Center_1, Center_2, SampleDistance, WaveLength, DetectorRotation_1, DetectorRotation_2, DetectorRotation_3. Pixel distances di on a Saxs projection are proportional to distances dx in the laboratory:

dx = di * PSize

Waxs: Projection of a Saxs type pattern to the Ewald-sphere, currently only to a plane that is perpendicular to the primary beam. Rotations to describe inclined geometries may be defined later. Detector rotations cannot be used. The specific keywords are: Offset_1, Offset_2, PSize_1, PSize_2, Center_1, Center_2, SampleDistance, WaveLength. Pixel distances di on a Waxs projection are proportional to distances ds in reciprocal space (WaveLength0=1e-9, s=2*sin(Theta)*(WaveLength0/WaveLength):

ds = di * (PSize/SampleDistance) * (WaveLength0/WaveLength)

Value

ProjectionType Value: Saxs, Waxs

Default

Saxs

Description

A title of the data block.

Value

String Value with escape sequences (to avoid curly braces and semicolons, see paragraph String Value). Strings longer than MaxValLen (currently 512) are truncated. There are still some subroutines which can only pass 255 characters.

Default

no default

Description

Time at start of the exposure, like 2001-11-25 10:25:03.654321

Value

Time Value

Default

no default

Description

A dummy is a value that represents an invalid data point. Zero (0.0) can never be used as a dummy value. All values between Dummy-DDummy and Dummy+DDummy are taken as invalid data points. If -DDummy < Dummy < +DDummy no dummy value is defined.

Value

Double Float Value

Default

0.0 (no dummy)

Description

Radius around Dummy to represent a dummy value.

Value

positive Double Float Value

Default

max(0.1, 1e-4 * Dummy)

The following keywords have been defined ad hoc for immediate use at the beamlines ID01 and ID02. They are only used in conversion routines of the form saxs_norm... which convert the raw data into the standard representation.

All keywords ending with "Info" contain a free format string value about the corresponding item.

Description

Info string about detector

Value

String Value

Default

no default

Description

Info string about the experiment in general

Value

String Value

Default

no default

Description

Info string about machine status or setup

Value

String Value

Default

no default

Description

Info string about optical setup

Value

String Value

Default

no default

Description

Info string about the proposal

Value

String Value

Default

no default

Description

Info string about the station

Value

String Value

Default

no default

Description

A general description of the experiment, should be replaced by the keyword ExperimentInfo

Value

String Value

Default

no default

Keywords starting with "Detector" are used to describe detector properties.

Description

The position of the detector on the optical bench, starting with 0.0 a the end stop close to the sample. The distance between sample and detector is calculated from this by adding a constant.

Value

Double Float Value

Default

no default

Description

Name of the detector (currently free format)

Value

String Value

Default

no default

A 32 channel scaler is used to count calibration data during each exposure (incoming photons, transmitted photons, exposure time, anode couts). All keywords starting with "HS32" are related to the 32 channel scaler.

A scaler value is calculated by

1. ScalerValue = (ScalerCounts - ScalerZero * TimerValue) * ScalerFactor

ScalerZero is used to subtract an offset from a signal of a voltage to frequency converter. The units are as follows: ScalerCounts [counts], ScalerZero [counts/s], TimerValue [s], ScalerFactor [<unit>/counts], where <unit> stands for the physical unit that is measured by the scaler. The keywords for ScalerCounts, ScalerZero and ScalerFactor are shown below.

At least one scaler must be fed with a constant frequency, e.g. 1MHz, and must be used as a timer. The timer value is calculated by

2. TimerValue = TimerCounts * TimerFactor

The units are as follows: TimerValue [s], TimerCounts [counts], TimerFactor [s/counts]. The scaler that is actually used as timer is given by the keyword "HSTime" (see below).

HS32Len

Description

Number of scalers, from 1 to HS32Len <= 32

Value

Long Integer Value

Default

32

HS32C<nn>

Description

ScalerCounts (see eq. (11))

Syntax

All keywords starting with HS32C... are followed by a two digit channel number (HS32C01, HS32C02, ..., HS32C10, ...). The maximum scaler number is given by HS32Len.

Value

Double Float Value

Default

no default

HS32N<nn>

Description

The name of the corresponding scaler

Syntax

All keywords starting with HS32S... are followed by a two digit channel number (HS32S01, HS32S02, ..., HS32S10, ...). The maximum scaler number is given by HS32Len.

Value

String Value

Default

no default

HS32Z<nn>

Description

ScalerZero (see eq. (11)). The zero value of the scaler.

Syntax

All keywords starting with HS32Z... are followed by a two digit channel number (HS32Z01, HS32Z02, ..., HS32Z10, ...). The maximum scaler number is given by HS32Len.

Value

Double Float Value

Default

no default

HS32F<nn>

Description

ScalerFactor (see eq. (11)). The multiplication factor for the corresponding scaler.

Syntax

All keywords starting with HS32F... are followed by a two digit scaler number (HS32F01, HS32F02, ..., HS32F10, ...). The maximum scaler number is given by HS32Len.

Value

Double Float Value

Default

no default

HS32Depth

Description

Double float value that shows the dynamics of the scaler counts. The multi channel scaler has only a dynamics of 24 bits. With an input frequency of 1MHz the counter gets an overflow after approximately 16 seconds. To allow longer counting times the counts of the multi channel scaler are accumulated externally in software. The dynamics of the software counters after k=0, 1, 2, etc. external accumulations is calculated with

3. HS32Depth = (ln(k+1)/ln(2.0)) + 24.0

With HS32Depth the maximum scaler count is given by

4. max_count = exp(ln(2)* HS32Depth)

Value

Double Float Value

Default

24.0

Default

no default

Binary Data Keywords

All keywords starting with HM (Histogramming Memory) are related to the binary data which were originally data from a histogramming memory for a multiwire proportional chamber.

HMFrame

Description

Frame number of the binary data in HMFile, starting with 1

Value

Long Integer Value

Default

no default

HMFile

Description

File name and path of the binary file that was originally created by the acquisition program.

Value

String Value

Default

no default

HMStartTime

Description

Absolute start time of the experiment (currently still in unix date notation)

Value

Time Value

Default

no default

HMDeltaTime

Description

Relative start time in seconds of the exposure of this image relative to the absolute start time of the experiment (see Default

no default

HMDeltaTime

).

Value

Double Float Value

Default

no default

Keywords to Assign Scaler Numbers to Incoming Photons, Transmitted Photons, Anode Counts and Exposure Time

The following keywords assign scalers to specific measurements. Each value can be measured by a primary and a secondary (alternative) scaler. If a scaler is not defined or used the value after the keyword is 0.

The input frequency of the secondary scaler must be a divided frequency of the primary scaler. The calibration factors and zero values must be correctly set for both scalers.

If an alternative scaler exists it is checked for an overflow of the primary scaler. The maximum allowed value of the primary scaler (without subtraction of the zero value) is given by

5. MaximumScalerValue' = ScalerFactor*exp(ln(2)* HS32Depth)

The scaler value without zero level subtraction (') is given by

6. ScalerValue' = ScalerFactor*ScalerCounts1
7. ScalerValueS' = ScalerFactorS*ScalerCountsS

If the scaler value of the secondary scaler (ScalerValueS') is larger than 99% of MaximumScalerValue' the value is calculated from the second scaler, otherwise from the primary scaler.

Description

Scaler number of the I0 monitor (flux before sample) (1 .. HS32Len). The I0-value is the number of photons in the primary beam during the exposure.

Unit of ScalerValue

#photons

Value

Long Integer Value

Default

0

Description

Scaler number of the alternative I0 monitor (flux before sample) (1 ... HS32Len)

Unit of ScalerValue

#photons

Value

Long Integer Value

Default

0

Description

Scaler number of the I1 monitor (flux after sample) (1 .. HS32Len)

Unit of ScalerValue

#photons

Value

Long Integer Value

Default

0

Description

Scaler number of the alternative I1 monitor (flux after sample) (1 ... HS32Len)

Unit of ScalerValue

#photons

Value

Long Integer Value

Default

0

Description

Scaler number of the anode pulse counter

Unit of ScalerValue

#counts

Value

Long Integer Value

Default

0

Description

Scaler number of the alternative anode pulse counter

Unit of ScalerValue

#counts

Value

Long Integer Value

Default

0

Description

Scaler number of the time counter

Unit of ScalerValue

seconds

Value

Long Integer Value

Default

0

Description

Scaler number of the alternative time counter

Unit of ScalerValue

seconds

Value

Long Integer Value

Default

0

2.10

Description

Name of the I0 monitor (beam intensity monitor before the sample)

Value

String Value

Default

no default

Description

Name of the I1 monitor (beam intensity monitor after the sample)

Value

String Value

Default

no default

Description

Name of the anode counts monitor

Value

String Value

Default

no default

Description

Name of the exposure time monitor

Value

String Value

Default

no default

Description

Integrated number of photons in the primary beam before the sample during the exposure.

Unit

#photons

Value

Double Float Value

Default

no default

Description

Integrated number of photons in the primary beam after the sample during the exposure. Attention, the ratio Intensity1/Intensity0 can be larger than the sample transmission if only a part of the primary beam hits the sample.

Unit

#photons

Value

Double Float Value

Default

no default

Description

Integrated number of anode counts during the exposure.

Unit

#counts

Value

Double Float Value

Default

no default

Description

Integrated exposure time

Unit

seconds

Value

Double Float Value

Default

no default

2.10

Description

Internal code of the time to digital converter for its resolution mode

Value

Long Integer Value

Default

no default

Description

TDC resolution in seconds

Unit

seconds

Value

Double Float Value

Default

no default

Description

TDC offset in seconds

Unit

seconds

Value

Double Float Value

Default

no default

Description

TDC time out in seconds

Unit

seconds

Value

Double Float Value

Default

no default

Description

Theta angle of the esrf id01 goniometer

Unit

degreeå (radian)

Value

Double Float Value

Default

no default

Description

Chi angle of the esrf id01 goniometer

Unit

degreeå (radian)

Value

Double Float Value

Default

no default

Description

Chi angle of the esrf id01 goniometer

Unit

degreeå (radian)

Value

Double Float Value

Default

no default

Description

Phi angle of the esrf id01 goniometer

Unit

degreeå (radian)

Value

Double Float Value

Default

no default

The ESRF ID01 specific keywords in the above described form are no longer in use. They are replaced by informational beamline specific keywords of the type ESRF_<IDxx>_<SpecSession>_<MotorMnemonic>. The units are defined by the acquisition program.

Value

String Value

2.30

Description

String that describes the value of the parameter <Mnemonic> in the spec session <SpecSession> at the beamline <IDxx> at the ESRF. <Mnemonic> can be the name of variables, motor or counter mnemonics.

Default

no default

Example

ESRF_ID01_PSIC_SAV = 10 ;

{

EDF_DataFormatVersion = 2.30 ;

EDF_DataBlocks = 9 ;

EDF_BlockBoundary = 512 ;

}

{

EDF_DataBlockID = 1.Image.Psd ;

EDF_BinarySize = 1048576 ;

ByteOrder = LowByteFirst ;

Center_1 = 269 ;

Center_2 = 268 ;

Compression = None ;

DataType = FloatValue ;

DDummy = 0.1 ;

Dim_1 = 512 ;

Dim_2 = 512 ;

Dummy = -1 ;

Offset_1 = 0 ;

Offset_2 = 0 ;

Psize_1 = 0.000343 ;

Psize_2 = 0.000337 ;

RasterOrientation = 1 ;

SampleDistance = 9.82514 ;

SaxsDataVersion = 1.0 ;

Title = vacuum setup ;

WaveLength = 9.90376e-11 ;

}

<binary data follows here>

{

EDF_DataBlockID = 1.Image.Psd ;

EDF_BinarySize = 1048576 ;

ByteOrder = HighByteFirst ;

Center_1 = 269 ;

Center_2 = 268 ;

Compression = None ;

DataType = UnsignedInteger ;

DetectorName = two dimensional delay line detector (IF = 176, SN = 3) ;

DetectorPosition = 9.10013 ;

Dim_1 = 512 ;

Dim_2 = 512 ;

Dummy = -1 ;

HMDeltaTime = 0.006 ;

HMFile = /scratch/data/com38/com38_001-001 ;

HMFrame = 1 ;

HMStartTime = Wed Dec 4 02:51:48 1996 ;

HS32C01 = 59807 ;

HS32C02 = 3562 ;

HS32C03 = 2228 ;

HS32C04 = 8743 ;

HS32C05 = 54374 ;

HS32C06 = 2150 ;

HS32C07 = 57630 ;

HS32C08 = 17714 ;

HS32C09 = 54374 ;

HS32C10 = 28 ;

HS32C11 = 0 ;

HS32C12 = 0 ;

HS32C13 = 726006 ;

HS32C14 = 355 ;

HS32C15 = 1.05002e+08 ;

HS32C16 = 51268 ;

HS32C17 = 0 ;

HS32C18 = 0 ;

HS32C19 = 0 ;

HS32C20 = 0 ;

HS32C21 = 0 ;

HS32C22 = 20095 ;

HS32C23 = 1.07518e+08 ;

HS32C24 = 1.07518e+08 ;

HS32C25 = 0 ;

HS32C26 = 0 ;

HS32C27 = 0 ;

HS32C28 = 0 ;

HS32C29 = 0 ;

HS32C30 = 0 ;

HS32C31 = 0 ;

HS32C32 = 0 ;

HS32Depth = 26.8074 ;

HS32F01 = 7.59e+07 ;

HS32F02 = 7.27e+07 ;

HS32F03 = 3.51228e+07 ;

HS32F04 = 4.0644e+08 ;

HS32F05 = 9.78206e+06 ;

HS32F06 = 1.05443e+11 ;

HS32F07 = 1.35616e+06 ;

HS32F08 = 3.56277e+11 ;

HS32F09 = 9.78206e+06 ;

HS32F10 = 2.00337e+10 ;

HS32F11 = 1 ;

HS32F12 = 1 ;

HS32F13 = 1 ;

HS32F14 = 2048 ;

HS32F15 = 1e-06 ;

HS32F16 = 0.002048 ;

HS32F17 = 1 ;

HS32F18 = 1 ;

HS32F19 = 1 ;

HS32F20 = 1 ;

HS32F21 = 1 ;

HS32F22 = 0.01 ;

HS32F23 = 1 ;

HS32F24 = 0.0005 ;

HS32F25 = 0 ;

HS32F26 = 0 ;

HS32F27 = 0 ;

HS32F28 = 0 ;

HS32F29 = 0 ;

HS32F30 = 0 ;

HS32F31 = 0 ;

HS32F32 = 0 ;

HS32Len = 32 ;

HS32N01 = PIN1 ;

HS32N02 = PIN2 ;

HS32N03 = PIN3 ;

HS32N04 = PIN41 ;

HS32N05 = PIN42 ;

HS32N06 = PIN5 ;

HS32N07 = PIN6 ;

HS32N08 = PIN7 ;

HS32N09 = I0 ;

HS32N10 = I02 ;

HS32N11 = I1 ;

HS32N12 = I12 ;

HS32N13 = anode ;

HS32N14 = anode2 ;

HS32N15 = time ;

HS32N16 = time2 ;

HS32N17 = bad ;

HS32N18 = bad ;

HS32N19 = bad ;

HS32N20 = bad ;

HS32N21 = bad ;

HS32N22 = LINKAM ;

HS32N23 = vfc27 ;

HS32N24 = thc2 ;

HS32N25 = 0 ;

HS32N26 = ;

HS32N27 = ;

HS32N28 = ;

HS32N29 = ;

HS32N30 = ;

HS32N31 = ;

HS32N32 = ;

HS32Z01 = 41.01 ;

HS32Z02 = 14.16 ;

HS32Z03 = 19.82 ;

HS32Z04 = 82.31 ;

HS32Z05 = 416 ;

HS32Z06 = 20.8 ;

HS32Z07 = 549.4 ;

HS32Z08 = 168.6 ;

HS32Z09 = 416 ;

HS32Z10 = 0.203125 ;

HS32Z11 = 0 ;

HS32Z12 = 0 ;

HS32Z13 = 0 ;

HS32Z14 = 0 ;

HS32Z15 = 0 ;

HS32Z16 = 0 ;

HS32Z17 = 0 ;

HS32Z18 = 0 ;

HS32Z19 = 0 ;

HS32Z20 = 0 ;

HS32Z21 = 0 ;

HS32Z22 = 20050 ;

HS32Z23 = 0 ;

HS32Z24 = -4000 ;

HS32Z25 = 0 ;

HS32Z26 = 0 ;

HS32Z27 = 0 ;

HS32Z28 = 0 ;

HS32Z29 = 0 ;

HS32Z30 = 0 ;

HS32Z31 = 0 ;

HS32Z32 = 0 ;

HSAnode = 13 ;

HSAnodeS = 14 ;

HSI0 = 5 ;

HSI0S = 10 ;

HSI1 = 7 ;

HSI1S = 0 ;

HSTime = 15 ;

HSTimeS = 16 ;

MachineInfo = " Ie=165.58mA,gap46=25.54mm,taper46= 0.00mm,gap26=20.31mm,taper26= 0.01mm" ;

Offset_1 = 0 ;

Offset_2 = 0 ;

OpticsInfo = optics ;

Psize_1 = 0.000343 ;

Psize_2 = 0.000337 ;

RasterOrientation = 1 ;

SampleDistance = 9.82514 ;

SaxsDataVersion = 1.0 ;

Size = 1048576 ;

StationInfo = id2 ;

ExperimentInfo = detector with 2.02% R14 + 20.1% C2H6 + QS Xe(Air Liquide ;

Title = vacuum setup ;

WaveLength = 9.90376e-11 ;

}