-
Notifications
You must be signed in to change notification settings - Fork 0
Comparing changes
Open a pull request
base repository: ChinlabLiCsCode/labscript
base: master
head repository: labscript-suite/labscript
compare: master
- 10 commits
- 2 files changed
- 5 contributors
Commits on Dec 2, 2025
-
Ignore PySide6 ephemeral imports from zip that linger in sys.modules as
being in the labscript-suite profile path. Implemented as a simple string filter for common component names.
Configuration menu - View commit details
-
Copy full SHA for 8c5e165 - Browse repository at this point
Copy the full SHA 8c5e165View commit details
Commits on Dec 12, 2025
-
fix: set 0 as default
max_BLACS_conn_length- Set the default value of `max_BLACS_conn_length` to 0 so that the `np.empty` always receives a valid arguement - Fixes labscript-suite#118
Configuration menu - View commit details
-
Copy full SHA for ac0c633 - Browse repository at this point
Copy the full SHA ac0c633View commit details
Commits on Jan 18, 2026
-
add attribute
BLACS_connectionto classDevice- Define the attribute `BLACS_connection` in base class `Device`, to ensure that all `Device` subclasses have this attribute. Suggested-by: @dihm
Configuration menu - View commit details
-
Copy full SHA for 32e46d9 - Browse repository at this point
Copy the full SHA 32e46d9View commit details
Commits on Feb 5, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 0248d55 - Browse repository at this point
Copy the full SHA 0248d55View commit details
Commits on Mar 16, 2026
-
Merge pull request labscript-suite#119 from YinFengQi/fix-#118
fix: set 0 as default `max_BLACS_conn_length`
Configuration menu - View commit details
-
Copy full SHA for fa22b43 - Browse repository at this point
Copy the full SHA fa22b43View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2145dbf - Browse repository at this point
Copy the full SHA 2145dbfView commit details -
Merge pull request labscript-suite#117 from dihm/pyside6_fix
Ignore PySide6 import objects in CWD when saving labscript files on compilation
Configuration menu - View commit details
-
Copy full SHA for 7a12be5 - Browse repository at this point
Copy the full SHA 7a12be5View commit details -
Merge pull request labscript-suite#121 from Json-To-String/variable-n…
…ame-bug Remove try except for variable checking in favor of string.isidentifi…
Configuration menu - View commit details
-
Copy full SHA for df53903 - Browse repository at this point
Copy the full SHA df53903View commit details
Commits on Mar 20, 2026
-
Don't have all devices have a BLACS_connection
Setting this in the base class creates ordering requirements for when subclasses call the base class `__init__` in order for their `BLACS_connection` not to be overridden. Simplify connection table string length calculation by just using variable length strings for all fields (except for the name field) Connection table reading code in `labscript_utils/connections.py`, does not rely on these being fixed-length `numpy` strings. Unless code is explicitly checking the dtype, it can't tell the difference and gets back bytestrings. There is a bug in labscript_utils/properties where code being too clever *does* (unnecessarily) check the dtype of the name field explicitly in order to be compatible with either fixed or variable-length strings, but this is done correctly and will crash on actual vlen strings. This check should be removed, but we should leave the name field fixed-length so that existing installations with the bug can still read the files created by newer labscript versions.
Configuration menu - View commit details
-
Copy full SHA for 2b8c2a2 - Browse repository at this point
Copy the full SHA 2b8c2a2View commit details -
Merge pull request labscript-suite#122 from labscript-suite/blacs-con…
…nection-bug Don't have all devices have a BLACS_connection
Configuration menu - View commit details
-
Copy full SHA for a0787c4 - Browse repository at this point
Copy the full SHA a0787c4View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...master