From 7d1d0cb75ad7bf233cf566fc91b8207fb0ca5814 Mon Sep 17 00:00:00 2001 From: "Ware, Joseph (DLSLtd,RAL,LSCI)" Date: Fri, 18 Oct 2024 12:03:16 +0100 Subject: [PATCH] Encourage moving generic devices to ophyd_async --- docs/reference/device-standards.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/device-standards.rst b/docs/reference/device-standards.rst index 21913f4873..11b170e9d8 100644 --- a/docs/reference/device-standards.rst +++ b/docs/reference/device-standards.rst @@ -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