channel: support recalibrating force data

[JoepVanlier]

Why this PR?
It is good to be able to recalibrate your force data.

By providing an API to do this, you basically end up with a force slice that can be treated as any other force slice (with a calibration item attached that conforms to a common API).

For instance, a recalibrated force slice can now directly be fed to the piezo tracking API (which reads from the calibration item).

Prior to implementing the new functionality, I removed some old cruftiness from the API that didn't really gel well with the new API. I left this as a separate commit.

Usage example:

  import lumicks.pylake as lk
  f = lk.File("passive_calibration.h5")
  calibration = f.force1x.calibration[1]  # Grab a calibration item for force 1x

  # Slice the data corresponding to the calibration we want to reproduce.
  calib_slice = f.force1x[calibration]

  # De-calibrate to volts using the calibration that was active before this slice.
  previous_calibration = calib_slice.calibration[0]
  calib_slice = calib_slice / previous_calibration.force_sensitivity
  calibration_params = previous_calibration.calibration_params()
  new_calibration = lk.calibrate_force(calib_slice.data, **calibration_params)
  new_calibration.plot()

  # Make a new calibration, but change the amount of blocking
  less_blocking_params = calibration_params | {"num_points_per_block": 200}
  less_blocking = lk.calibrate_force(calib_slice.data, **less_blocking_params)
  less_blocking.plot()

  # Recalibrate the force channels
  recalibrated_force1x = f.force1x.recalibrate_force(less_blocking)

[aafkevandenberg]

Very nice addition, this is much easier and cleaner way to recalibrate.

The example you mention would fit well in the force calibration docs. I guess you do that in a separate PR?

[JoepVanlier]

Very nice addition, this is much easier and cleaner way to recalibrate.

The example you mention would fit well in the force calibration docs. I guess you do that in a separate PR?

Yeah. I was considering that too, but I figure, with the big shuffle, it doesn't make a lot of sense to add it now.

However, I could rebase this one on the docs rewrite and just add it there.