Grouping components about pmag2 HOT 9 CLOSED

Okay great :) thanks for the suggestions

from pmag2.

The stereonet in the tab shows all the components in the "active" group. You cannot view different groups at the same time. If you want to change the group of a specimen you need to go back to the interpretation. Maybe I can make some more helpful options to merge groups together.

from pmag2.

Maybe it is only me, but I have a tendency to analyze in specimen coordinates and then check how those groups are. If after check I have the feeling that two components are not so distinct than they looked in the Zeijdervelds (let's say 3-5 degrees of difference), I try to merge them, before statistics. But if nobody complains, it is fine.

Also, in addition of a shortcut writing the group name, wouldn't it be possible one that jumps from one to other in alphabetic/numeric order? If that is hard, it is also ok.

from pmag2.

Sort of implemented with c8eb798. You can now quickly switch groups on the interpreted components page and see what group is active.

from pmag2.

Added merging of groups by double click in 173de57.

Should help the workflow!

from pmag2.

It does! And it looks perfect (also it shows all components so if you mislabeled one you can easily correct it ☝️) . Love it!

Now I only miss the Statistics portal being capable to import components ("groups") as different collections (but that is other open issue)

from pmag2.

So you would expect all groups to be in the exported interpretation file and then when it's loaded to the statistic portal it sorts by group and adds three collections?

Collection - ChRM
Collection - Group1
Collection - Group2

from pmag2.

Testing this in 1f7de92. Can you try on beta.paleomagnetism.org to see if its how you expect? I like this idea!

from pmag2.

This is EXACTLY what I wanted! I Love it!!
Then you can try if some of the components you separated are statistically the same (in the CTMD) and if so you can combine, or combine overprinted directions from several sites creating an "overprint locality"

Maybe I am the only one that loves that, but before I had to save several files when I had two components (which in my samples is kind of common).

from pmag2.