|
NAMEBio::Graphics::Panel - Generate GD images of Bio::Seq objectsSYNOPSIS# This script parses a GenBank or EMBL file named on the command # line and produces a PNG rendering of it. Call it like this: # render.pl my_file.embl | display - use strict; use Bio::Graphics; use Bio::SeqIO; my $file = shift or die "provide a sequence file as the argument"; my $io = Bio::SeqIO->new(-file=>$file) or die "could not create Bio::SeqIO"; my $seq = $io->next_seq or die "could not find a sequence in the file"; my @features = $seq->all_SeqFeatures; # sort features by their primary tags my %sorted_features; for my $f (@features) { my $tag = $f->primary_tag; push @{$sorted_features{$tag}},$f; } my $panel = Bio::Graphics::Panel->new( -length => $seq->length, -key_style => 'between', -width => 800, -pad_left => 10, -pad_right => 10, ); $panel->add_track( arrow => Bio::SeqFeature::Generic->new(-start=>1, -end=>$seq->length), -bump => 0, -double=>1, -tick => 2); $panel->add_track(generic => Bio::SeqFeature::Generic->new(-start=>1, -end=>$seq->length), -glyph => 'generic', -bgcolor => 'blue', -label => 1, ); # general case my @colors = qw(cyan orange blue purple green chartreuse magenta yellow aqua); my $idx = 0; for my $tag (sort keys %sorted_features) { my $features = $sorted_features{$tag}; $panel->add_track($features, -glyph => 'generic', -bgcolor => $colors[$idx++ % @colors], -fgcolor => 'black', -font2color => 'red', -key => "${tag}s", -bump => +1, -height => 8, -label => 1, -description => 1, ); } print $panel->png; $panel->finished; exit 0; DESCRIPTIONThe Bio::Graphics::Panel class provides drawing and formatting services for any object that implements the Bio::SeqFeatureI interface, including Ace::Sequence::Feature and Das::Segment::Feature objects. It can be used to draw sequence annotations, physical (contig) maps, or any other type of map in which a set of discrete ranges need to be laid out on the number line.The module supports a drawing style in which each type of feature occupies a discrete "track" that spans the width of the display. Each track will have its own distinctive "glyph", a configurable graphical representation of the feature. The module also supports a more flexible style in which several different feature types and their associated glyphs can occupy the same track. The choice of glyph is under run-time control. Semantic zooming (for instance, changing the type of glyph depending on the density of features) is supported by a callback system for configuration variables. The module has built-in support for Bio::Das stylesheets, and stylesheet-driven configuration can be intermixed with semantic zooming, if desired. You can add a key to the generated image using either of two key styles. One style places the key captions at the top of each track. The other style generates a graphical key at the bottom of the image. Note that this module depends on GD. The optional SVG output depends on GD::SVG and SVG. The installed script glyph_help.pl provides quick help on glyphs and their options. METHODSThis section describes the class and object methods for Bio::Graphics::Panel.Typically you will begin by creating a new Bio::Graphics::Panel object, passing it the desired width of the image to generate and an origin and length describing the coordinate range to display. The Bio::Graphics::Panel->new() method has many configuration variables that allow you to control the appearance of the image. You will then call add_track() one or more times to add sets of related features to the picture. add_track() places a new horizontal track on the image, and is likewise highly configurable. When you have added all the features you desire, you may call png() to convert the image into a PNG-format image, or boxes() to return coordinate information that can be used to create an imagemap. CONSTRUCTORSnew() is the constructor for Bio::Graphics::Panel:
OBJECT METHODS
GLYPH OPTIONSEach glyph has its own specialized subset of options, but some are shared by all glyphs:Option Description Default ------ ----------- ------- -key Description of track for undef display in the track label. -category The category of the track undef for display in the track label. -fgcolor Foreground color black -bgcolor Background color turquoise -linewidth Width of lines drawn by 1 glyph -height Height of glyph 10 -font Glyph font gdSmallFont -fontcolor Primary font color black -font2color Secondary font color turquoise -opacity Value from 0.0 (invisible) 1.0 to 1.0 (opaque) which controls the translucency of overlapping features. -label Whether to draw a label false -description Whether to draw a false description -bump Bump direction 0 -sort_order Specify layout sort order "default" -feature_limit Maximum number of features undef (unlimited) to display -bump_limit Maximum number of levels undef (unlimited) to bump -hbumppad Additional horizontal 0 padding between bumped features -strand_arrow Whether to indicate undef (false) strandedness -stranded Synonym for -strand_arrow undef (false) -part_labels Whether to label individual undef (false) subparts. -part_label_merge Whether to merge undef (false) adjacent subparts when labeling. -connector Type of connector to none use to connect related features. Options are "solid," "hat", "dashed", "quill" and "none". -all_callbacks Whether to invoke undef callbacks for autogenerated "track" and "group" glyphs -subpart_callbacks Whether to invoke false callbacks for subparts of the glyph. -box_subparts Return boxes around feature 0 subparts rather than around the feature itself. -link, -title, -target These options are used when creating imagemaps for display on the web. See L</"Creating Imagemaps">. -filter Select which features to display. Must be a CODE reference. Specifying colors: Colors can be expressed in either of two ways: as symbolic names such as "cyan", as HTML-style #RRGGBB triples, and r,g,b comma-separated numbers. The symbolic names are the 140 colors defined in the Netscape/Internet Explorer color cube, and can be retrieved using the Bio::Graphics::Panel->color_names() method. Transparent and semi-transparent colors can be specified using the following syntax: #RRGGBBAA - red, green, blue and alpha r,g,b,a - red, green, blue, alpha blue:alpha - symbolic name and alpha rgb(r,g,b) - CSS style rgb values rgba(r,g,b,a) - CSS style rgba values Alpha values can be specified as GD style integers ranging from 0 (opaque) to 127 (transparent), or as CSS-style floating point numbers ranging from 0.0 (transparent) through 1.0 (opaque). As a special case, a completely transparent color can be specified using the color named "transparent". In the rgb() and rgba() forms, red, green, blue values can be specified as percentages, as in rgb(100%,0%,50%); otherwise, the values are integers from 0 to 255. In addition, the -fgcolor and -bgcolor options accept the special color names "featureScore" and "featureRGB". In the first case, Bio::Graphics will examine each feature in the track for a defined "score" tag (or the presence of a score() method) with a numeric value ranging from 0-1000. It will draw a grayscale color ranging from lightest (0) to darkest (1000). If the color is named "featureRGB", then Bio::Graphics will look for a tag named "RGB" and will use that as the color. Foreground color: The -fgcolor option controls the foreground color, including the edges of boxes and the like. Background color: The -bgcolor option controls the background used for filled boxes and other "solid" glyphs. The foreground color controls the color of lines and strings. The -tkcolor argument controls the background color of the entire track. Default opacity:For truecolor images, you can apply a default opacity value to both foreground and background colors by supplying a -opacity argument. This is specified as a CSS-style floating point number from 0.0 to 1.0. If the color has an explicit alpha, then the default is ignored. Track color: The -tkcolor option used to specify the background of the entire track. Font: The -font option controls which font will be used. If the Panel was created without passing a true value to -truecolor, then only GD bitmapped fonts are available to you. These include 'gdTinyFont', 'gdSmallFont', 'gdLargeFont', 'gdMediumBoldFont', and 'gdGiantFont'. If the Panel was creaed using a truevalue for -truecolor, then you can pass the name of any truetype font installed on the server system. Any of these formats will work: -font => 'Times New Roman', # Times font, let the system pick size -font => 'Times New Roman-12' # Times font, 12 points -font => 'Times New Roman-12:Italic' # Times font, 12 points italic -font => 'Times New Roman-12:Bold' # Times font, 12 points bold Font color: The -fontcolor option controls the color of primary text, such as labels Secondary Font color: The -font2color option controls the color of secondary text, such as descriptions. Labels: The -label argument controls whether or not the ID of the feature should be printed next to the feature. It is accepted by all glyphs. By default, the label is printed just above the glyph and left aligned with it. -label can be a constant string or a code reference. Values can be any of: -label value Description ------------ ----------- 0 Don't draw a label 1 Calculate a label based on primary tag of sequence "a string" Use "a string" as the label code ref Invoke the code reference to compute the label A known bug with this naming scheme is that you can't label a feature with the string "1". To work around this, use "1 " (note the terminal space). Descriptions: The -description argument controls whether or not a brief description of the feature should be printed next to it. By default, the description is printed just below the glyph and left-aligned with it. A value of 0 will suppress the description. A value of 1 will "magically" look for tags of type "note" or "description" and draw them if found, otherwise the source tag, if any, will be displayed. A code reference will be invoked to calculate the description on the fly. Anything else will be treated as a string and used verbatim. Connectors: A glyph can contain subglyphs, recursively. The top level glyph is the track, which contains one or more groups, which contain features, which contain subfeatures, and so forth. By default, the "group" glyph draws dotted lines between each of its subglyphs, the "segment" glyph draws a solid line between each of its subglyphs, and the "transcript" and "transcript2" glyphs draw hat-shaped lines between their subglyphs. All other glyphs do not connect their components. You can override this behavior by providing a -connector option, to explicitly set the type of connector. Valid options are: "hat" an upward-angling conector "solid" a straight horizontal connector "quill" a decorated line with small arrows indicating strandedness (like the UCSC Genome Browser uses) "dashed" a horizontal dashed line. The -connector_color option controls the color of the connector, if any. Collision control: The -bump argument controls what happens when glyphs collide. By default, they will simply overlap (value 0). A -bump value of +1 will cause overlapping glyphs to bump downwards until there is room for them. A -bump value of -1 will cause overlapping glyphs to bump upwards. You may also provide a -bump value of +2 or -2 to activate a very simple type of collision control in which each feature occupies its own line. This is useful for showing dense, nearly-full length features such as similarity hits. A bump of 3 or the string "fast" will turn on a faster collision-detection algorithm that only works properly with the default "left" sort order. Finally, a bump value of "overlap" will cause features to overlap each other and to made partially translucent (the translucency can be controlled with the -opacity setting). Features that are on opposite strands will bump, but those on the same strand will not. The bump argument can also be a code reference; see below. For convenience and backwards compatibility, if you specify a -bump of 1 and use the default sort order, the faster algorithm will be used. If you would like to see more horizontal whitespace between features that occupy the same line, you can specify it with the -hbumppad option. Positive values increase the amount of whitespace between features. Negative values decrease the whitespace. Keys: The -key argument declares that the track is to be shown in a key appended to the bottom of the image. The key contains a picture of a glyph and a label describing what the glyph means. The label is specified in the argument to -key. box_subparts: Ordinarily, when you invoke the boxes() methods to retrieve the rectangles surrounding the glyphs (which you need to do to create clickable imagemaps, for example), the rectangles will surround the top level features. If you wish for the rectangles to surround subpieces of the glyph, such as the exons in a transcript, set box_subparts to a true numeric value. The value you specify will control the number of levels of subfeatures that the boxes will descend into. For example, if using the "gene" glyph, set -box_subparts to 2 to create boxes for the whole gene (level 0), the mRNAs (level 1) and the exons (level 2). part_labels: If set to true, each subpart of a multipart feature will be labeled with a number starting with 1 at the 5'-most part. This is useful for counting exons. You can pass a callback to this argument; the part number and the total number of parts will be arguments three and four. For example, to label the exons as "exon 1", "exon 2" and so on: -part_labels => sub { my ($feature,undef,$partno) = @_; return 'exon '.($partno+1); } The -label argument must also be true. part_labels_merge: If true, changes the behavior of -part_labels so that features that abut each other without a gap are treated as a single feature. Useful if you want to count the UTR and CDS segments of an exon as a single unit, and the default for transcript glyphs. strand_arrow: If set to true, some glyphs will indicate their strandedness, usually by drawing an arrow. For this to work, the Bio::SeqFeature must have a strand of +1 or -1. The glyph will ignore this directive if the underlying feature has a strand of zero or undef. sort_order: By default, features are drawn with a layout based only on the position of the feature, assuring a maximal "packing" of the glyphs when bumped. In some cases, however, it makes sense to display the glyphs sorted by score or some other comparison, e.g. such that more "important" features are nearer the top of the display, stacked above less important features. The -sort_order option allows a few different built-in values for changing the default sort order (which is by "left" position): "low_score" (or "high_score") will cause features to be sorted from lowest to highest score (or vice versa). "left" (or "default") and "right" values will cause features to be sorted by their position in the sequence. "longest" (or "shortest") will cause the longest (or shortest) features to be sorted first, and "strand" will cause the features to be sorted by strand: "+1" (forward) then "0" (unknown, or NA) then "-1" (reverse). In all cases, the "left" position will be used to break any ties. To break ties using another field, options may be strung together using a "|" character; e.g. "strand|low_score|right" would cause the features to be sorted first by strand, then score (lowest to highest), then by "right" position in the sequence. Finally, a subroutine coderef with a $$ prototype can be provided. It will receive two glyph as arguments and should return -1, 0 or 1 (see Perl's sort() function for more information). For example, to sort a set of database search hits by bits (stored in the features' "score" fields), scaled by the log of the alignment length (with "start" position breaking any ties): sort_order = sub ($$) { my ($glyph1,$glyph2) = @_; my $a = $glyph1->feature; my $b = $glyph2->feature; ( $b->score/log($b->length) <=> $a->score/log($a->length) ) || ( $a->start <=> $b->start ) } It is important to remember to use the $$ prototype as shown in the example. Otherwise Bio::Graphics will quit with an exception. The arguments are subclasses of Bio::Graphics::Glyph, not the features themselves. While glyphs implement some, but not all, of the feature methods, to be safe call the two glyphs' feature() methods in order to convert them into the actual features. The '-always_sort' option, if true, will sort features even if bumping is turned off. This is useful if you would like overlapping features to stack in a particular order. Features towards the end of the list will overlay those towards the beginning of the sort order. -feature_limit: When this option is set to a non-zero value, calls to a track's add_feature() method will maintain a count of features added to a track. Once the feature count exceeds the value set in -feature_limit, additional features will displace existing ones in a way that effects a uniform sampling of the total feature set. This is useful to protect against excessively large tracks. The total number of features added can be retrieved by calling the track's feature_count() method. -bump_limit: When bumping is chosen, colliding features will ordinarily move upward or downward without limit. When many features collide, this can lead to excessively high images. You can limit the number of levels that features will bump by providing a numeric bump_limit option. After the limit is hit, features will pile up on top of each other, usually as a band at the bottom of the track. The -filter option, which must be a CODE reference, will be invoked once for each feature prior to rendering it. The coderef will receive the feature as its single option and should return true if the feature is to be shown and false otherwise. Options and CallbacksInstead of providing a constant value to an option, you may subsitute a code reference. This code reference will be called every time the panel needs to configure a glyph. The callback will be called with three arguments like this:sub callback { my ($feature,$option_name,$part_no,$total_parts,$glyph) = @_; # do something which results in $option_value being set return $option_value; } The five arguments are $feature, a reference to the IO::SeqFeatureI object, $option_name, the name of the option to configure, $part_no, an integer index indicating which subpart of the feature is being drawn, $total_parts, an integer indicating the total number of subfeatures in the feature, and finally $glyph, the Glyph object itself. The latter fields are useful in the case of treating the first or last subfeature differently, such as using a different color for the terminal exon of a gene. Usually you will only need to examine the first argument. This example shows a callback examining the score() attribute of a feature (possibly a BLAST hit) and return the color "red" for high-scoring features, and "green" for low-scoring features: sub callback { my $feature = shift; if ($feature->score > 90) { return 'red'; else { return 'green'; } } The callback should return a string indicating the desired value of the option. To tell the panel to use the default value for this option, return the string "*default*". The callback for -grid is slightly different because at the time this option is needed there is no glyph defined. In this case, the callback will get two arguments: the feature and the panel object: -glyph => sub { my ($feature,$panel) = @_; return 'gene' if $panel->length < 10_000; return 'box'; } When you install a callback for a feature that contains subparts, the callback will be invoked first for the top-level feature, and then for each of its subparts (recursively). You should make sure to examine the feature's type to determine whether the option is appropriate. Also be aware that some options are only called for subfeatures. For example, when using multi-segmented features, the "bgcolor" and "fgcolor" options apply to the subfeatures and not to the whole feature; therefore the corresponding callbacks will only be invoked for the subfeatures and not for the top-level feature. To get information that applies to the top-level feature, use the glyph's parent_feature() method. This returns: * the parent if called with no arguments or with an argument of (1) * the parent's parent if called with an argument of (2) * the parent's parent's parent if called with an argument of (3) * etc. The general way to take advantage of this feature is: sub callback { my ($feature,$option_name,$part_no,$total_parts,$glyph) = @_; my $parent = $glyph->parent_feature(); # do something which results in $option_value being set return $option_value; } or, more concisely: sub callback { my $feature = shift; # first argument my $glyph = pop; # last argument my $parent = $glyph->parent_feature(); # do something which results in $option_value being set return $option_value; } Some glyphs deliberately disable recursion into subparts. The "track", "group", "transcript", "transcript2" and "segments" glyphs selectively disable the -bump, -label and -description options. This is to avoid, for example, a label being attached to each exon in a transcript, or the various segments of a gapped alignment bumping each other. You can override this behavior and force your callback to be invoked by providing add_track() with a true -all_callbacks argument. In this case, you must be prepared to handle configuring options for the "group" and "track" glyphs. In particular, this means that in order to control the -bump option with a callback, you should specify -all_callbacks=>1, and turn on bumping when the callback is in the track or group glyphs. The -subpart_callbacks options is similar, except that when this is set to true callbacks are invoked for the main glyph and its subparts. This option only affects the -label and -description options. ACCESSORSThe following accessor methods provide access to various attributes of the panel object. Called with no arguments, they each return the current value of the attribute. Called with a single argument, they set the attribute and return its previous value.Note that in most cases you must change attributes prior to invoking gd(), png() or boxes(). These three methods all invoke an internal layout() method which places the tracks and the glyphs within them, and then caches the result. Accessor Name Description ------------- ----------- width() Get/set width of panel spacing() Get/set spacing between tracks key_spacing() Get/set spacing between keys length() Get/set length of segment (bp) flip() Get/set coordinate flipping pad_top() Get/set top padding pad_left() Get/set left padding pad_bottom() Get/set bottom padding pad_right() Get/set right padding start() Get the start of the sequence (bp; read only) end() Get the end of the sequence (bp; read only) left() Get the left side of the drawing area (pixels; read only) right() Get the right side of the drawing area (pixels; read only) COLOR METHODSThe following methods are used internally, but may be useful for those implementing new glyph types.
Creating ImagemapsYou may wish to use Bio::Graphics to create clickable imagemaps for display on the web. The main method for achieving this is image_and_map(). Under special circumstances you may instead wish to call either or both of create_web_image() and create_web_map().Here is a synopsis of how to use image_and_map() in a CGI script, using CGI.pm calls to provide the HTML scaffolding: print h2('My Genome'); my ($url,$map,$mapname) = $panel->image_and_map(-root => '/var/www/html', -url => '/tmpimages', -link => 'http://www.google.com/search?q=$name'); print img({-src=>$url,-usemap=>"#$mapname"}); print $map; We call image_and_map() with various arguments (described below) to generate a three element list consisting of the URL at which the image can be accessed, an HTML fragment containing the clickable imagemap data, and the name of the map. We print out an <image> tag that uses the URL of the map as its src attribute and the name of the map as the value of its usemap attribute. It is important to note that we must put a "#" in front of the name of the map in order to indicate that the map can be found in the same document as the <image> tag. Lastly, we print out the map itself.
To use this method effectively, you will need a web server and an image directory in the document tree that is writable by the web server user. For example, if your web server's document root is located at /var/www/html, you might want to create a directory named "tmpimages" for this purpose: mkdir /var/www/html/tmpimages chmod 1777 /var/www/html/tmpimages The 1777 privilege will allow anyone to create files and subdirectories in this directory, but only the owner of the file will be able to delete it. When you call image_and_map(), you must provide it with two vital pieces of information: the URL of the image directory and the physical location of the web server's document tree. In our example, you would call: $panel->image_and_map(-root => '/var/www/html',-url=>'/tmpimages'); If you are working with virtual hosts, you might wish to provide the hostname:portnumber part of the URL. This will work just as well: $panel->image_and_map(-root => '/var/www/html', -url => 'http://myhost.com:8080/tmpimages'); If you do not provide the -root argument, the method will try to figure it out from the DOCUMENT_ROOT environment variable. If you do not provide the -url argument, the method will assume "/tmp". During execution, the image_and_map() method will generate a unique name for the image using the Digest::MD5 module. You can get this module on CPAN and it must be installed in order to use image_and_map(). The imagename will be a long hexadecimal string such as "e7457643f12d413f20843d4030c197c6.png". Its URL will be /tmpimages/e7457643f12d413f20843d4030c197c6.png, and its physical path will be /var/www/html/tmpimages/e7457643f12d413f20843d4030c197c6.png In addition to providing directory information, you must also tell image_and_map() how to create outgoing links for each graphical feature, and, optionally, how to create the "hover title" (the popup yellow box displayed by most modern browsers), and the name of the window or frame to link to when the user clicks on it. There are three ways to specify the link destination:
The -link argument can be either a string or a coderef. If you pass a string, it will be interpreted as a URL pattern containing runtime variables. These variables begin with a dollar sign ($), and are replaced at run time with the information relating to the selected annotation. Recognized variables include: $name The feature's name (display name) $id The feature's id (eg, PK from a database) $class The feature's class (group class) $method The feature's method (same as primary tag) $source The feature's source $ref The name of the sequence segment (chromosome, contig) on which this feature is located $description The feature's description (notes) $start The start position of this feature, relative to $ref $end The end position of this feature, relative to $ref $length Length of this feature $segstart The left end of $ref displayed in the detailed view $segend The right end of $ref displayed in the detailed view For example, to link each feature to a Google search on the feature's description, use the argument: -link => 'http://www.google.com/search?q=$description' Be sure to use single quotes around the pattern, or Perl will attempt to perform variable interpretation before image_and_map() has a chance to work on it. You may also pass a code reference to -link, in which case the code will be called every time a URL needs to be generated for the imagemap. The subroutine will be called with two arguments, the feature and the Bio::Graphics::Panel object, and it should return the URL to link to, or an empty string if a link is not desired. Here is a simple example: -link => sub { my ($feature,$panel) = @_; my $type = $feature->primary_tag; my $name = $feature->display_name; if ($primary_tag eq 'clone') { return "http://www.google.com/search?q=$name"; } else { return "http://www.yahoo.com/search?p=$name"; } The -link argument cascades. image_and_map() will first look for a -link option in the track configuration, and if that's not found, it will look in the Panel configuration (created during Bio::Graphics::Panel->new). If no -link configuration option is found in either location, then image_and_map() will use the value of -link passed in its argument list, if any. The -title and -target options behave in a similar manner to -link. -title is used to assign each feature "title" and "alt" attributes. The "title" attribute is used by many browsers to create a popup hints box when the mouse hovers over the feature's glyph for a preset length of time, while the "alt" attribute is used to create navigable menu items for the visually impaired. As with -link, you can set the title by passing either a substitution pattern or a code ref, and the -title option can be set in the track, the panel, or the method call itself in that order of priority. If not provided, image_and_map() will autogenerate its own title in the form "<method> <display_name> <seqid>:start..end". The -target option can be used to specify the window or frame that clicked features will link to. By default, when the user clicks on a feature, the loaded URL will replace the current page. You can modify this by providing -target with the name of a preexisting or new window name in order to create effects like popup windows, multiple frames, popunders and the like. The value of -target follows the same rules as -title and -link, including variable substitution and the use of code refs. NOTE: Each time you call image_and_map() it will generate a new image file. Images that are identical to an earlier one will reuse the same name, but those that are different, even by one pixel, will result in the generation of a new image. If you have limited disk space, you might wish to check the images directory periodically and remove those that have not been accessed recently. The following cron script will remove image files that haven't been accessed in more than 20 days. 30 2 * * * find /var/www/html/tmpimages -type f -atime +20 -exec rm {} \; BUGSPlease report them.SEE ALSOBio::Graphics::Glyph, Bio::Graphics::Glyph::arrow, Bio::Graphics::Glyph::cds, Bio::Graphics::Glyph::crossbox, Bio::Graphics::Glyph::diamond, Bio::Graphics::Glyph::dna, Bio::Graphics::Glyph::dot, Bio::Graphics::Glyph::ellipse, Bio::Graphics::Glyph::extending_arrow, Bio::Graphics::Glyph::generic, Bio::Graphics::Glyph::graded_segments, Bio::Graphics::Glyph::heterogeneous_segments, Bio::Graphics::Glyph::line, Bio::Graphics::Glyph::pinsertion, Bio::Graphics::Glyph::primers, Bio::Graphics::Glyph::rndrect, Bio::Graphics::Glyph::segments, Bio::Graphics::Glyph::redgreen_box, Bio::Graphics::Glyph::ruler_arrow, Bio::Graphics::Glyph::toomany, Bio::Graphics::Glyph::transcript, Bio::Graphics::Glyph::transcript2, Bio::Graphics::Glyph::translation, Bio::Graphics::Glyph::triangle, Bio::Graphics::Glyph::xyplot, Bio::Graphics::Glyph::whiskerplot, Bio::SeqI, Bio::SeqFeatureI, Bio::Das, GD GD::SVG glyph_help.plAUTHORLincoln Stein <lstein@cshl.org>Copyright (c) 2001 Cold Spring Harbor Laboratory This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See DISCLAIMER.txt for disclaimers of warranty.
Visit the GSP FreeBSD Man Page Interface. |