Skip to content

Conversation

@olliesilvester
Copy link
Collaborator

Part of DiamondLightSource/mx-bluesky#1200

Requires bluesky/ophyd-async#999

Instructions to reviewer on how to test:

  1. Do thing x
  2. Confirm thing y happens

Checks for reviewer

  • Would the PR title make sense to a scientist on a set of release notes
  • If a new device has been added does it follow the standards
  • If changing the API for a pre-existing device, ensure that any beamlines using this device have updated their Bluesky plans accordingly
  • Have the connection tests for the relevant beamline(s) been run via dodal connect ${BEAMLINE}

@DominicOram
Copy link
Contributor

@olliesilvester to tidy up, we'll merge w/o the mx-bluesky side. @jacob720 to review

Copy link
Contributor

@jacob720 jacob720 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, as long as those comments don't need to be done in this PR

set_log_beamline(BL)
set_utils_beamline(BL)

# TODO check jungfrau is connected here
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this still need to be done in this PR?

If this is called when already instantiated, it will return the existing object."""
file_provider = AutoIncrementFilenameProvider(filename)

# TODO find the prefixes + odin nodes
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above

@olliesilvester
Copy link
Collaborator Author

@jacob720 sorry, this is superseded by #1721. That requires a new ophyd-async release before reviewing though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants