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

dials.integrate d_min= should be obvious #2650

Open
graeme-winter opened this issue Apr 23, 2024 · 2 comments
Open

dials.integrate d_min= should be obvious #2650

graeme-winter opened this issue Apr 23, 2024 · 2 comments
Assignees

Comments

@graeme-winter
Copy link
Contributor

i.e.

silver-surfer work :( $ dials.integrate refined.* d_min=2.0
Sorry: Ambiguous parameter definition: d_min = 2.0
Best matches:
  profile.ellipsoid.prediction.d_min
  prediction.d_min
  significance_filter.d_min

it is obvious to me I want to predict to 2.0Å

@graeme-winter
Copy link
Contributor Author

Suspect that the collision here is because there are d_min defined all over the place with similar expert_level values without any centralised idea of which one is the default.

The only one which is mentioned in the main command_line/integrate.py script is the prediction.d_min one so will bump the expert level of the others as soon as I can find them

@graeme-winter graeme-winter self-assigned this Apr 23, 2024
@graeme-winter
Copy link
Contributor Author

OK, looks like the others are brought in from e.g. ssx_integrate

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