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

Add time of flight check in Scan.is_still() #689

Merged
merged 4 commits into from
Feb 12, 2024

Conversation

toastisme
Copy link

Scan.is_still() is currently used in a lot of branching to separate rotational scans from still images that have Scan objects. Time of flight data does not fully fit in either camp, but in most cases the check is used to distinguish between 2D and 3D data. Within DIALS, time of flight data is being treated as 3D data, with the third dimension being time of flight rather than rotation.

Copy link

codecov bot commented Feb 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (65c53c3) 42.14% compared to head (dc767e7) 42.14%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #689   +/-   ##
=======================================
  Coverage   42.14%   42.14%           
=======================================
  Files         185      185           
  Lines       16231    16231           
  Branches     3121     3121           
=======================================
  Hits         6840     6840           
  Misses       8759     8759           
  Partials      632      632           

@ndevenish ndevenish enabled auto-merge (squash) February 12, 2024 09:11
@ndevenish ndevenish merged commit 300f4fe into cctbx:main Feb 12, 2024
12 of 13 checks passed
toastisme added a commit to toastisme/dxtbx that referenced this pull request Jul 18, 2024
Time of flight data does not fully fit in either still or sweeps camp,
but in most cases the check is used to distinguish between 2D and 3D
data.

Within DIALS, time of flight data is being treated as 3D data, with the
third dimension being time of flight rather than rotation.

Update this check to reflect that.
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.

None yet

3 participants