OOF2: The Manual
HKL (HKLreader) |
||
|---|---|---|
|
6.5.2. Subclasses |  |
Name
HKL (HKLreader) — HKL channel text file
Synopsis
HKLreader()
Description
This OrientMapReader reads data
files produced by HKL[36] 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. If this HKL reader does
not work, try using GenericReader
instead.
The HKL data file is expected to look like this. Items in bold are
keywords that OOF2 expects to find. [37]
Words in angle
brackets (like <this>) describe numbers that
OOF2 that oof2 will read.
[Header lines above XCells are ignored] XCells <number of cells in the x direction> YCells <number of cells in the y direction> XStep <step size in the x direction> YStep <step size in the y direction> [More header lines that are ignored] Phase [more column names, also ignored] <phase> <x> <y> [ignored] [ignored] <Euler angles> [ignored...]
The last line is repeated for each data point. There should be
XCells*YCells data lines. The Euler angle data is
three columns containing the Bunge
angles phi1, theta, and
phi2 in that order.
The first column of the data section contains phase information in
the form of an integer. Each pixel will be added to a pixel
group named Phase_X, where
X is the phase number from the data file.
![[Warning]](IMAGES/warning.png) |
Warning |
|---|---|
|
Please see the warning about how orientation data is interpreted. |
[36] This interface between HKL files and OOF2 was created at the request of OOF2 users and does not represent an endorsement by NIST.
[37]
OOF2 isn't actually paying much attention to the keywords. It
assumes that they're in the order given, and it doesn't bother
to check that YCells comes after
XCells, for example.
|
|
 |
|
Grid Points (GridSampleSet)
|
 |
HSVAColor (HSVAColor) |