OOF2: The Manual

Name

TSL (TSLreader) — TSL .ang file (old format)

Synopsis

TSLreader(flip_x, flip_y, angle_offset)

Details

  • Base class: OrientMapReader
  • Parameters:

    flip_x
    Flip data, swapping x and -x. Type: Boolean: True or False.
    flip_y
    Flip data, swapping y and -y. Type: Boolean: True or False.
    angle_offset
    Subtract this angle (in degrees) from phi1. Type: A real number.

Description

This OrientMapReader reads data files produced by TSL (now ESAX)[46] EBSD devices. There is no guarantee that it is up to date. It was written to read files that were provided to us as examples 10 or more years ago, and is not based on any formal file specification. The TSLreader2 reader is based on a more recent example file. If the TSL readers do not work, try using GenericReader instead.

OOF2 expects the data file to start with some number of header lines that begin with #. The content of these lines is ignored, except that if one of them begins with # Column 1-3 and contains the word radians, then angle data will be assumed to be in radians instead of degrees.

After the header comes a table of data, with one line for each data point (pixel). There are ten columns of numbers, separated by white space, followed by one column of phase names. OOF2 only uses the first five columns of numbers and the phase name. The first three columns specify an orientation in Bunge angles, and the fourth and the fifth columns are the x and y coordinates of the pixel. Pixels with the same phase name will be placed into a pixel group with that name.

OOF2 only works on rectangular grids pixels. If the x values of the first two rows of data are not the same, OOF2 assumes that the data file contains a hexagonal grid, and converts it to a rectangular grid by discarding every other row.

The parameters flip_x, flip_y, and angle_offset provide some flexibility in interpreting the data file.

[Warning] Warning

Please see the warning about how orientation data is interpreted.



[46] This interface between TSL files and OOF2 was created at the request of OOF2 users and does not represent an endorsement of TSL or ESAX by NIST.