Repository navigation
Drivers as the hardware extension point, Core with CUDA and ONNX, one build script - #28
Merged
Merged
Conversation
… the driver SDK boundary
…log inputs of a device in one task
…task once per change
…eresis that follows the noise
…ase stopped stream rings
…ir dylibs beside it
…and build ONNX inference into every Core
…s and CMake, and rewrite the developer guide
…imes to the README
… modules self-contained
… multi-camera configuration in its own DriverHost and reach hardware only through HardwareRuntime
…ames DriverHost removes once ScopeOne has attached
… the Semaphore.h of MMCore
… which gave two cameras of one host the same name
…e one a crashed ScopeOne left behind
… and with --clean
…which macOS lacks
…d name the SDK interfaces after devices
…eOneProvider, with the cfg label as device id
… the Cobolt 05-01 lasers
…n from the Drivers dialog and keep the Micro-Manager demo beside two ScopeOne demos
…Visual Studio environment, which sets it to its own vcpkg
…e the PMT out of them
…ages to stderr on Windows and report its exit code
…its port, and set the Jive configuration to COM17
…ror, and name the Cobolt power properties with their units
…les without reloading
…rial Port and keep Core roles consistent after device and role edits
…tofocus, split Stage into XYStage and ZStage, and move the default devices, AutoShutter and pixel size to the Core roles and calibration of the cfg
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
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.
Hardware outside Micro-Manager now goes through drivers only. Each driver runs in its own DriverHost process and sees nothing but the driver SDK and Qt Core. DAQ, PMT and a serial driver that runs JSON device descriptions (Cobolt 05-01 first) are drivers now. Native devices load from ScopeOneDevice lines of the cfg next to Micro-Manager devices. Python processing stays the other public extension point.
The CUDA and ONNX modules moved into Core, with ONNX Runtime downloaded to match CUDA. A Hardware Configuration dialog edits devices, roles, presets and light sources, and roles apply without a reload. Signal Monitor works like a scope now.
Build is one script per platform, with an installed Qt 6.8+ or vcpkg's Qt. CI and the release workflow call the same scripts.