search

labscript-suite-temp / labscript_devices

Module containing labscript suite hardware compatibility, separate from the main programs. Device compatibility is implemented with a plugin architecture, for modularity and extensibility. Each file in this module contains a labscript device class, a BLACS tab class, a BLACS worker class and a runviewer parser class for a particular device. These implement functionality for the device which the programs in question call on when they encounter each device in user labscript code, hdf5 files, or connection tables.
0 stars 0 forks source link

No button labels on PulseBlaster_SP2_24_100_32k in BLACS #9

Closed philipstarkey closed 9 years ago

philipstarkey commented 9 years ago

Original report (archived issue) by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).

In BLACS, the buttons for the flags on the PulseBlaster_SP2_24_100_32k aren't labeled with what output device they are connected to. I forget why this is but it's something I've looked into before. It might even be sensitive to how you write your connection table. It's probably trivial but I'm creating this bug report so I don't forget about it.

philipstarkey commented 9 years ago

Original comment by Philip Starkey (Bitbucket: pstarkey, GitHub: pstarkey).

Fixed bug where any device based on PulseBlaster_No_DDS did not get labels on the front panel buttons in BLACS. This was because the change to the pseudoclock/clockline object hierarchy in labscript requires an extra method to be defined in the tab class as outputs are now more removed from the device the tab belongs to.

fixes #9

→ \<\<cset 18faff22c5bf353467dda2924fa082eb404f1eab>>