Skip to content

Commit

Permalink
Updated documentation for area detectors.
Browse files Browse the repository at this point in the history
  • Loading branch information
canismarko committed Feb 12, 2025
1 parent 1236639 commit efa3ff2
Showing 1 changed file with 8 additions and 6 deletions.
14 changes: 8 additions & 6 deletions docs/topic_guides/area_detectors.rst
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ Currently supported detectors:
- Eiger 500K (:py:class:`~haven.devices.area_detector.Eiger500K`)
- Lambda (:py:class:`~haven.devices.area_detector.Lambda250K`)
- Simulated detector (:py:class:`~haven.devices.detectors.sim_detector.SimDetector`)
- Aravis cameras (:py:class:`~haven.devices.detectors.aravis.AravisDetector`)

EPICS and Ophyd do not make a distinction between area detectors and
cameras. After all, a camera is just an area detector for visible
Expand All @@ -25,9 +26,10 @@ label "area_detectors". They can be used interchangeably in plans.

.. warning::

The first time you stage the device after the IOC has been
restarted, you may receive an error about the **plugin not being
primed**. The means that the plugin does not know the size of the
image to expect since it has not seen one yet. The solution is to
open the caQtDM panels for the detector, ensure the corresponding
plugins are enabled, and then manually acquire a frame.
For threaded devices, the first time you stage the device after the
IOC has been restarted, you may receive an error about the **plugin
not being primed**. The means that the plugin does not know the
size of the image to expect since it has not seen one yet. The
solution is to open the caQtDM panels for the detector, ensure the
corresponding plugins are enabled, and then manually acquire a
frame.

0 comments on commit efa3ff2

Please sign in to comment.