EBSD data stored as a matrix rather than as a list
The shared base of EBSDsquare and EBSDhex. It carries the matrix layout and nothing else: id, rotations, pos and every prop are (r x c) instead of (n x 1), so the data can be handed to image processing and registration tools directly, and ebsd(i,j) addresses a scan position.
It is deliberately NOT a capability tier. Everything an EBSD can be asked to compute lives on EBSD and works on a plain list, via ebsd.lattice - a grid class only changes how the same data is stored. Anything added here must be a statement about the matrix layout; if it is a statement about the measurements, it belongs on EBSD.
Note that a grid may be rotated relative to the x/y axes and smoothly distorted - pos is stored per pixel, not derived from an origin and a spacing - so no method here may assume pos(i,j) is an axis aligned affine function of (i,j).
Derived classes
<EBSDsquare.EBSDsquare.html EBSDsquare> - pos(i,j) is affine in (i,j)
<EBSDhex.EBSDhex.html EBSDhex> - rows (or columns) are staggered by half a step, so it is
not; the (row,col) <-> lattice conversion needs the parity