Talk:GBrowse 1 Configuration HOWTO
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. Alpapan
* -> h3 for track properties, etc, easier on the eyes?
I ran a snippet of code...
s/^\*(.+)\n/===$1===\n/
...to produce the following output. If anyone cares, I think it lets the track properties - which are currently bulleted - stand out a bit more, making them easier to find. (check the General [SECTION] for an example.) --Stewarta 13:43, 14 March 2008 (EDT)
Declaring New Aggregators
i think it should be
aggregators = transcript{....
not
aggregator = transcript{....
At least with my gbrowse dev branch... I didn't edit it in case i 'm wrong. Alpapan
