-
Notifications
You must be signed in to change notification settings - Fork 3
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
Issues with reading in multiple passes #28
Comments
When we limit ourselves to an ON and an OFF pass at the same angles, and specify
followed by a CalledProcessError This happens when |
The following work-around by suggested by @kmdalton in the DIALS Slack channel seems to circumvent any problems with The workaround is:
but upon
followed by a |
on I run the following script, living in
The error message:
This appears to be the same error as above. |
The |
Could you provide a brief use example? |
Attached my script for the hemoglobin example. This works in principle. The first ~12 frames of run a have poor geometry, but that is probably unrelated to what is described in this issue. Let's get feedback from @hkwang and then close this issue. |
Yes, this works in principle: on either the hemoglobin or e35_PDZ example, the
|
After using the sequence_to_stills.py fix on the e35_PDZ dataset, where each pass is processed individually, the time-resolved signal looks different than previously, but not noticeably worse. |
With reference to
/n/hekstra_lab/projects/laue-dials-tests/hemoglobin_TR/playground/tutorial-hemoglobin.ipynb
, the following,fails with a
DialsIndexError("No suitable lattice could be found.")
. The cause of this appears to be related to the angles of the four passes. Specifically, I did not specifygeometry.scan.oscillation
during dials.import, According todials.show imported.expt
in that case, the code advances the angle of each image by one degree in each pass (instead of the true step size of 6 degrees), and subsequent laue.initial_solution fails as described above. Presumably the cause of the error is therefore that the indexing routine is being fed garbage frame geometry.When we do specify
geometry.scan.oscillation
as 0,6 during dials.import,dials.show imported.expt
produces four scans withand laue.initial_solution seems to succeed (very confusing given my comment below) but leads to trouble when invoking sequence_to_stills.
The difficulty is that the first ON/OFF pass uses angles (0:6:180) and the second pass uses (183:6:363).
Part of the problem seems to be that there are no angles/no angles are read from the MarCCD header, so we need to specify them externally. Naively it seems that there are three possible solutions:
The text was updated successfully, but these errors were encountered: