Skip to content

Fixed ConfigureHeadstage64OpticalStimulator properties#563

Open
bparks13 wants to merge 1 commit intomainfrom
fix-hs64-opto-properties
Open

Fixed ConfigureHeadstage64OpticalStimulator properties#563
bparks13 wants to merge 1 commit intomainfrom
fix-hs64-opto-properties

Conversation

@bparks13
Copy link
Member

@bparks13 bparks13 commented Jan 12, 2026

The pulse frequency was sometimes indicated as pulse period and other times as frequency with bad results.

This PR was pulled from PR #529 as it is not tied to the firmware updates but is a useful addition to the next release.

image

Note that the labels and scales are the incorrect units; that is fixed in a separate PR, #562. What I am showing here is that the Pulse Freq. [Hz] label is now correctly applied on the PulsesPerSecond property of the optical stimulator.

Fixes #542

- The pulse frequency was sometimes indicated as pulse period and other
  times as frequency with bad results
@bparks13 bparks13 added this to the 0.7.0 milestone Jan 12, 2026
@bparks13 bparks13 requested a review from jonnew January 12, 2026 21:10
@bparks13 bparks13 self-assigned this Jan 12, 2026
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.

Headstage64 Optical Stimulator: Standardize naming between GUI and Configure node

2 participants