There I uploaded things, which I do not consider core part of pyleco, but useful in the context of pyleco.
For example it includes:
GUIs for
the starter,
Datalogger,
LogLogger,
and an overview over the Components in the LECO network.
Actor/Director for a specific step motor driver
An analyzing director, which can analyze an instrument (for example pymeasure) and allows to direct an actor controlling that instrument with autocompletion, method calls, channels nested in arbitrary depth (if they are pymeasure channels)...
For example director.device.ch_1.start_measurement(5) will execute the method start_measurement of channel ch_1 of the instrument controlled by the actor.
I'm open to put this REPO under the pymeasure umbrella, but it adds requirements (for example for the motor driver) which I do not want in the pyleco core.
We could also move some things from there into pyleco itself or vice versa, if you think it good. Especially the analyzind director is a hot candidate to enter pyleco proper.
I made a pyleco-extras repository: https://github.com/BenediktBurger/pyleco-extras
There I uploaded things, which I do not consider core part of pyleco, but useful in the context of pyleco. For example it includes:
director.device.ch_1.start_measurement(5)will execute the methodstart_measurementof channelch_1of the instrument controlled by the actor.I'm open to put this REPO under the pymeasure umbrella, but it adds requirements (for example for the motor driver) which I do not want in the pyleco core. We could also move some things from there into pyleco itself or vice versa, if you think it good. Especially the analyzind director is a hot candidate to enter pyleco proper.