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 notebook explaining the effect of jittering #360

Merged
merged 2 commits into from
Mar 19, 2024
Merged

Conversation

rettigl
Copy link
Member

@rettigl rettigl commented Mar 15, 2024

Closes #180

@coveralls
Copy link
Collaborator

coveralls commented Mar 15, 2024

Pull Request Test Coverage Report for Build 8332330972

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.05%) to 91.54%

Totals Coverage Status
Change from base Build 8230697770: 0.05%
Covered Lines: 5984
Relevant Lines: 6537

💛 - Coveralls

Copy link
Member

@zain-sohail zain-sohail left a comment

Choose a reason for hiding this comment

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

Well explained effect of jittering and how to use it.
Would you say that finding the right parameter is just a brute force method for the user? or are there some reasonable values to use?

Perhaps we can come up with an optimization routine to find the optimal jittering (but that's another discussion)

tutorial/8_jittering_tutorial.ipynb Outdated Show resolved Hide resolved
@rettigl rettigl merged commit 0cdaf5d into main Mar 19, 2024
7 of 8 checks passed
@rettigl rettigl deleted the jittering_tutorial branch March 19, 2024 11:20
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.

Add tutorial for correct use of jittering
3 participants