PuffinPlot issue tracker

Bug: a88/9a0

ID : 9a03d19f-89f6-479e-81ed-d73db8294c5e
Short name : a88/9a0
Status : fixed
Severity : minor
Assigned :
Reporter : Pontus Lurcock <pont@talvi.net>
Creator : Pontus Lurcock <pont@talvi.net>
Created : Thu, 06 Jun 2013 08:18:40 +0000
Target : 1.03
Summary : Allow import of sample-level data [271]

Comment: --------- Comment ---------
ID: 7a9594f9-f172-4490-b586-e13187e3e5a3
Short name: a88/9a0/7a9
From: Pontus Lurcock <pont@talvi.net>
Date: Thu, 06 Jun 2013 08:18:40 +0000

So far two users (Christian and Bruce McFadden) have expressed a
need to use PuffinPlot for simple directional data (presumably 
sample directions obtained from a different program). PuffinPlot 
doesn't currently allow this: even the custom import dialog will
read every line of the file as a demagnetization point. I can 
envisage a somewhat unpleasant hack involving flipping directions,
anchored PCA to "promote" step directions to sample directions, etc.
but it's probably better to do it properly. Shouldn't be too hard
but there are probably a few places in the code where I assume that
there will be at least one demagnetization step associated with a
sample.

Comment: --------- Comment ---------
ID: db14b18f-7a18-4aec-8d5f-05557b8e6f87
Short name: a88/9a0/db1
From: Pontus Lurcock <pont@talvi.net>
Date: Thu, 16 Oct 2014 16:23:32 +0000

Now implemented in a simple fashion, though quite a lot of changes were
required even for this basic functionality. PuffinPlot now supports:
importing of directions to create samples without any demagnetization
data; plotting and analysis of imported directions in the same way as
"normal" (PCA and Fisher) sample directions; and saving and loading of
these directions in PuffinPlot files.

There's one notable omission: because sample and formation corrections
are applied at a Datum level, they have no effect on imported sample
directions. Fixing this would (I think) be a fairly large and delicate
job: the existing data model has to be kept for "normal" data, and the
corrections applied at the sample level *only* for the imported data.
It's not clear whether either of the original requesters actually
required this functionality, so for now I'm omitting it. Can always
open a new ticket and implement it if it's requested later.