Skip to main content
Ctrl+K
ophyd-async 0.13.2.dev5+g9d2016b89 documentation - Home ophyd-async 0.13.2.dev5+g9d2016b89 documentation - Home
  • Tutorials
  • How-to Guides
  • Explanations
  • Reference
  • Bluesky Project
  • GitHub
  • PyPI
  • Tutorials
  • How-to Guides
  • Explanations
  • Reference
  • Bluesky Project
  • GitHub
  • PyPI

Section Navigation

  • Architectural Decision Records
    • 1. Record architecture decisions
    • 2. Adopt python-copier-template for project structure
    • 3. Ophyd Async migration
    • 4. Repository Structure
    • 5. Respect black line length
    • 6. Procedural Device Definitions
    • 7. Sub-package Structure
    • 8. Settle on Signal Types
    • 9. Procedural vs Declarative Devices
    • 10. Decide on docstring format
    • 11. Buffer updates when using camonitor
  • Declarative vs Procedural Devices
  • Design goals and differences with ophyd sync
  • Device connection strategies
  • Devices, Signals and their Backends
  • What is the difference between step and fly scanning
  • What plan stubs will do to Devices
  • When should a device extend movable
  • Where should Device logic live?
  • Explanations

Explanations#

Explanations of how it works and why it works that way.

  • Architectural Decision Records
  • Declarative vs Procedural Devices
  • Design goals and differences with ophyd sync
  • Device connection strategies
  • Devices, Signals and their Backends
  • What is the difference between step and fly scanning
  • What plan stubs will do to Devices
  • When should a device extend movable
  • Where should Device logic live?

previous

How to store and retrieve device settings

next

Architectural Decision Records
Edit on GitHub

This Page

  • Show Source

Built with the PyData Sphinx Theme 0.16.1.