x_scaler needs clarification
The x_scaler
callable should translate between the scan IDs and the scan dimension, e.g. turning 001
into 1.10 Å
.
In the example this is done with:
x_scaler = lambda x: (x + 109) / 100
However the list of x values gets accessed like this:
...
x = [x_scaler(x) for x in range(len(energies))],
which starts with index 0
, meaning the scan coordinates are shifted by 1.
I think it's important for the user to have an intuitive way of creating the x_scaler
, so this interaction takes priority.
But which way is easier for thinking about this?