X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2Freleases.html;h=9fae20fa398ef55f7b0367e06106f5e50246f084;hb=33342a9ee15da4873f9fd94bc2330bc73e7bc51f;hp=471e12a5dcb2056da476c5945a98cbad232b26aa;hpb=438f101f56c8bcfe5422a54328d7bad60e9c07eb;p=jalview.git diff --git a/help/html/releases.html b/help/html/releases.html index 471e12a..9fae20f 100755 --- a/help/html/releases.html +++ b/help/html/releases.html @@ -70,6 +70,373 @@ li:before {
+ 2.10.3b1
23/1/2018
+
+ +
+
+
+ Desktop
+ + + + +
+ 2.10.3
17/11/2017
+
+ +
+ + + Scripting + + Testing and Deployment + +
+
+ General + + Desktop + + Applet
+ + BioJSON
+ + New Known Issues + + Known Java 9 Issues + +
+ + + +
+ 2.10.2b2
+ 2/10/2017
+
+ +
+ New features in Jalview Desktop + +
+
+
+ + + +
+ 2.10.2b1
+ 7/9/2017
+
+ +
+ + +
+
+ + +
+ + + +
2.10.2
17/8/2017
@@ -210,7 +577,9 @@ li:before { Updated JABAWS client to v2.2
  • - Filter non-standard amino acids and nucleotides when submitting to AACon and other MSA Analysis services + Filter non-standard amino acids and + nucleotides when submitting to AACon and other MSA + Analysis services
  • URLs for viewing database @@ -272,25 +641,23 @@ li:before { matrix - C->R should be '-3'
    Old matrix restored with this one-line groovy script:
    jalview.analysis.scoremodels.ScoreModels.instance.BLOSUM62.@matrix[4][1]=3
  • -
  • - Fixed Jalview's treatment of gaps in PCA - and substitution matrix based Tree calculations.

    In - earlier versions of Jalview, gaps matching gaps were - penalised, and gaps matching non-gaps penalised even more. - In the PCA calculation, gaps were actually treated as - non-gaps - so different costs were applied, which meant - Jalview's PCAs were different to those produced by - SeqSpace.
    Jalview now treats gaps in the same way as - SeqSpace (ie it scores them as 0).

    Enter - the following in the Groovy console to restore pre-2.10.2 - behaviour:
    +
  • Fixed + Jalview's treatment of gaps in PCA and substitution matrix + based Tree calculations.

    In earlier versions + of Jalview, gaps matching gaps were penalised, and gaps + matching non-gaps penalised even more. In the PCA + calculation, gaps were actually treated as non-gaps - so + different costs were applied, which meant Jalview's PCAs + were different to those produced by SeqSpace.
    Jalview + now treats gaps in the same way as SeqSpace (ie it scores + them as 0).

    Enter the following in the + Groovy console to restore pre-2.10.2 behaviour:
    jalview.analysis.scoremodels.ScoreMatrix.scoreGapAsAny=true // for 2.10.1 mode
    jalview.analysis.scoremodels.ScoreMatrix.scoreGapAsAny=false // to restore 2.10.2 mode

    Note: these settings will affect all subsequent tree and PCA - calculations (not recommended) -
  • + calculations (not recommended)
  • Fixed off-by-one bug that affected scaling of branch lengths for trees computed using @@ -643,7 +1010,8 @@ li:before { doesn't always add secondary structure annotation.
  • - + +
    2.10.1
    29/11/2016
    @@ -1320,6 +1688,10 @@ li:before { after clicking on it to create new annotation for a column. +
  • + Null Pointer Exception raised when + pressing Add on an orphaned cut'n'paste window. +