`diode_range_available` vs `possible_range` API coherency
Coherency issue:
bv.diode_range_available
vs
keithley.possible_range
I think range_available
would be preferable for auto-completion reasons.
or to have everything prefixed by available_
:
available_rates
available_ranges
...
Maybe we can also think to a global unification of API of many devices:
- for keithley
- K428 to put in common API ?
- gain / range unification ?
Wout also asked for a pint
output for keithley range (V/A)
Edited by Cyril Guilloud