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.

Sign up for GitHub

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

Jump to bottom

v2.1.9 does not output send correctly when using long-read mode #791

Open
xinehc opened this issue Mar 5, 2024 · 2 comments
Open

v2.1.9 does not output send correctly when using long-read mode #791

xinehc opened this issue Mar 5, 2024 · 2 comments

Comments

@xinehc
Copy link

xinehc commented Mar 5, 2024

v2.1.8:

diamond blastx -q GCF_000708165.1_E_coli_EC2.contigs_genomic.fna -d a.fasta --range-culling -F15 --outfmt 6 qseqid sseqid sstart send scovhsp
NZ_JFJL01000045.1	WP_000046661.1	1	109	100

v2.1.9:

diamond blastx -q GCF_000708165.1_E_coli_EC2.contigs_genomic.fna -d a.fasta --range-culling -F15 --outfmt 6 qseqid sseqid sstart send scovhsp
NZ_JFJL01000045.1	WP_000046661.1	1	0	100

The send column in v2.1.9 is always 0 (bug?). scovhsp seems correct.
@thackl
Copy link

thackl commented Apr 23, 2024 •
edited

I have the same problem. send is reported as 0 in v2.1.9.

@xinehc I think you accidentally put qend in the title of the issue.

thackl added a commit to thackl/detectEVE that referenced this issue Apr 23, 2024
@thackl
use diamond v2.1.8. v2.1.9 has a critical bug bbuchfink/diamond#791
3bcfc08
@Pooryamb
Copy link

The same issue happened to me!
send is 0

@xinehc xinehc changed the title v2.1.9 does not output qstart and qend correctly when using long-read mode v2.1.9 does not output send correctly when using long-read mode Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@thackl @xinehc @Pooryamb