Difference between revisions of "Testwork: Aggregating samples"
(→Queries Table) |
(→Queries Table) |
||
| Line 1: | Line 1: | ||
==Queries Table== |
==Queries Table== |
||
[[file:Testwork-queries.png|thumb|Screenshot showing portion of a large queries table]] |
[[file:Testwork-queries.png|thumb|Screenshot showing portion of a large queries table]] |
||
| − | The list of samples that run through a circuit model is shown in the "Queries" table. This is the list of samples that contain all of the necessary test results required to satisfy a particular model. For example, the "queries" table for a Bond/Barratt model will show only those samples that have a [[Testwork: Crushing work index|crushing work index]] (Wi<sub>C</sub>), [[Testwork: Bond rod mill work index|Bond rod mill work index]] (Wi<sub>RM</sub>) and a [[Testwork: Bond ball mill work index|Bond ball mill work index]] (Wi<sub>BM</sub>). Any sample that lacks any of these three values can not be run in the model and will not appear in the listing. |
+ | The list of samples that run through a circuit model is shown in the "Queries" table. This is the list of samples that contain all of the necessary test results required to satisfy a particular model. For example, the "queries" table for a Bond/Barratt model (contained in a 'bond' Project folder) will show only those samples that have a [[Testwork: Crushing work index|crushing work index]] (Wi<sub>C</sub>), [[Testwork: Bond rod mill work index|Bond rod mill work index]] (Wi<sub>RM</sub>) and a [[Testwork: Bond ball mill work index|Bond ball mill work index]] (Wi<sub>BM</sub>). Any sample that lacks any of these three values can not be run in the model and will not appear in the listing. |
| − | The "queries" table can not be directly manipulated. The list is generated automatically by combining individual test results by matching the sample name and program fields. |
+ | The "queries" table can not be directly manipulated. The list is generated automatically by combining individual test results by matching the sample name and program fields. The matching algorithm is controlled by the 'folder' that has been selected for this [[Project]]. |
| + | |||
| + | ===Requirements for matching results=== |
||
| + | In order for a Project to correctly associate test results (to realize that "these are actually different tests on the same sample"), the following criteria must be satisfied: |
||
| + | * The test results must be part of the same project (having the same `ProjNum`) |
||
| + | * The `Sample` fields must be identical ("Composite 1" is not the same as "Composite No.1" or "composite 1") |
||
| + | * The `Program` fields must be identical ("SAG feed" of Program "2010 survey" is not the same sample as "SAG feed" of program "2011 survey"). |
||
| + | |||
| + | If a sample name is misspelled in one of the testwork tables, then that sample will not match the name in the other tables and that sample will not appear in the Query table. ''(Hint: you can see mismatched sample names by scrolling through the -All- table in testwork.)'' |
||
===Example: Aggregation of data=== |
===Example: Aggregation of data=== |
||
Revision as of 20:26, 13 April 2013
Queries Table
The list of samples that run through a circuit model is shown in the "Queries" table. This is the list of samples that contain all of the necessary test results required to satisfy a particular model. For example, the "queries" table for a Bond/Barratt model (contained in a 'bond' Project folder) will show only those samples that have a crushing work index (WiC), Bond rod mill work index (WiRM) and a Bond ball mill work index (WiBM). Any sample that lacks any of these three values can not be run in the model and will not appear in the listing.
The "queries" table can not be directly manipulated. The list is generated automatically by combining individual test results by matching the sample name and program fields. The matching algorithm is controlled by the 'folder' that has been selected for this Project.
Requirements for matching results
In order for a Project to correctly associate test results (to realize that "these are actually different tests on the same sample"), the following criteria must be satisfied:
- The test results must be part of the same project (having the same `ProjNum`)
- The `Sample` fields must be identical ("Composite 1" is not the same as "Composite No.1" or "composite 1")
- The `Program` fields must be identical ("SAG feed" of Program "2010 survey" is not the same sample as "SAG feed" of program "2011 survey").
If a sample name is misspelled in one of the testwork tables, then that sample will not match the name in the other tables and that sample will not appear in the Query table. (Hint: you can see mismatched sample names by scrolling through the -All- table in testwork.)
Example: Aggregation of data
The example data set from Los Bronces (from published papers by Oestreicher & Spollen, SAG 2006 and Becerra & Amelunxen, Procemin 2012) is summarized below. It contains samples that have been subjected to a variety of tests including the Bond work index series and the drop weight tests.
| Sample | WiBM | WiRM | WiC | A×b |
| Los Bronces A | 13.3 | 9.4 | 8.97 | 55.4 |
| Los Bronces B | 14.9 | 11.2 | 8.83 | 44.4 |
| Los Bronces C | 14.5 | 13.1 | 9.46 | 33 |
| LB 25th percentile | 15.6 | 14.7 | 35.7 | |
| LB 75th percentile | 17.4 | 18.5 | 27.1 | |
| LB average | 16.5 | 16.7 | 32.3 | |
| LB maximum | 22 | 24.6 | 22.8 | |
| LB median | 16.5 | 16.7 | 30 | |
| LB minimum | 12.2 | 11.9 | 50.9 |
A Bond/Barratt model would generate a query table that returns only samples Los Bronces A, Los Bronces B and Los Bronces C. The other samples are missing one of the required test results (the crushing work index, WiC), so those samples can not be run in the standard Bond/Barratt model contained in a 'bond' folder (however, they can be run in a 'bond_SetWiC' folder which relaxes the requirement to have a crushing work index value).
