Unconfigured Ad

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • dharan
    replied
    Problem is still seen in HTSeq - v0.5.3p5

    Dear Simon,

    I had installed the latest version of HTseq (HTSeq-0.5.3p5.tar.gz) to solve the problem but it looks like for me the error still persists.

    I am still facing this error:
    Error: ("'seq' and 'qualstr' do not have the same length.", 'line 2671032 of file ..)
    [Exception type: ValueError, raised in _HTSeq.pyx:765]

    Can you please help me out?

    Thanks,
    Dharanya

    Leave a comment:


  • fishinabarrel
    replied
    I should also add that I installed HTSeq-0.5.3p3 to encounter the qual problem and upon installing HTSeq-0.5.3p4, all was well.

    Leave a comment:


  • fishinabarrel
    replied
    Dear Simon,

    You are my hero.
    Just ran into this problem yesterday. And by this morning a solution was already in place.
    I owe you a beer.

    Leave a comment:


  • NicoBxl
    replied
    Thanks Simon, it worked great.

    Leave a comment:


  • Simon Anders
    replied
    I've just fixed this. In HTSeq 0.5.3p4, SAM files with "*" in the quality field are accepted. Sorry that this took a while.

    Leave a comment:


  • NicoBxl
    replied
    Originally posted by Simon Anders View Post
    Yes, that's a limitation of HTSeq. Fixing this has been on my to-do list since a while; sorry that it's still not done.
    Hi Simon,

    Do you fix this bug ? I've the same problem with tophat 2.0.0 bam files.

    Code:
    samtools view -h -o out.sam in.bam
    htseq-count out.sam annotation.gtf > htseq_out.txt
    gives me

    Code:
    100000 GFF lines processed.
    200000 GFF lines processed.
    283699 GFF lines processed.
    Error occured in line 36 of file out.sam.
    Error: ("'seq' and 'qualstr' do not have the same length.", 'line 36 of file out.sam')
    [Exception type: ValueError, raised in _HTSeq.pyx:765]

    Leave a comment:


  • kamsen
    replied
    Just a few remarks to close this topic:

    1) I was talking about version 0.5.3p3
    2) I made quick & dirty workaround in the code (__init__ modul l. 537) which worked for me. If somebody encounters this problem one could easily just return the line from the .sam file and create 0 qualities / read the original ones. After that the conversion to the Alignment format will work again.
    3) Thanks anyway for your nice package Simon!

    regards

    Leave a comment:


  • Simon Anders
    replied
    Yes, that's a limitation of HTSeq. Fixing this has been on my to-do list since a while; sorry that it's still not done.

    Leave a comment:


  • maubp
    replied
    Sounds like a bug in HTSeq - as discussed in the linked thread, the SAM/BAM file format explicitly allows the sequencing qualities to be omitted (which in SAM is represented with the * character).

    Have you contacted the HTSeq authors?

    P.S. Saying you use the latest version isn't as helpful as saying the actual version you are using. People may read this thread later on

    Leave a comment:


  • kamsen
    started a topic HTSeq dealing with "*" qualities

    HTSeq dealing with "*" qualities

    Hi everyone,

    I started using HTSeq a couple of days ago and now encountered a problem. Maybe someone knows a workaround.

    I am interating over an sam file and cant find a solution for the error:
    (also described here http://seqanswers.com/forums/showthread.php?t=12091)

    ValueError: 'seq' and 'qualstr' do not have the same length.
    The Alignment is from Bowtie2 and lacks the qualitystring (only a "*" is in the file, but the complete read sequence is there).

    Like: blaaaaa ACTACTATCTAC * blaaaaa


    Since I have a lot of files I cant perform a filtering in the first place, because I do not want to touch those big files twice.

    thanks in advance.

    EDIT:
    I am using the latest release of HTSeq.



    regards
    Last edited by kamsen; 04-04-2012, 07:06 AM.

Latest Articles

Collapse

  • SEQadmin2
    Beyond CRISPR/Cas9: Understand, Choose, and Use the Right Genome Editing Tool
    by SEQadmin2



    CRISPR/Cas9 sparked the gene editing revolution for both research and therapeutics.1 But this system still showed severe issues that limited its applications. The most prominent were the heavy reliance on PAM sequences, delivery limitations, double-stranded breaks that prompt unintended edits and cell death, and editing inefficiency (both in targeting and in knock-in reliability).

    Despite this, “CRISPR helped turn genome editing from a specialized technique into
    ...
    07-31-2026, 11:01 AM

ad_right_rmr

Collapse

News

Collapse

Topics Statistics Last Post
Started by SEQadmin2, 08-24-2026, 10:32 AM
0 responses
23 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 08-20-2026, 11:17 AM
0 responses
39 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 08-18-2026, 10:05 AM
0 responses
38 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 08-13-2026, 12:22 PM
0 responses
48 views
0 reactions
Last Post SEQadmin2  
Working...