X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2Freleases.html;h=e39a4c19197802dcf32f18a48473d19c4f75b1d3;hb=163ed5b997bbda48e4cdd950e87a8fe01baae7fb;hp=97d6789b4b2cb756b292915b5f0f2c59daa41974;hpb=c430867beda6dcf8236f59d1346ff4b026b0b62b;p=jalview.git
diff --git a/help/html/releases.html b/help/html/releases.html
index 97d6789..e39a4c1 100755
--- a/help/html/releases.html
+++ b/help/html/releases.html
@@ -127,7 +127,7 @@ li:before {
-
Fixed incorrect value in BLOSUM 62 score
- matrix - C->R should be '3'
Old matrix restored with
+ 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
-
@@ -136,7 +136,7 @@ li:before {
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 mean't
+ 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). To restore pre-2.10.2