Difference between revisions of "Talk:GBrowse 1 Configuration HOWTO"
From GMOD
Line 9: | Line 9: | ||
''The current version of Apollo does require sequence-region, but I just chatted with the developer and he is removing the requirement that it be there; he thought it was required by the GFF3 spec. Of course, this question would probably have been better asked on the Apollo mailing list: http://mail.fruitfly.org/mailman/listinfo/apollo'' | ''The current version of Apollo does require sequence-region, but I just chatted with the developer and he is removing the requirement that it be there; he thought it was required by the GFF3 spec. Of course, this question would probably have been better asked on the Apollo mailing list: http://mail.fruitfly.org/mailman/listinfo/apollo'' | ||
--[[User:Scott|Scott]] 16:21, 29 January 2008 (EST) | --[[User:Scott|Scott]] 16:21, 29 January 2008 (EST) | ||
+ | |||
+ | Ah, thanks Scott | ||
+ | <br>I also was under the impression it was in the [http://www.sequenceontology.org/gff3.shtml GFF3 spec]. | ||
+ | This element is optional, but strongly encouraged because it allows parsers to perform bounds checking on features. | ||
+ | So I assumed that it was GBrowse that did not follow the spec. |
Revision as of 14:13, 30 January 2008
Hello Reg. GFF file format: I was wondering if the group/region field has to be (now or in the future) of the format
##sequence-region
I think Apollo (but not Artemis) breaks if that is not included.
The current version of Apollo does require sequence-region, but I just chatted with the developer and he is removing the requirement that it be there; he thought it was required by the GFF3 spec. Of course, this question would probably have been better asked on the Apollo mailing list: http://mail.fruitfly.org/mailman/listinfo/apollo --Scott 16:21, 29 January 2008 (EST)
Ah, thanks Scott
I also was under the impression it was in the GFF3 spec.
This element is optional, but strongly encouraged because it allows parsers to perform bounds checking on features.
So I assumed that it was GBrowse that did not follow the spec.