You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wish I could use pyvium to grab both EIS data at different frequencies and the values of open circuit voltage measured before the experiment. Is it possible at all?
Feature Description
While setting up an EIS measurement you can select "Apply wrt OCP", a monitor time and a monitor interval. However, that information is lost if I just use Tools.get_idf_data and it can be crucial to have.
Alternative Solutions
(...)
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Thank you for bringing this up! I understand that the get_idf_data function currently does not handle OCP data and only extracts the primary data from the IDF file.
To address this, I plan to modify the get_idf_data function to optionally retrieve OCP data. For example, it could include an optional parameter like get_idf_data(idf_path, ocp=True) (or equivalent). This enhancement should provide the additional functionality you’re looking for while maintaining the current behavior as the default.
I’m already working on this and expect to have it implemented within the next week. I’ll update this thread as soon as the changes are ready for you to test.
Thanks again for your feedback—it helps us improve the library for all users!
Feature Type
Adding new functionality to pyvium
Changing existing functionality in pyvium
Removing existing functionality in pyvium
Problem Description
I wish I could use pyvium to grab both EIS data at different frequencies and the values of open circuit voltage measured before the experiment. Is it possible at all?
Feature Description
While setting up an EIS measurement you can select "Apply wrt OCP", a monitor time and a monitor interval. However, that information is lost if I just use Tools.get_idf_data and it can be crucial to have.
Alternative Solutions
(...)
Additional Context
No response
The text was updated successfully, but these errors were encountered: