Match Samples dialog
Notes about comparing samples:
- The combination of depth(s), type and label makes a sample unique.
- Generally in StrataBugs, a sample with a top depth A is not equal to a sample with a top depth A and base depth B. During the matching process however, a workspace sample with a null top depth or a null base depth can be matched to a duel-depth database sample on the basis of top or base only (whichever is not null), and sample type. In the highlighted row of the above example, the workspace sample "100 CU" matches the database sample "50 - 100 CU" because their base depths are the same.
- This does not happen in reverse, i.e. duel-depth workspace samples are not matched to single-depth database samples. This is because it is preferable to store duel depths if they are known.
- Where you do have duel-depth workspace data and single-depth database data, you can use exclude/save top/base depths buttons to make samples match.
- Note that the sample status colours also reflect the consistency of the workspace list - there will be conflicts if two samples are the same or overlap. You may cause the workspace list to become inconsistent by excluding some top/base depths.
- If you exclude samples, you exclude any analyses based on them. You are not allowed to exclude samples used as interval boundaries.
- Generally, samples can only conflict if their labels are different (see example). If the database sample has no label, the workspace label will be added to it (prior to saving, workspace status is yellow - part stored). You may select any or all of the samples and press 'exclude' or 'delete' in the labels box to remove either the workspace or database labels.
- Pressing Save will store all unstored samples. Conflicting labels are ignored and samples will still display the red status.
- You can edit the database samples from the Samples & Interpretations module while the workspace is loaded in Organiser; data, status colours and data ranges will be automatically updated.
- Note that in some situations, you may find that not all the of the database samples appear in the list. This will happen where there are samples with overlapping depth ranges which match one of the workspace samples. The hidden samples will not be affected by matching.
Page last updated: 28-Jul-2014 10:40