From 8318a5d8ceca6cf6d5adbb815471f9433cc9aa56 Mon Sep 17 00:00:00 2001
From: jprocter
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.
Data Sharing Capability | Jalview Version | +
Alignments, sequences and annotation, trees, database references, cDNA/protein mappings. | 2.4 |
Mouseover location across linked DNA, protein and structure positions. | 2.4 |
Jalview project settings (Multiple views, groups, tree partitions, colouring, window positions) | 2.4.1 |
Sequence region and column selections | 2.4.1 |
- 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. + For further details about the VAMSAS framework, please check the VAMSAS website. The VAMSAS framework is implemented as a Java 1.4 Library and depends on a number of other open source projects. Its source is will be released under the LGPL license.