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

feature: support IUPAC bases #53

Closed
wants to merge 9 commits into from
Closed

feature: support IUPAC bases #53

wants to merge 9 commits into from

Conversation

nh13
Copy link
Member

@nh13 nh13 commented Feb 6, 2025

Closes #52

This is much slower when we have a lot unmatched reads, so this needs to be investigated before we merge.

@nh13 nh13 requested a review from tfenne as a code owner February 6, 2025 19:35
@@ -6,7 +6,7 @@ authors = [
]
name = "fqtk"
version = "0.3.2-rc.1"
edition = "2021"
edition = "2024"
Copy link
Member Author

@nh13 nh13 Feb 6, 2025

Choose a reason for hiding this comment

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

@@ -1,3 +1,3 @@
[toolchain]
channel = "1.65.0"
channel = "nightly"
Copy link
Member Author

Choose a reason for hiding this comment

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

FIXME

Copy link
Member

@tfenne tfenne left a comment

Choose a reason for hiding this comment

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

I'm 👍 on functionality. But I think one of @theJasonFan or @jdidion should review too.

Comment on lines 95 to 96
// Note: this allows IUPAC fuzzy matching with IUPAC bases in the expected barcodes, but not in the observed barcodes.
if expected_base & observed_base != observed_base {
Copy link
Member

Choose a reason for hiding this comment

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

Technically I think this will allow IUPAC in the observed ... so long as it's at least as specific at the expected, right? For example, if both are N then it will pass. But if expected is R and observed is N it will fail?

@nh13
Copy link
Member Author

nh13 commented Feb 6, 2025

Did some benchmarking on some data I had lying around. No timing differences across 100M reads across 24 samples.

@nh13 nh13 requested a review from jdidion February 7, 2025 21:14
Copy link

@jdidion jdidion left a comment

Choose a reason for hiding this comment

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

Much cleaner!

@nh13
Copy link
Member Author

nh13 commented Feb 7, 2025

Waiting for rust v1.85 to go out on 2025-02-20.

@nh13
Copy link
Member Author

nh13 commented Feb 10, 2025

Closing in favor of #54

@nh13 nh13 closed this Feb 10, 2025
@nh13 nh13 deleted the feature/iupac-support branch February 10, 2025 23:31
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.

Support IUPAC bases in the expected barcode
3 participants