Manual

English | 日本語

• Frame and integral acquisition
• mini_pix architecture and implementation boundaries
  • Implemented control path
  • Proposed extension path (unverified)
  • Data and control
  • Transparent gRPC frame and API mapping
• D08-W0313 individual calibration
• MiniPixCtrl public API
• Measurement results: data structure and acquisition timing
  • Acquisition result
  • SDK acquisition frames versus Python history
  • Callback and readout timing
  • State, exceptions, and threading
  • Saving
• Implementation status and API scope
  • APIs confirmed in the current implementation
  • Unimplemented or unverified functionality
  • Relationship between calibration and the Python API
• DeviceProxy integration
  • Purpose and evidence
  • Intended responsibilities
  • Interface compatibility
  • Transparent gRPC frame and API mapping
• Frequently asked questions
  • Which detector is used?
  • Why is FileDevice 0 reported?
  • Does set_threshold() accept raw THL?
  • Why does Integral return one image?
  • Are ToT values expressed in keV?
  • Is 55 fps guaranteed?
• gRPC server and local detector control
  • Verified implementation boundary
  • Intended architecture (not verified as implemented)
  • Candidate remote interface based on verified local APIs
  • Transparent gRPC frame and API mapping
• Device specifications and safety
• Image data and file formats
• Installation and runtime requirements
• PIXet Python SDK and control
• Energy measurements and spectroscopy
• Troubleshooting
  • Cannot connect
  • No physical detector found / FileDevice 0
  • setThreshold, setBias, or setTimepixClock fails
  • Acquisition fails
  • Unexpected pixel values