GoFish should be largely self-explanatory, but below is a brief description of how to use it.
Note: Leaving the GoFish page in your browser causes the GoFish applet to quit, discarding all current results. Therefore, if you intend to browse the Web while using GoFish it is a good idea to open GoFish in its own browser window.
The GO attribute viewer (bottom left corner of the GoFish window) shows a detail of all ancestors and descendants of the last selected GO attribute.
In fact, choosing Reset returns GoFish to its original state (except that the originally chosen organism remains in effect).
Version 1.11alpha of GoFish differs from version 1.0 mainly in that it supports arbitrary Boolean queries, instead of only "AND" queries. These are described more fully below.
Other minor differences to note:
The main difference between v1.1 and v1.0 is that the newer version allows users to query about the likelihood of gene products' satisfying an arbitrary boolean expression. (In contrast, v1.0 effectively allowed users to enter boolean queries containing (implicitly) only the & [AND] operator.)
In v1.11alpha, when one selects attributes, either from the Gene Ontology Browser panel or from Search results panel, as before, the attribute is added to the list in the Selected GO attributes area, but now the added attribute is preceded by an upper case letter label. In addition, a new clause, represented by the label for the newly added attribute, is added to a boolean query in the field immediately below the Selected GO attributes list. If the attribute is the first attribute chosen, the letter symbol is added by itself; otherwise it is preceded by an ampersand (&). For example, if one first select the attribute "kinase" followed by the attribute "membrane", the Selected GO attributes list will show:
A. kinase B. membraneand the query immediately below will read
A & BThis query string is the default query string for the two selected attributes. If at this point one clicks on the GoFish! button, the current organism's gene products will be ranked by the probability of having both attributes A (kinase) and B (membrane), and shown in the table on the Ranked gene products area on the right. This is exactly the same outcome that one would obtain with GoFish v1.0 if one selected the same organism and the same two attributes. But with v1.11alpha, one can edit the query line to produce a query that combines the selected attributes differently. For example, if one wanted to rank gene products by the probability of having either attribute A or attribute B, we would replace the & in the query string with a |, i.e.
A | BTo represent negation, one uses an exclamation mark (!). For example, if one wanted to rank gene products by the probability of having attribute A and not having attribute B, one would replace the query string by
A & ! B
Now, suppose one selects an additional attribute, "intracellular signaling cascade", which gets assigned the letter C, and suppose we edit the query string so that it reads:
A | B & CThen this query results in ranking the gene products according to the probability of either having attribute A or having both attributes B and C. In other words, in this case gene products are ranked according to the chances of their being either a kinase, or a membrane protein involved in an intracellular signaling cascade.
But suppose that what we really wanted was to rank gene products according to their chances of coding either for a protein involved in an intracellular signaling cascade and that is either kinase or a membrane protein (or both). For this we would need to edit the query to read:
(A | B) & CIn words
(kinase OR membrane) AND intracellular signaling cascadeIn other words, parentheses are required to specify which of the two boolean operators to apply first. When parentheses are left out, by default, the & operator is applied before the | operator, as in the previous example. In general, it is easiest to use parentheses to specify one's intentions, instead of relying on the default precedence of the boolean operators.
Since arbitrary boolean queries are now possible, in the table showing the ranked gene product, there is now a column labeled "QS" (for "Query Satisfaction"). (This column replaces the "Evidence" column in GoFish v1.0.) The score in this column ranges from 0 to 1, with 1 being, in a sense, best (the query is fully satisfied). The meaning of this score is best explained with an example. Consider the same three attributes in the previous example, and suppose that the query is
(A | B) & ! COr, in words,
(kinase OR membrane) AND NOT intracellular signaling cascadeSuppose that upon ranking the gene products according to this query, one gene product gets a QS score of 0.67 = 2/3. This says (roughly) that for this gene product 2 out of the 3 attributes satisfy the query, and 1 doesn't. More precisely, it says that if the available evidence (now regarded as a binary classification: the gene product either has or doesn't have the attribute) for 1 out of the 3 attributes were the opposite of what it is, this gene product would satisfy the query. If instead a gene product has a QS score of 1 for the query above, it means that there is evidence in the literature for that gene product being either a kinase or a membrane protein, and that, in addition, that there is no evidence that it is involved in intracellular signaling cascade. In contrast, a QS of 0 means that the evidence contradicts the query for all attributes; the evidence would have to be exactly the opposite of what one finds in the literature for the gene product in question to satisfy the query.
As with GoFish v1.0 we can remove individual elements from the selected attributes list by first clicking on the attributes we want to remove, and then clicking on the Remove button. In GoFish v1.11alpha however, this action has two additional effects. First, if necessary, the remaining attributes in the list get relabeled so that there are no gaps in the sequence of label (A, B, C, etc.). Second, the query string gets reset to its default query string for the current number of selected attributes. For example, suppose 3 attributes are selected, labeled A, B, and C, and that the query string is
A & ! (B & C)then if we remove the attribute labeled B, the label for the attribute originally labeled C will change to B; the label for the A-attribute remains unchanged; and the query string becomes
A & B