Unconfigured Ad

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • Ashmita Khanal
    Junior Member
    • Feb 2024
    • 1

    Problem with using HTseq count

    Hi everyone,
    I am using Htseq count to identify a total number of reads mapped onto each feature. While I do get results, I see that some samples have the same gene name repeated 12 times with the same gene count. Also, I see that the same result is repeated 12 times (for reference i have attached the repetitive value of __no_feature count).
    __no_feature 1544569
    __no_feature 1544569
    __no_feature 1544569
    __no_feature 1544569
    __no_feature 1544569
    __no_feature 1544569
    __no_feature 1544569
    __no_feature 1544569
    __no_feature 1544569
    __no_feature 1544569
    __no_feature 1544569
    __no_feature 1544569
    It performs one run and does it again for 12 runs and gives me the same value for all the genes 12 times. I am confused why is this happening? is it normal for the software to work like this? or is it because I have requested more nodes to run this analysis? I did check my Gtf file and the transcript id and gene id are different in my Gtf file so I do not think that should be an issue. Please find the first few lines of gtf files as well here:
    ##gtf-version X
    # GFF-like GTF i.e. not checked against any GTF specification. Conversion based on GFF input, standardised by AGAT.
    # Liftoff v1.6.3
    # /home/askhanal/miniconda3/envs/rna_seq/bin/liftoff -g ./Spurpurea_519_v5.1.gene_exons.gff3 -dir ./snigra_527M_annot/ -o ./snigra_527M_annot/snigra.527.liftoff.gff3 ./SN527M_sorted.fa ./Spurpurea_519_v5.0.fa
    Chr01 Liftoff gene 804 3346 . + . gene_id "Sapur.001G001900.v5.1"; ID "Sapur.001G001900.v5.1"; Name "Sapur.001G001900"; copy_num_ID "Sapur.001G001900.v5.1_0"; coverage "0.995"; extra_copy_number "0"; sequence_ID "0.961"; valid_ORFs "0";
    Chr01 Liftoff mRNA 804 3346 . + . gene_id "Sapur.001G001900.v5.1"; transcript_id "Sapur.001G001900.1.v5.1"; ID "Sapur.001G001900.1.v5.1"; Name "Sapur.001G001900.1"; Parent "Sapur.001G001900.v5.1"; extra_copy_number "0"; longest "1"; matches_ref_protein "False"; missing_stop_codon "True"; pacid "41822505"; valid_ORF "False";
    Chr01 Liftoff exon 804 1502 . + . gene_id "Sapur.001G001900.v5.1"; transcript_id "Sapur.001G001900.1.v5.1"; ID "Sapur.001G001900.1.v5.1.exon.1"; Parent "Sapur.001G001900.1.v5.1"; extra_copy_number "0"; pacid "41822505";
    Chr01 Liftoff exon 1541 3346 . + . gene_id "Sapur.001G001900.v5.1"; transcript_id "Sapur.001G001900.1.v5.1"; ID "Sapur.001G001900.1.v5.1.exon.2"; Parent "Sapur.001G001900.1.v5.1"; extra_copy_number "0"; pacid "41822505";
    Chr01 Liftoff CDS 837 1502 . + 0 gene_id "Sapur.001G001900.v5.1"; transcript_id "Sapur.001G001900.1.v5.1"; ID "Sapur.001G001900.1.v5.1.CDS.1"; Parent "Sapur.001G001900.1.v5.1"; extra_copy_number "0"; pacid "41822505";
    Chr01 Liftoff CDS 1541 3248 . + 0 gene_id "Sapur.001G001900.v5.1"; transcript_id "Sapur.001G001900.1.v5.1"; ID "Sapur.001G001900.1.v5.1.CDS.2"; Parent "Sapur.001G001900.1.v5.1"; extra_copy_number "0"; pacid "41822505";
    Chr01 Liftoff five_prime_UTR 804 836 . + . gene_id "Sapur.001G001900.v5.1"; transcript_id "Sapur.001G001900.1.v5.1"; ID "Sapur.001G001900.1.v5.1.five_prime_UTR.1"; Parent "Sapur.001G001900.1.v5.1"; extra_copy_number "0"; pacid "41822505";
    Chr01 Liftoff three_prime_UTR 3249 3346 . + . gene_id "Sapur.001G001900.v5.1"; transcript_id "Sapur.001G001900.1.v5.1"; ID "Sapur.001G001900.1.v5.1.three_prime_UTR.1"; Parent "Sapur.001G001900.1.v5.1"; extra_copy_number "0"; pacid "41822505";
    Chr01 Liftoff gene 6845 9497 . - . gene_id "Sapur.001G002000.v5.1"; ID "Sapur.001G002000.v5.1"; Name "Sapur.001G002000"; copy_num_ID "Sapur.001G002000.v5.1_0"; coverage "0.982"; extra_copy_number "0"; sequence_ID "0.902"; valid_ORFs "1";
    Chr01 Liftoff mRNA 6845 9497 . - . gene_id "Sapur.001G002000.v5.1"; transcript_id "Sapur.001G002000.1.v5.1"; ID "Sapur.001G002000.1.v5.1"; Name "Sapur.001G002000.1"; Parent "Sapur.001G002000.v5.1"; extra_copy_number "0"; longest "1"; matches_ref_protein "False"; pacid "41821890"; valid_ORF "True";
    Chr01 Liftoff exon 6845 7216 . - . gene_id "Sapur.001G002000.v5.1"; transcript_id "Sapur.001G002000.1.v5.1"; ID "Sapur.001G002000.1.v5.1.exon.2"; Parent "Sapur.001G002000.1.v5.1"; extra_copy_number "0"; pacid "41821890";
    Chr01 Liftoff exon 8416 9497 . - . gene_id "Sapur.001G002000.v5.1"; transcript_id "Sapur.001G002000.1.v5.1"; ID "Sapur.001G002000.1.v5.1.exon.1"; Parent "Sapur.001G002000.1.v5.1"; extra_copy_number "0"; pacid "41821890";
    Chr01 Liftoff CDS 7153 7216 . - 1 gene_id "Sapur.001G002000.v5.1"; transcript_id "Sapur.001G002000.1.v5.1"; ID "Sapur.001G002000.1.v5.1.CDS.2"; Parent "Sapur.001G002000.1.v5.1"; extra_copy_number "0"; pacid "41821890";
    Chr01 Liftoff CDS 8416 8918 . - 0 gene_id "Sapur.001G002000.v5.1"; transcript_id "Sapur.001G002000.1.v5.1"; ID "Sapur.001G002000.1.v5.1.CDS.1"; Parent "Sapur.001G002000.1.v5.1"; extra_copy_number "0"; pacid "41821890";
    Chr01 Liftoff five_prime_UTR 8919 9497 . - . gene_id "Sapur.001G002000.v5.1"; transcript_id "Sapur.001G002000.1.v5.1"; ID "Sapur.001G002000.1.v5.1.five_prime_UTR.1"; Parent "Sapur.001G002000.1.v5.1"; extra_copy_number "0"; pacid "41821890";
    Chr01 Liftoff three_prime_UTR 6845 7152 . - . gene_id "Sapur.001G002000.v5.1"; transcript_id "Sapur.001G002000.1.v5.1"; ID "Sapur.001G002000.1.v5.1.three_prime_UTR.1"; Parent "Sapur.001G002000.1.v5.1"; extra_copy_number "0"; pacid "41821890";

    Also this is the code that i used:



    for i in {1..36}; do htseq-count -r name -s no -f bam -c htseq_no_strand/out_S${i}.tsv ../alignment_S${i}.bam ../snigra.527.liftoff.gtf ; done

    ​I have 36 samples and I have seen this issue in half of them while others are fine. I did check the file size of the bam file. For the one which gives redundant output in htseq the bam file is around 3.5g and the others have 1.5g. Not sure if it has something to do with it. Any kind of help will be appreciated.
    Thank you

Latest Articles

Collapse

  • SEQadmin2
    Advanced Sequencing Platforms Tackle Neuroscience’s Toughest Genomics Problems
    by SEQadmin2



    Genomics studies in neuroscience face a special challenge due to the brain’s complexity and scarcity of samples. Mapping changes in cell type and state using conventional next-generation sequencing methods remains challenging. Advances in technologies like single-cell sequencing, spatial transcriptomics, and long-read sequencing have opened the door to deeper studies of the brain and diseases like Alzheimer’s, amyotrophic lateral sclerosis (ALS), and schizophrenia.
    ...
    07-09-2026, 11:10 AM
  • SEQadmin2
    Cancer Drug Resistance: The Lingering Barrier to Rising Survival
    by SEQadmin2



    Cancer survival rates have significantly increased in the last few decades in the United States, reaching a combined 70% 5-year survival rate by 2021. Behind this number, there are years of research to find new therapies, drug targets, and early detection methods. But there is one core challenge that keeps slowing down these advances, and it’s about drug resistance.

    There is no single reason why many patients don’t respond to treatment as expected. Cancer is...
    07-08-2026, 05:17 AM
  • GATTACAT
    Reply to Nine Things a Sample Prep Scientist Thinks About Before Sequencing
    by GATTACAT
    Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.
    07-01-2026, 11:43 AM

ad_right_rmr

Collapse

News

Collapse

Topics Statistics Last Post
Started by SEQadmin2, Yesterday, 10:26 AM
0 responses
12 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 07-09-2026, 10:04 AM
0 responses
25 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 07-08-2026, 10:08 AM
0 responses
16 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 07-07-2026, 11:05 AM
0 responses
33 views
0 reactions
Last Post SEQadmin2  
Working...