Plz1004wh pulse sequence feature

[cmgriffin]

Adds the ability to configure and trigger fast sequences for the Kikusui_PLZ1004WH class. I have been using this for a few months on the bench so most of the bugs have been resolved. Some improvements are still possible but I would like to allow colleagues to start using it without needing to switch to my fork.

New Attributes

This is a simple dataclass that captures the properties of a sequence step, current and trigger in the case of the Kikusui fast sequence
SequenceStep

New Methods

Configure an arbitrary sequence of load current values
def configure_sequence(self,steps: list["Kikusui_PLZ1004WH.SequenceStep"], current_range: str = "HIGH", step_size: float = 1e-3, initialize: bool = True)

Run a sequence that has been defined
def run_sequence(self)

Configure a sequence of load current values that form a pulse
This is essentially a helper function that creates a pulse sequence then calls configure_sequence to send it to the load
def configure_pulse_seqeunce(self, pulse_current: float, pulse_width: float, trig_delay: float, step_size: float = 1e-3, initial_idle_time: float = 10e-3, idle_current: float = 0.0, current_range: str = "HIGH", keep_load_on: bool = False)

[AnnaGiasson]

Looks good, I see no issues with it.
I like the way you structured things, I feel like this should be good for stepped current waveforms, but might be a little annoying to use for ramping. You can always do it with a bit more logic outside the class though. Did you consider an implementation where you specify an array of currents and a fixed sample rate?

Also, learned itertools.batched is a thing; looks like it was added in 3.12. That's a nice one to remember, I've definitely had to implement that with slicing before.

[cmgriffin]

Thanks!

Did you consider an implementation where you specify an array of currents and a fixed sample rate?

With the fast load sequence for the Kik loads it is a fixed sample rate. Each step in the sequence has a current level and optional trigger pulse so that's the way I structured the sequence you feed into configure_sequence. Something that could be done is to allow configure_sequence to take either list["Kikusui_PLZ1004WH.SequenceStep"] or list[float] which would simplify it where the trigger pulse is not needed. configure_pulse_seqeunce is very much just a wrapper for configure_sequence that could be implemented externally but I figured it was frequently used enough to add it to the class.

Also, learned itertools.batched is a thing; looks like it was added in 3.12. That's a nice one to remember, I've definitely had to implement that with slicing before.

I actually didn't realize itertools.batched was only added in 3.12 so that kind of kills earlier version compatibility. I'm fine with keeping it as is and making the min version 3.12 though if you are.