Make run_number a metadata key in period-per-point mode & document/make it easier to add scan-specific metadata #277
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of work
run_numbera metadata key in our standardscan()plan, if in period-per-point mode andsave_runis True.mdinto most of our top-level plans (as per bluesky upstream recommendation)Ticket
Closes #152
Acceptance criteria
run_numberis a metadata key in our standardscan()plan, if in period-per-point mode andsave_runis True. Otherwise it should not be present.Documentation
Added documentation in the getting-started guide about how to add further metadata if users are not using "our" scan plan wrapper.