Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean profile for general use #1

Open
10 tasks
tangkong opened this issue Feb 17, 2021 · 1 comment
Open
10 tasks

Clean profile for general use #1

tangkong opened this issue Feb 17, 2021 · 1 comment
Assignees

Comments

@tangkong
Copy link
Owner

Implementation is currently quite hard-coded in many places, and efforts should be made to minimize knowledge of the bluesky/ophyd/databroker stack.

Regular actions to consider:

  • Detector change
  • User changeover (user information, proposal number, file export location)
  • Operation with some subset of detectors. (profile initialization)

General issues involved in use:

  • Machine to run Bluesky from
  • Ensure access to Bluedata for mongoDB metadata server
  • User data access, databroker access patterns
  • Separate development modules from necessary modules (unnecessary detectors, plans, location files)
  • Test user directory

Documentation additions:

  • Settings for xspress3
  • Organization of instrument package, where / how to modify things if necessary.
@tangkong tangkong self-assigned this Feb 17, 2021
@tangkong
Copy link
Owner Author

tangkong commented Feb 17, 2021

Due to mongo not really allowing for granular access controls, need to consider setting up separate database for each user? (current NSLS solution). Can rely on prompt export, but gathering csv type information needs to happen post run.

  • script / function for gathering csv data, based on query

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

No branches or pull requests

1 participant