Open wangshun1121 opened 4 years ago
Yes, the explanation is that "reference" transcripts (in the file given with -r
option) cannot be unstranded (as is origin.STRG.179.1
in your example), so such reference transcripts will be discarded before the comparison is performed. Running gffcompare with -V
option should give more information (perhaps too much) about how the input and reference data are processed (and discarded/adjusted as it may be the case).
Btw thanks to your message I just fixed a bug in the -V
output, in the warning message about discarding unstranded reference transcripts.
This is my gtf file for test, saved as 'Test.gtf':
I typed following command:
and this is
gffcmp.tracking
:See, I compare this file with itself, and two transcripts were not marked two '=', instead,
origin.STRG.179
was markedi
compared withorigin.STRG.178
. Is there any explanation?