Hi, first of all, big thanks for the great software!
I've been trying to get UTR predictions using --addUTR in braker1 and got corrupted gene and transcript rows; the start/end positions of the gene/transcripts are not correct. There were 82 cases like this in my ~20,000 gene set. The results of a test run using the test files from the GitHub repository also have this error, so I presumed it was a GUSHR error. I'm not fluent in python so I just filed an issue.
Here's some genes from the test run that have this error. You can see that the gene and transcript rows edited by GUSHR has mistaken start and stop positions.
After meddling around with gushr.py, I noticed at line 680 and 684 (and also in 693, 697), the both two values being compared were str variables, not int. Adding int() to these rows and fixing line 551 (A space was added before the tabular) resulted in a perfect test run gushr.py -t example/augustus.gtf -b example/RNAseq.bam -g example/genome.fa -o utrs2 and braker --addUTR run.
Hi, first of all, big thanks for the great software! I've been trying to get UTR predictions using --addUTR in braker1 and got corrupted gene and transcript rows; the start/end positions of the gene/transcripts are not correct. There were 82 cases like this in my ~20,000 gene set. The results of a test run using the test files from the GitHub repository also have this error, so I presumed it was a GUSHR error. I'm not fluent in python so I just filed an issue.
Here's some genes from the test run that have this error. You can see that the gene and transcript rows edited by GUSHR has mistaken start and stop positions.
After meddling around with
gushr.py
, I noticed at line 680 and 684 (and also in 693, 697), the both two values being compared were str variables, not int. Adding int() to these rows and fixing line 551 (A space was added before the tabular) resulted in a perfect test rungushr.py -t example/augustus.gtf -b example/RNAseq.bam -g example/genome.fa -o utrs2
and braker --addUTR run.