3 <head><title>Sequence Features File</title></head>
\r
6 <p><strong>Sequence Features File</strong></p>
\r
7 <p>The Sequence features file (which used to be known as the "Groups
\r
8 file" prior to version 2.08) is a simple way of getting
\r
9 your own sequence annotations into Jalview. It was introduced to allow
\r
10 sequence features to be rendered in the Jalview applet, and so is
\r
11 intentionally lightweight and minimal because the applet is often used
\r
12 in situations where data file size must be kept to a minimum, and no
\r
13 XML parser is available.</p>
\r
14 <p>Features files are imported into Jalview in the following ways:<br>
\r
16 <li>from the command line<strong><pre>
\r
17 -features <<em>Features filename</em>></pre></strong></li>
\r
18 <li>Dragging a features file onto an alignment window</li>
\r
19 <li>Via the "Load Features / Annotations" entry in the
\r
20 <strong>File</strong> menu of an alignment window.</li>
\r
23 <p><strong>Sequence Features File Format</strong></p>
\r
24 <p>A features file is a simple ASCII text file, where each line
\r
25 contains tab separated text fields. <strong>No comments are
\r
26 allowed</strong>.</p>
\r
27 <p>The first set of lines contain type definitions:<strong>
\r
28 <pre><em>Feature label</em>	<em>Feature Colour</em></pre>
\r
29 </strong>A feature type has a text label, and a colour (specified as a
\r
30 red,green,blue 24 bit triplet either in hexadecimal (eg. 00ff00) or as comma
\r
31 separated numbers (ranging from 0 to 255)).
\r
32 <p>The remaining lines in the file are the sequence annotation
\r
33 definitions, where the now defined features are attached to regions on
\r
34 particular sequences, optionally with some descriptive text (displayed
\r
35 in a tooltip when the mouse is near the feature on that sequence). There are two alternate ways of referring to a
\r
36 sequence, either by its text ID, or its index in an associated
\r
38 <em>description</em>	<em>sequenceId</em>	<em>sequenceIndex</em>	<em>start</em>	<em>end</em>	<em>featureType</em></pre>Normally,
\r
39 sequence features are associated with sequences rather than
\r
40 alignments, and the sequenceIndex field is given as "-1". In
\r
41 order to specify a sequence by its index in a particular alignment, the
\r
42 sequenceId should be given as "ID_NOT_SPECIFIED", otherwise the
\r
43 sequenceId field will be used in preference to the sequenceIndex field.</p><p>
\r
44 Feature annotations can be collected into named groups by prefixing
\r
45 definitions with lines of the
\r
46 form:<strong><pre>startgroup	groupname</pre></strong>.. and
\r
47 subsequently post-fixing the group
\r
48 with:<strong><pre>endgroup	groupname</pre></strong>Feature grouping
\r
49 was introduced in version 2.08, and used to control whether a set of features
\r
50 are either hidden or shown together in the <a href="seqfeatures.html">sequence Feature settings
\r
52 <p>A complete example is shown below :<pre>
\r
54 metal ion-binding site	00ff00
\r
55 transit peptide	0,105,215
\r
57 modified residue	105,225,35
\r
58 signal peptide	0,155,165
\r
62 Your Own description here	FER_CAPAA	-1	3	93	domain
\r
63 Your Own description here	FER_CAPAN	-1	48	144	chain
\r
64 Your Own description here	FER_CAPAN	-1	50	140	domain
\r
65 Your Own description here	FER_CAPAN	-1	136	136	modified residue
\r
66 Your Own description here	FER1_LYCES	-1	1	47	transit peptide
\r
67 Your Own description here	Q93XJ9_SOLTU	-1	1	48	signal peptide
\r
68 Your Own description here	Q93XJ9_SOLTU	-1	49	144	chain
\r
69 startgroup	secondarystucture
\r
70 PDB secondary structure annotation	FER1_SPIOL	-1	52	59	strand
\r
71 PDB secondary structure annotation	FER1_SPIOL	-1	74	80	helix
\r
72 endgroup	secondarystructure
\r