Skip to content

Commit

Permalink
Encourage moving generic devices to ophyd_async
Browse files Browse the repository at this point in the history
  • Loading branch information
DiamondJoseph committed Oct 18, 2024
1 parent 0edd8e9 commit 7d1d0cb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/reference/device-standards.rst
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Dodal is written with the philosophy that Ophyd devices should be assumed to be
should think about where to place them in the following order:

#. A device that could be used at any facility, e.g. a generic ``EpicsMotor`` or a commercial product with a
standard IOC, should go in https://github.com/bluesky/ophyd-epics-devices
standard IOC, should go in https://github.com/bluesky/ophyd-async/ or https://github.com/bluesky/ophyd-epics-devices
#. A device that may be on any beamline should go in the top level of the ``devices`` folder. If it is a quite
complex device (e.g. multiple files) it should have a folder of its own e.g. ``oav``
#. A device that is very specific to a particular beamline should go in the ``devices/ixx`` folder
Expand Down

0 comments on commit 7d1d0cb

Please sign in to comment.