You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Automatic detection & handling of the bgzipped annotation file, or at least a graceful error message along the lines of ".gff3 file cannot be compressed".
3. What actually happened?
When vg rna tried to parse the annotation file to add transcript splice junctions, it errored on the compressed data. Note that it fails on the first line of the file. That's the header ##gff-version 3.
[vg rna] Parsing graph file ...
[vg rna] Converting graph format ...
[vg rna] Graph and GBWT index parsed in 328.684 seconds, 14.7488 GB
[vg rna] Adding transcript splice-junctions and exon boundaries to graph ...
ERROR: Chromosome path "�BCw�Z]o�8}��" not found in graph or haplotypes index (line 1).
4. If you got a line like Stack trace path: /somewhere/on/your/computer/stacktrace.txt, please copy-paste the contents of that file here:
No stacktrace, but the output of --progress is in #3.
5. What data and command can the vg dev team use to make the problem happen?
Annotation file - note that this uses the chr1 naming system, and the graph uses CHM13#0#chr1 system, so you have to edit the file before using it successfully. However, that's not necessary to reproduce the error, which occurs before vg has a chance to look at any chromosome names.
On the cluster, the chromosome-edited file is /private/groups/patenlab/fokamoto/lr-pan-rna/data/chm13v2.0_RefSeq_Liftoff_v5.2.chm13_prefix.gff3.gz. The same command works with the non-gzipped version of the file, which is the same but without the .gz prefix.
I used a GBZ from the HPRC pangenom v1.1, on the cluster at /private/home/hickey/dev/work/hprc-v1.1-jul4/hprc-v1.1-mc-chm13/hprc-v1.1-mc-chm13.gbz. I suspect this will occur for any valid .gbz graph.
vg version v1.61.0-1291-g1c97950d1 "Plodio"
Compiled with g++ (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 on Linux
Linked against libstd++ 20230528
Using HTSlib headers 101990, library 1.19.1-29-g3cfe8769
Built by [email protected]
If you want to run my exact installation, y'all can find it in /private/groups/patenlab/fokamoto/lr-pan-rna/vg :)
The text was updated successfully, but these errors were encountered:
1. What were you trying to do?
Create a pantranscriptome from a GBZ graph and bgzipped GFF3 annotation set, following the transcriptomic analysis wiki.
(My exact command on the cluster was this:)
2. What did you want to happen?
Automatic detection & handling of the bgzipped annotation file, or at least a graceful error message along the lines of "
.gff3
file cannot be compressed".3. What actually happened?
When
vg rna
tried to parse the annotation file to add transcript splice junctions, it errored on the compressed data. Note that it fails on the first line of the file. That's the header##gff-version 3
.4. If you got a line like
Stack trace path: /somewhere/on/your/computer/stacktrace.txt
, please copy-paste the contents of that file here:No stacktrace, but the output of
--progress
is in #3.5. What data and command can the vg dev team use to make the problem happen?
chr1
naming system, and the graph usesCHM13#0#chr1
system, so you have to edit the file before using it successfully. However, that's not necessary to reproduce the error, which occurs beforevg
has a chance to look at any chromosome names.On the cluster, the chromosome-edited file is
/private/groups/patenlab/fokamoto/lr-pan-rna/data/chm13v2.0_RefSeq_Liftoff_v5.2.chm13_prefix.gff3.gz
. The same command works with the non-gzipped version of the file, which is the same but without the.gz
prefix./private/home/hickey/dev/work/hprc-v1.1-jul4/hprc-v1.1-mc-chm13/hprc-v1.1-mc-chm13.gbz
. I suspect this will occur for any valid.gbz
graph.6. What does running
vg version
say?I built
vg
from source with the following code:Running
vg version
gives:If you want to run my exact installation, y'all can find it in
/private/groups/patenlab/fokamoto/lr-pan-rna/vg
:)The text was updated successfully, but these errors were encountered: