-
Notifications
You must be signed in to change notification settings - Fork 121
Refactor pydiscamb interface #1060
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
base: master
Are you sure you want to change the base?
Conversation
…ters to pydiscamb
/azp run |
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
/azp run Full |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run XFEL CI |
Azure Pipelines successfully started running 1 pipeline(s). |
Looks like windows has some permission error for the atom assignment file. I only test locally on linux so this slipped by. I'll look into it |
Windows tests should work now, as of viljarjf/pyDiSCaMB#36. I set up windows and macOS testing for pydiscamb as well |
/azp run Full |
Azure Pipelines successfully started running 1 pipeline(s). |
Thanks! We see the other commits passing now. We're still discussing the implementation, but we are pretty much on board with it. |
Hello!
This PR aims to make use of the existing structure factor + gradient framework in cctbx when using TAAM with pydiscamb.
I refactored the algorithm selection slightly, and added TAAM as an option. Currently, the actual implementation is in pydiscamb: https://github.com/viljarjf/pyDiSCaMB/blob/main/pydiscamb/cctbx_interface.py
I would like some input on this solution, if maybe the
gradients_taam
andfrom_scatterers_taam
classes should be in cctbx and the results classes in pydiscamb?The runtime measurement still needs to be added to the taam classes, regardless.
Extra parameters can be passed to DiSCaMB by means of a phil scope. I put this in pydiscamb, to more easily support / update the options if and when they change in DiSCaMB. The
extra
-scope is meant to allow for other algorithms in the future, with adiscamb
subscope defined in pydiscamb. Here, I also have the option to add more parameter sets for other available calculators in DiSCaMB.Happy for any input on this! I have not been able to test this much, as I'm having difficulties properly installing cctbx.