Feature/hardware provider architecture - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Compared with main, this branch introduces the complete ScopeOne hardware-provider and plugin architecture, including the installable ScopeOneCore SDK, DriverHost process, Micro-Manager integration, DAQ and signal-source interfaces, and the reorganized hardware/processing/tools plugin layout.
It adds NI-DAQmx, PTU file, simulated PMT raster scanning, DHM reconstruction, iSCAT processing, CUDA processing support, CPU/CUDA FFT and Gaussian filters, and example plugins. The image workflow now includes unified layer management, static and stack image import, asynchronous stack loading, gallery sessions, offline stack processing, 2D/3D surface visualization, layer duplication and renaming, colormaps, and layer-bounded slice navigation.
The branch also extends the Local API, MCP integration, Python client examples and documentation, and exposes unified layer frame-rate tracking through ScopeOneCore and the plugin SDK.