Refactor pydiscamb interface #1060
Open
+148
−138
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ters to pydiscamb
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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_taamandfrom_scatterers_taamclasses 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 adiscambsubscope 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.