From de6ebd44d54adaa7ca55988268b7af30e417be18 Mon Sep 17 00:00:00 2001 From: jprocter Date: Wed, 27 Aug 2008 14:15:33 +0000 Subject: [PATCH] fix vamas homedir link --- help/html/vamsas/index.html | 90 +++++++++++++++++++++---------------------- 1 file changed, 45 insertions(+), 45 deletions(-) diff --git a/help/html/vamsas/index.html b/help/html/vamsas/index.html index ce2dffc..7cc841a 100644 --- a/help/html/vamsas/index.html +++ b/help/html/vamsas/index.html @@ -1,45 +1,45 @@ - - -VAMSAS Interoperation - - -

VAMSAS Interoperation

-

Jalview can interact with other applications using - "the VAMSAS Interoperaton framework" - which is an experimental model for interoperation between - bioinformatics applications (Visualization - and Analysis of Molecular - Sequences, Alignements - and Structures). Currently, the only other VAMSAS enabled application is TOPALi - a user friendly program for phylogenetics and evolutionary analysis. -

VAMSAS enabled applications access - a shared bioinformatics dataset containing sequences, alignments, - annotation and trees, which can be represented by an XML document - analogous to a Jalview - Project Archive.

-
Connecting to a VAMSAS session
-The VAMSAS functionality in Jalview is accessed through the Desktop's Vamsas menu. The options available in this menu depend on whether the application is currently interacting with a VAMSAS dataset in a VAMSAS session. -When the application is not connected to a session is active, the menu options are as follows:
- -
- Once you have successfully connected to a VAMSAS session, any data made available by other VAMSAS applications will be automatically imported into Jalview. However, in order to share the data in Jalview with other VAMSAS applications, - you must manually select the Vamsas→"Session Update" entry that is visible when a session is active. Selecting this option will update the VAMSAS session document, with the data loaded into Jalview. Any new alignments, trees and annotation will be written to the session, in addition to any edits you have made to data originally stored in the document. -
- Saving the current session
- You can save the current session as a VAMSAS Session archive using the Vamsas→"Session Update". The file contains a snapshot of the current VAMSAS session, including data from any other applications connected to the session. - Leaving a VAMSAS session
- A session can be disconnected from at any time using the Vamsas→"Stop Session" option. Selecting this option will only disconnect Jalview from the session - any other applications will remain connected to the session. If Jalview is the only application connected to the session and you have not yet saved the VAMSAS session then you will be prompted with an optional 'Save VAMSAS session...' dialog box, allowing the session to be saved and returned to at a later date. -
- VAMSAS Session Persistence
- VAMSAS sessions are persistent - this means that they exist independently of any VAMSAS applications that are connected to them. - This means that if something goes wrong with a VAMSAS application and it crashes or otherwise fails, the VAMSAS session it is connected to will (hopefully) be unaffected. For instance, if Jalview is killed or crashes whilst it is still connected to a session, that session can be recovered in a new Jalview instance using the Vamsas→"Existing session" sub menu.

-

- For further details, please check the VAMSAS website. The VAMSAS framework is implemented as a Java 1.4 Library and its source is will be released under the LGPL license. -  

- - + + +VAMSAS Interoperation + + +

VAMSAS Interoperation

+

Jalview can interact with other applications using + "the VAMSAS Interoperaton framework" + which is an experimental model for interoperation between + bioinformatics applications (Visualization + and Analysis of Molecular + Sequences, Alignements + and Structures). Currently, the only other VAMSAS enabled application is TOPALi - a user friendly program for phylogenetics and evolutionary analysis. +

VAMSAS enabled applications access + a shared bioinformatics dataset containing sequences, alignments, + annotation and trees, which can be represented by an XML document + analogous to a Jalview + Project Archive.

+
Connecting to a VAMSAS session
+The VAMSAS functionality in Jalview is accessed through the Desktop's Vamsas menu. The options available in this menu depend on whether the application is currently interacting with a VAMSAS dataset in a VAMSAS session. +When the application is not connected to a session is active, the menu options are as follows:
+ +
+ Once you have successfully connected to a VAMSAS session, any data made available by other VAMSAS applications will be automatically imported into Jalview. However, in order to share the data in Jalview with other VAMSAS applications, + you must manually select the Vamsas→"Session Update" entry that is visible when a session is active. Selecting this option will update the VAMSAS session document, with the data loaded into Jalview. Any new alignments, trees and annotation will be written to the session, in addition to any edits you have made to data originally stored in the document. +
+ Saving the current session
+ You can save the current session as a VAMSAS Session archive using the Vamsas→"Session Update". The file contains a snapshot of the current VAMSAS session, including data from any other applications connected to the session. + Leaving a VAMSAS session
+ A session can be disconnected from at any time using the Vamsas→"Stop Session" option. Selecting this option will only disconnect Jalview from the session - any other applications will remain connected to the session. If Jalview is the only application connected to the session and you have not yet saved the VAMSAS session then you will be prompted with an optional 'Save VAMSAS session...' dialog box, allowing the session to be saved and returned to at a later date. +
+ VAMSAS Session Persistence
+ VAMSAS sessions are persistent - this means that they exist independently of any VAMSAS applications that are connected to them. + This means that if something goes wrong with a VAMSAS application and it crashes or otherwise fails, the VAMSAS session it is connected to will (hopefully) be unaffected. For instance, if Jalview is killed or crashes whilst it is still connected to a session, that session can be recovered in a new Jalview instance using the Vamsas→"Existing session" sub menu.

+

+ For further details, please check the VAMSAS website. The VAMSAS framework is implemented as a Java 1.4 Library and its source is will be released under the LGPL license. +  

+ + -- 1.7.10.2