From 9d3c97968dc42cb2d29b090a262215d61021c278 Mon Sep 17 00:00:00 2001 From: Noemi Frisina Date: Tue, 28 Apr 2026 13:11:40 +0000 Subject: [PATCH 1/4] Add a note to injecting multiple devices docs --- docs/how-to/write-plans.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/how-to/write-plans.md b/docs/how-to/write-plans.md index cba1ab4958..acec21ded1 100644 --- a/docs/how-to/write-plans.md +++ b/docs/how-to/write-plans.md @@ -42,6 +42,9 @@ Then in your plan module: :language: python ``` +> [!NOTE] +> In order for this to work, the `MyDeviceComposite` needs to be mae available to blueapi by importing it into the `planFunctions` module. + ## Injecting Metadata From f5eb2d335f50997372fed58d4e1903cf69b27efa Mon Sep 17 00:00:00 2001 From: Noemi Frisina Date: Tue, 28 Apr 2026 13:13:11 +0000 Subject: [PATCH 2/4] Actually save changes --- docs/how-to/write-plans.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to/write-plans.md b/docs/how-to/write-plans.md index acec21ded1..1f681174a1 100644 --- a/docs/how-to/write-plans.md +++ b/docs/how-to/write-plans.md @@ -43,7 +43,7 @@ Then in your plan module: ``` > [!NOTE] -> In order for this to work, the `MyDeviceComposite` needs to be mae available to blueapi by importing it into the `planFunctions` module. +> In order for this to work, the `MyDeviceComposite` needs to be mae available to blueapi by importing it into the `planFunctions` module where it's needed. ## Injecting Metadata From 20368b04782b89a47a0cf83cc7da0d9969bc3670 Mon Sep 17 00:00:00 2001 From: Noemi Frisina <54588199+noemifrisina@users.noreply.github.com> Date: Tue, 28 Apr 2026 16:28:11 +0100 Subject: [PATCH 3/4] Update docs/how-to/write-plans.md Co-authored-by: Zoheb Shaikh --- docs/how-to/write-plans.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to/write-plans.md b/docs/how-to/write-plans.md index 1f681174a1..e379b628f7 100644 --- a/docs/how-to/write-plans.md +++ b/docs/how-to/write-plans.md @@ -43,7 +43,7 @@ Then in your plan module: ``` > [!NOTE] -> In order for this to work, the `MyDeviceComposite` needs to be mae available to blueapi by importing it into the `planFunctions` module where it's needed. +> In order for this to work, the `MyDeviceComposite` needs to be made available to blueapi by importing it into the `planFunctions` module where it's needed. ## Injecting Metadata From 0d1cc5de99137bd700a79de101940a7cdcb9cde7 Mon Sep 17 00:00:00 2001 From: Noemi Frisina Date: Tue, 28 Apr 2026 15:29:18 +0000 Subject: [PATCH 4/4] Suggested addition --- docs/how-to/write-plans.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/how-to/write-plans.md b/docs/how-to/write-plans.md index e379b628f7..a25d3e128e 100644 --- a/docs/how-to/write-plans.md +++ b/docs/how-to/write-plans.md @@ -43,7 +43,7 @@ Then in your plan module: ``` > [!NOTE] -> In order for this to work, the `MyDeviceComposite` needs to be made available to blueapi by importing it into the `planFunctions` module where it's needed. +> In order for this to work, the `MyDeviceComposite` needs to be made available to blueapi by importing it into the `planFunctions` module where it's needed. Factories for the individual devices within the composite also need to be available in the relevant beamline device module. ## Injecting Metadata