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

Improvements to AzimuthIntervals #800

Merged
merged 15 commits into from
Nov 20, 2024
Merged

Improvements to AzimuthIntervals #800

merged 15 commits into from
Nov 20, 2024

Conversation

tskisner
Copy link
Member

  • Use a more robust technique for computing the scan velocity and acceleration in the presence of noise and flags
  • Use a fit to the velocity for finding turnarounds
  • Add a unit test to generate plots and check that the expected number of scans is found

Example plot of scan properties found in the unit tests:
az_intervals

Copy link
Member

@keskitalo keskitalo left a comment

Choose a reason for hiding this comment

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

Looks good. More robust interval finding, backed by a unit test.

src/toast/ops/simple_jumpcorrect.py Show resolved Hide resolved
src/toast/utils.py Show resolved Hide resolved
@tskisner tskisner merged commit 92b4eed into toast3 Nov 20, 2024
7 checks passed
@tskisner tskisner deleted the so_fixes branch November 20, 2024 21:26
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