While using hardpotato for my work, I created a fork with a more streamlined CHI functionality. Essentially, I used a base class to combine all CHI techniques into one file, chi.py, that replaces the individual CHI model files. If a user wants to add a new instrument model, the user adds the model information to the ChiInfo class (instead of making a new model_name.py file). The primary benefit of this setup is that if a user adds a new technique (e.g., Chronoamperometry (CA)), that technique need only be added to the potentiostat.py and chi.py files. (In the old setup, a user must update each model_name.py file, which gets tedious and error-prone with so many CHI models.) The principles behind this redesign could also be applied to the Emstat Pico code, though I have not done so.
If you would like to view my fork and/or incorporate some of the changes, you can see it at https://github.com/D3TaLES/hardpotato.
While using hardpotato for my work, I created a fork with a more streamlined CHI functionality. Essentially, I used a base class to combine all CHI techniques into one file,
chi.py, that replaces the individual CHI model files. If a user wants to add a new instrument model, the user adds the model information to theChiInfoclass (instead of making a newmodel_name.pyfile). The primary benefit of this setup is that if a user adds a new technique (e.g., Chronoamperometry (CA)), that technique need only be added to thepotentiostat.pyandchi.pyfiles. (In the old setup, a user must update eachmodel_name.pyfile, which gets tedious and error-prone with so many CHI models.) The principles behind this redesign could also be applied to the Emstat Pico code, though I have not done so.If you would like to view my fork and/or incorporate some of the changes, you can see it at https://github.com/D3TaLES/hardpotato.