PuffinPlot issue tracker

Bug: a88/c74

ID : c74a4480-1974-4b6f-8572-a31355e03abe
Short name : a88/c74
Status : closed
Severity : minor
Assigned :
Reporter : Pontus Lurcock <pont@talvi.net>
Creator : Pontus Lurcock <pont@talvi.net>
Created : Fri, 24 Oct 2014 09:13:03 +0000
Target : 1.03
Summary : Site param table doesn't update

Comment: --------- Comment ---------
ID: 941bfd1b-d121-49d1-85a2-98a4a99258db
Short name: a88/c74/941
From: Pontus Lurcock <pont@talvi.net>
Date: Fri, 24 Oct 2014 09:16:12 +0000

The following from Adrian Muxworthy:
***
Just looking at the "Fisher by site". It does not seem to update properly,
e.g., if the user selects points for PCA for a site, then calculates the
Fisher site mean, it produces the fisher site mean in the site table.
However, if the user wishes to go back and revise their PCA choices, the
Fisher site mean does not update to include the new picks, it seems to
continue with the old ones, even if cleared, re-picked and saved. Perhaps a
quick investigation might resolve this.

a) Fisher by site. Just tested on my Mac using the native mac program; it
seems to work fine. The issue arose on my phd student's windows 7 machine
using puffin plot. On refreshing the "fisher by site" by pressing the
option in the calculations menu, it did not update properly. Leaving the
old fisher by site calculation in the table. The figures etc are all
updated, but that is from a different process I guess.
***

So far have attempted (and failed) to reproduce using PP 1.02 on:
Windows 7 / Java 8
Windows 7 / Java 7
Windows XP / Java 6


Comment: --------- Comment ---------
ID: f12ecdab-3eb3-4daf-9744-7b847e30e848
Short name: a88/c74/f12
From: Pontus Lurcock <pont@talvi.net>
Date: Thu, 19 Feb 2015 10:34:35 +0000

After further attempts, closing as "can't reproduce". Without the
problematic data file and the *exact* steps to reproduce (which I
haven't been able to obtain), there's not much more that can be done.
Anyway, it's likely that post-v1.02 changes have fixed whatever was
causing it. Can always open a new ticket (hopefully with more detail)
if it rears its head again in 1.03.