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

Fix crash in symmetry code when no resolution limit #1641

Merged
merged 3 commits into from
Apr 1, 2021

Conversation

ndevenish
Copy link
Member

When no d_min could be determined this caused a TypeError in the logging systems, as

>>> "%d" % None
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: %d format: a number is required, not NoneType

@ndevenish ndevenish merged commit 00a89e1 into dials:main Apr 1, 2021
ndevenish added a commit that referenced this pull request Apr 1, 2021
In some combinations of dependencies/platform, the resolution limit
fitting appears to sometimes break, returning None. This means that
doesn't cause a TypeError via "%f" % None.
DiamondLightSource-build-server added a commit that referenced this pull request Apr 1, 2021
Features
--------

- ``dials.cosym``: Significantly faster via improved computation of functional, gradients and curvatures (#1639)
- ``dials.integrate``: Added parameter ``valid_foreground_threshold=``, to require a minimum fraction of valid pixels before profile fitting is attempted (#1640)

Bugfixes
--------

- ``dials.cosym``: Cache cases where Rij is undefined, rather than recalculating each time. This can have significant performance benefits when handling large numbers of sparse data sets. (#1634)
- ``dials.cosym``: Fix factor of 2 error when calculating target weights (#1635)
- ``dials.cosym``: Fix broken ``engine=scipy`` option (#1636)
- ``dials.integrate``: Reject reflections with a high number of invalid pixels, which were being integrated since 3.4.0. This restores better merging statistics, and prevents many reflections being incorrect profiled as zero-intensity. (#1640)
- Fix rare crash in symmetry calculations when no resolution limit could be calculated (#1641)
@ndevenish ndevenish deleted the fix_fail branch February 24, 2022 19:12
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 this pull request may close these issues.

2 participants