Assembly info "/ainfo" group
Since most of our raw data is assembled into either complete 2D diffraction images or
3D datacubes, it is important to keep track of all important experimental settings that were in effect
when the raw data files were recorded. Thus, the "/ainfo" group is comparable to the
adi_struct of the "/adi" group, with the difference that all tags are initialized as arrays that
contain the respective values of every single file that has been used for the assembly. Due to that the adi_struct becomes partly obsolete and is only being used for tags that are likely to have the same value for all files (e.g. lambda_meters). The "/ainfo" group as it is written to the HDF5 file consists of the following tags (Note that there might be additional parameters that are only being used whithin the I/O routines and that might differ depending on the implementation):
- The attribute ainfo_version is used to indicate to the
dm_fileio routines any changes in the structure of information
in the ainfo_group.
- file_directory contains the path to the folder where all the
files that were used for the assembly are stored. Obsolete since we
are giving full filenames in filename_array?
- filename_array contains an array of filenames of all the files
used for the assembly.
- systime_array stores the creation date and time for every file
that was used for the assembly.
- camera_x_pixelsize_m_array stores the size of camera
pixels in meters for every file used for the assembly. Obsolete since already defined
in "/adi" group?
- camera_y_pixelsize_m_array: see above. Obsolete since already defined
in "/adi" group?
- theta_x_radians_array: GMR position for each file .
- xcenter_array: location of the center of the array.
- ycenter_array: see above. (Maybe change to ycenter_offset_pixels?)
- n_frames stores the number of files that were used for the assembly. This value is entered
by the user and has to be checked carefully since it determines the size of the above arrays.
- string_length: the minimum string length required to store the longest filename, systime,
or file directory. Automatically determined in the IDL implementation. For C the user has
to define a keyword.
For information about how to read and store information from/to the "/ainfo" group, see Sec. 2.4.5 for the C implementation and Sec. 2.5.1 for the IDL implementation.
Microscope User
2008-04-30