<td width="60" nowrap>
<div align="center">
<strong><a name="Jalview.2.10.2">2.10.2</a><br />
- <em>30/5/2017</em></strong>
+ <em>20/6/2017</em></strong>
</div>
</td>
<td><div align="left">
<ul>
<li>
<!-- JAL-2398, -->Fixed incorrect value in BLOSUM 62 score
- matrix - C->R should be '3'<br />Old matrix restored with
+ matrix - C->R should be '-3'<br />Old matrix restored with
this one-line groovy script:<br />jalview.analysis.scoremodels.ScoreModels.instance.BLOSUM62.@matrix[4][1]=3
</li>
<li>
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.<br />Jalview now treats gaps in the same way as
SeqSpace (ie it scores them as 0). To restore pre-2.10.2
<li><!-- JAL-2385 -->Conservation shading or PID threshold lost when base colourscheme changed if slider not visible</li>
<li><!-- JAL-2547 -->Sequence features shown in tooltip for gaps before start of features</li>
<li><!-- JAL-2576 -->Very large alignments take a long time to load</li>
+ <li><!-- JAL-2590 -->Cannot load Newick trees from eggnog ortholog database</li>
</ul>
<em>Application</em>
<ul>