Skip to content

Remove duplicate sequence_fit < 0.60 check - #165

Open
nsheff wants to merge 2 commits into
devfrom
fix/sequence-fit-duplicate
Open

Remove duplicate sequence_fit < 0.60 check#165
nsheff wants to merge 2 commits into
devfrom
fix/sequence-fit-duplicate

Conversation

@nsheff

@nsheff nsheff commented Aug 3, 2026

Copy link
Copy Markdown
Member

Closes #164

The sequence_fit < 0.60 check appeared twice, so a file below 0.60 scored +3 instead of +2. Removes the duplicate.

@nsheff
nsheff requested a review from donaldcampbelljr August 3, 2026 20:48
@nsheff

nsheff commented Aug 3, 2026

Copy link
Copy Markdown
Member Author

@donaldcampbelljr I'm not sure if this was intentional; but it was confusing. can you glance and see what you meant here?

@donaldcampbelljr

Copy link
Copy Markdown
Member

I believe this to be a typo.

I suspect it is supposed to be tiered like so: .90, .75, .60.

@khoroshevskyi

Copy link
Copy Markdown
Member

Here can be a clue if it was implemented correctly or not:
ad98d8e#diff-03388a6d0d67686753ccfd807bb16dbaf7d15c3743d5adefa963d0aefd666231R326-R341

@khoroshevskyi

khoroshevskyi commented Aug 5, 2026

Copy link
Copy Markdown
Member

I think it won't influence our pipeline a lot, so LGTM

Comment thread bedboss/refgenome_validator/main.py Outdated
points_rating += 1
if sequence_fit < 0.60:
points_rating += 1
points_rating += 2

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This is functionally the same as it was before; I recommend having three tiers and make the middle value ~ 0.75.

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.

3 participants