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 memory calculation for multiple sweep integration runs #1728

Merged
merged 7 commits into from
May 27, 2021
Merged

Conversation

graeme-winter
Copy link
Contributor

Need to select the reflections for each experiment, not use all reflections for each image set. Fixes #1727.

Need to select the reflections for each experiment, not use all reflections for
each image set. Fixes #1727.
Copy link
Contributor

@jbeilstenedmands jbeilstenedmands left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change makes sense for the bug, thanks for fixing.

I thought it would be useful to start using the experiment identifier selection method, even though your selection wasn't wrong. I haven't verified this extra change on the data in question but I'm hoping it's trivial for you to do that?

@graeme-winter
Copy link
Contributor Author

@jbeilstenedmands testing

i.e. more than one experiment belonging to an imageset, one should
select all reflections belonging to that imageset for the memory
calculation.
@jbeilstenedmands
Copy link
Contributor

jbeilstenedmands commented May 26, 2021

Having thought about this further, I think the proposed change set would not have correctly handled multi-lattice data, where there are several reflection tables associated with the imageset, but which get processed as one 'block' of data for integration (the memory requirement would have been underestimated). So I've updated to handle this too.

@codecov
Copy link

codecov bot commented May 26, 2021

Codecov Report

Merging #1728 (3c98879) into main (802c9d6) will increase coverage by 4.44%.
The diff coverage is 83.28%.

@@            Coverage Diff             @@
##             main    #1728      +/-   ##
==========================================
+ Coverage   66.65%   71.09%   +4.44%     
==========================================
  Files         615      868     +253     
  Lines       68872    92399   +23527     
  Branches     9572    11799    +2227     
==========================================
+ Hits        45905    65694   +19789     
- Misses      21042    24616    +3574     
- Partials     1925     2089     +164     

@graeme-winter
Copy link
Contributor Author

Checking again following latest updates

@ndevenish could be good to get this merged if looks OK to everyone

@graeme-winter
Copy link
Contributor Author

I note there are now a lot of test failures in here 🤔

@jbeilstenedmands
Copy link
Contributor

Oh, this is probably because a lot of the test data won't have any identifiers set. Let me think about this.

@graeme-winter
Copy link
Contributor Author

Oh, this is probably because a lot of the test data won't have any identifiers set. Let me think about this.

Ah that makes some sense - indicates that we should probably update the test data but also a quick hasattr workaround would probably do it, and fall back to the original enumeration?

jbeilstenedmands and others added 2 commits May 27, 2021 11:31
Co-authored-by: Markus Gerstel <2102431+Anthchirp@users.noreply.github.com>
@ndevenish ndevenish merged commit acafa6c into main May 27, 2021
@ndevenish ndevenish deleted the fix-1727 branch May 27, 2021 14:06
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.

dials.integrate fails if > 1 scan and later scans longer than earlier
5 participants