Skip to content

Added new functionality to ds8r class #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

timnaher
Copy link

Hello,

We have recently used your package to control the DS8R stimulator, and we'd like to thank you for developing it!

In our setup, it was necessary to update the stimulation parameters on the device without immediately sending a pulse. To accommodate this requirement, we have rewritten your DS8R class and separated the functionality into distinct methods:

upload_parameters(): This method uploads the configured parameters to the DS8R device without triggering a pulse. It allows users to adjust settings safely and review them before activation.

trigger_pulse(): This method triggers a pulse on the DS8R device using the current settings. Separating this action from parameter uploading provides greater control over when pulses are sent, which is crucial for precise experimental timing.

Additionally, we have implemented a get_state() method that addresses the issue reported in Issue #3 . This method retrieves the current configuration of the DS8R device. The state can either be printed for immediate inspection or returned as a dictionary, which can then be easily saved to a CSV file or used for logging and analysis.

New Functionality Highlights:

  1. Parameter Management: By separating parameter uploading and pulse triggering, users can now modify stimulation parameters without causing unintended pulses. This enhances safety and flexibility in experimental protocols.

  2. State Retrieval: The get_state() method enables users to query the device for its current settings. This is particularly useful for verifying configurations, savind configurations (Issue Retrieving Measurement Panel Information #3), debugging, and ensuring reproducibility of experiments.

Let me know what you think! :)

All the best,
Tim

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant