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

add cctbx class #60

Open
themindatlarge opened this issue Jun 12, 2024 · 1 comment · Fixed by #61
Open

add cctbx class #60

themindatlarge opened this issue Jun 12, 2024 · 1 comment · Fixed by #61

Comments

@themindatlarge
Copy link
Collaborator

No description provided.

@themindatlarge themindatlarge linked a pull request Jun 18, 2024 that will close this issue
@fredericpoitevin
Copy link
Collaborator

fredericpoitevin commented Jul 18, 2024

Reopening to discuss and try to address the following:

  • make it run at NERSC optionally.
  • automate masking?
  • automate geometry calibration
    What file format and where does cctbx expects to see a geometry file?
    Note: we have students working on improving our current automated way to optimize geometry from silver behenate; CCTBX could benefit from it for free assuming we know the answer to the question above. Our current tools could already be useful.
  • automate setup
    Daniel took care of that (in the case of S3DF, not yet NERSC) but test failed today. Database issue?
  • simplify database management
    Why do we need to ping Murali again? Could we setup a simpler SQLite thing that we manage ourselves? Every experiment will come with its own database going forward. Murali automated the process.
  • clarify and document what’s up to the beamline operator (e.g. FEE spectrometer calibration)
  • automate trials management
    I’m looking into a way to retrieve the “Sample” associated with a given run upon run start. This could be picked up for the trials? How?

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 a pull request may close this issue.

2 participants