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 switch/flip error rate calculations #112

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

JosephLalli
Copy link

The previous code counted a string of errors "0 1 1 1 0" as two flips, two switch errors, and one correct variant. For researchers who want to examine the relative rate of flip events and switch errors unrelated to flips, this is unhelpful.

Instead, I would argue this represents one flip event, three switch errors, two correct variants, and zero "pure switch errors" (ie isolated switch errors that are not associated with a flip error).

This code change calculates flip events, switch errors, pure switch errors, and correct variants. It also calculated how many flip errors occur consecutively (ie, more than two errors in sequence).

Do you agree that this system of tracking errors and flips makes sense? I plan on publishing soon with data calculated using this code, and your sign off on this fork would be of immense help.

Thanks,
Joe

The previous code counted a string of errors "0 1 1 1 0" as two flips, two switch errors, and one correct variant. For researchers who want to examine the relative rate of flip events and switch errors unrelated to flips, this is unhelpful.

Instead, I would argue this represents one flip event, three switch errors, two correct variants, and zero "pure switch errors" (ie isolated switch errors that are not associated with a flip error).

This code change calculates flip events, switch errors, pure switch errors, and correct variants. It also calculated how many flip errors occur consecutively (ie, more than two errors in sequence).
…-rate-calculation

Fix switch/flip error rate calculations
@JosephLalli JosephLalli marked this pull request as ready for review October 25, 2024 18:36
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.

1 participant