The North American Vulcanism Geochemistry Dataset (called the NAVDAT dataset) comprises a large set of volcanic rock measurements in Western USA, with both age and geochemistry information. The data covers a complex geological setting, where there has been a combination of margin- and plume-based processes. In this case study, we try to partition data that was associated with the passing of the North American continent over the Yellowstone hot spot. Such a partitioning allows present-day regions to be identified that evolved due to the plume interaction. Geochemistry of the two (now segmented) populations allow for more indepth studies and validation. The case study illustrates the integration and quantitative analysis of data varying across both space and time.
Experience with GPlates (loading data, reconstruction animation and coregistration) as well as with the Orange data mining suite is necessary; the reading of the data mining tutorial 1, Identifying depositional environments for Australian age-coded mineral deposits, is recommended as it describes important steps in more detail. (The process of assigning plate IDs ("cookie-cutting") is also used here, but it can be skipped; another tutorial describes this more in depth.)
Start GPlates from the command line as follows:
gplates --data mining
Open the following feature collections:
Configure reconstruction animation settings between 60 Ma and 0 Ma, with a 1 Ma step.
The following depicts the loaded data (HS are shown as blue triangles; the order of the layers and the colouring might need to be changed to get the same picture):
Since the volcanic rocks measurements do not come with reconstruction information we need to assign to it approriate plate IDs ("cookie cut" it) like already shown in another tutorial.
After a few minutes (on a dual core machine) GPlates should have calculated the plate ID assignment for the specified time period. As a result the colours of the NAVDAT points should have adopted the colour of the corresponding plate (unless another colour scheme has been chosen) and when going back in time they should move with that plate.
The loaded data after attaching it to the North American plate:
The palaeo-association to be computed is to calculate the distance between all rock samples (the seeds), and their closest hot spot for each time, storing also the hot spot name. The coregistration must thus be set up to compute two relational associations, followed by selection of the full geochemistry metadata corresponding to the rock samples for subsequent analysis.
The following coregistration procedure should be carried out:
The first associations are depicted below (note that the red disk symbol in the bottom right corner of the main window indicates that the changes made to the NAVDAT dataset have not been saved yet - this, of course , only applies if step 2 has been skipped):
More selections, with geochemical attributes coregistered (here only the spherical coordinates and a selection of four chemical attributes of the volcanic rock data have been chosen for coregistration):
GPlates' coregistration table result (most probably there will be no coincidence in the numbering of the seeds of the picture due to the way GPlates' internally achieves the results):
After exporting the coregistration result open Orange, and extract the three necessary time-series from the coregistration, i.e. the palaeo-distance, the palaeo-hotspot name, and the palaeo-ID (this last one will be unnecessary in a future release). The following depicts the resultant time-series for a few exemplar rocks (with the widget renamed appropriately):
The three time-series should be extracted, and their values at time of birth computed (this is how we localise rocks in close proximity to the hot spots at their inception). These three vectors should then be combined. The full geochemical metadata is extracted from the present-day. A special merge component is then used to append the metadata to the palaeo-features - this widget allows the GPlates-IDs to be selected for both datasets, thereby obtaining row-wise correspondence (database tables operate in the same fashion for table joins). The following schema depicts the data processing phase, resulting in the final merged dataset (tables denoted with "Check" are just for checking intermediate results):
The next step is to filter out rocks that have formed close to the hot spot, and those that have formed close to Yellowstone in particular. The Select Data widget allows for defining of this filtering operation. Firstly for the palaeo-distance, a threshold distance should be chosen to suit the problem e.g. 200km. Next the palaeo-name attribute should be filtered using the same widget to extract data corresponing to Yellowstone only. The following snapshot captures the filtering step:
The final part of the data mining is to extract the lat-long coordinates of the segmented rock samples and to analyse the geochemistries of the two resultant populations, i.e. rocks associated with Yellowstone, and those not associated. The former task is computed by selecting the Latitude and Longitude attributes, and exporting. Several geochemical studies are possible. In comparing plume-based magmatism to margin-based magmatism, rare earth elements such as Yb, La, Ta and Th are good candidates. Coming soon: direct access to decorating selections in GPlates.
An important hint: The Select Data widget filters data and provides the complement as output, too, and automatically appends an identity for subsequent processing - in this study we need to identify both samples associated with hot spots, and those not. And the Select Attribute widget requires one of the two attributes to be chosen as a class attribute for saving to work. The following plot depicts a possible schema to complete the data mining task:
The following plot depicts Yb vs La for the two populations:
Coming soon: changing the palaeo-distance threshold in the data mining tool will be fed back to GPlates, providing graphical feedback. The following three palaeo-distance thresholds depict the segmentation implication:
Palaeo-distance threshold 160km:
Palaeo-distance threshold 260km:
Palaeo-distance threshold 360km:
The segmented result can also be viewed through time in GPlates, for example consider the following snapshots through 10, 4, 2 and 0 Ma respectively: