Entering test results - Revision history

Alex Doll: /* Entering a batch of test results */

2017-08-19T19:58:33Z

Entering a batch of test results

← Older revision		Revision as of 19:58, 19 August 2017
Line 25:		Line 25:

	===Entering a batch of test results===		===Entering a batch of test results===
	* download the [[https://www.sagmilling.com/articles/19/view/?s=1 test template spreadsheet]]		* download the [https://www.sagmilling.com/articles/19/view/?s=1 test template spreadsheet]
	or		or
	* using a spreadsheet provided by you laboratory, insert a row above the table of results and insert the '''field names''' for a particular test.		* using a spreadsheet provided by you laboratory, insert a row above the table of results and insert the '''field names''' for a particular test.

Alex Doll: /* Access Level */

2015-05-19T16:37:03Z

Access Level

← Older revision		Revision as of 16:37, 19 May 2015
Line 2:		Line 2:
	[[Category:Testwork]]		[[Category:Testwork]]
	==Access Level==		==Access Level==
	Anyone with 'user' access level <u>and</u> who has been set by an administrator to have 'read/write' access to a project will be able to enter test results for that project.		Anyone with 'user' access level (privileges) <u>and</u> who has been set by an administrator to have 'read/write' access to a project will be able to enter test results for that project.

	Users with 'read' access will be able to view test results, but not edit them or add new results. Contact your administrator if you need access to edit or add test results.		Users with 'read' access will be able to view test results, but not edit them or add new results. Contact your administrator if you need access to edit or add test results.


	==Entering Test Results==		==Entering Test Results==

Alex Doll: /* Entering Test Results */

2014-04-25T18:59:28Z

Entering Test Results

Alex Doll: /* Queries Table */

2014-02-07T05:45:43Z

Queries Table

← Older revision		Revision as of 05:45, 7 February 2014
Line 43:		Line 43:

	This summary table is automatically generated and can not be manually edited. In order to adjust a value in this table, it is necessary to modify the individual testwork pages.		This summary table is automatically generated and can not be manually edited. In order to adjust a value in this table, it is necessary to modify the individual testwork pages.

	===Queries Table===
	// IN PROGRESS //
	The list of samples that run through a circuit model is shown in the "[[Testwork: Queries\|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 "query" table for a Bond/Barratt model will show only those samples that have a [[Testwork: Crushing work index\|crushing work index]] (WiC), [[Testwork: Bond rod mill work index\|Bond rod mill work index]] (WiRM) and a [[Testwork: Bond ball mill work index\|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.

Alex Doll: /* Entering a batch of test results */

2013-12-08T20:47:19Z

Entering a batch of test results

← Older revision		Revision as of 20:47, 8 December 2013
Line 30:		Line 30:
	* using a spreadsheet provided by you laboratory, insert a row above the table of results and insert the '''field names''' for a particular test.		* using a spreadsheet provided by you laboratory, insert a row above the table of results and insert the '''field names''' for a particular test.
	then		then
			* define the [[How to use the Litho table\|sample names]] to be entered,
	* cut & paste a table of values from the spreadsheet in a "[[testwork: Batch entry\|batch]]";		* cut & paste a table of values from the spreadsheet in a "[[testwork: Batch entry\|batch]]";

Alex Doll: /* General Concepts */

2013-12-08T20:45:54Z

General Concepts

← Older revision		Revision as of 20:45, 8 December 2013
Line 17:		Line 17:
	The testing program should collect a series of samples corresponding to a particular interval of drill core, mine bench or some other reasonably uniform composite. Each sample will then have a series of tests conducted on it depending on which model (or models) are intended to be run. In order to properly index and organize the databases, each sample must have the following:		The testing program should collect a series of samples corresponding to a particular interval of drill core, mine bench or some other reasonably uniform composite. Each sample will then have a series of tests conducted on it depending on which model (or models) are intended to be run. In order to properly index and organize the databases, each sample must have the following:
	[[File:Testwork-NewProgram.png\|thumb\|Screenshot of entering a new testwork Program]]		[[File:Testwork-NewProgram.png\|thumb\|Screenshot of entering a new testwork Program]]
	* '''Program''': Used to group tests that were all part of the same batch of testing. Often this is denoted by the date of testing, lab name or part of the orebody that was being examined. ~~An example~~ Program ~~name~~ is		* '''Program''': Used to group tests that were all part of the same batch of testing. Often this is denoted by the date of testing, lab name or part of the orebody that was being examined. Example Program names are '2013', 'west extension' or 'infill'.
	[[File:Testwork-NewSample.png\|thumb\|Screenshot of dialogue to create new samples]]		[[File:Testwork-NewSample.png\|thumb\|Screenshot of dialogue to create new samples]]
	* '''Sample''': Sample name that is unique within a project. This can be a number, a drillhole number:from-to interval, or any other unique identifier. The same sample name will be used in all the tests in order to tell the database that "this is the same sample" when it goes looking to gather information.		* '''Sample''': Sample name that is unique within a project. This can be a number, a drillhole number:from-to interval, or any other unique identifier. The same sample name will be used in all the tests in order to tell the database that "this is the same sample" when it goes looking to gather information.

			The [[How to use the Litho table\|Sample names must be declared]] before test results may be entered for them.
	The database will only match samples (across the different tests) if both the '''Sample''' and '''Program''' entries are ''identical''. Enter these two values with care, otherwise the database won't be able to gather together the required tests for modelling, and samples will be missed from any calculations.

	If the database finds two different test results (for the same test) with the same '''Sample''' name, then the two test results are merged by arithmetic averaging. For example, if two ball mill work index tests at different closing screen sizes were performed on the same sample, and entered with the identical sample name, then the database will average the work index (for modelling) and will also average the test F80, gpr and P80 for display.		If the database finds two different test results (for the same test) with the same '''Sample''' name, then the two test results are merged by arithmetic averaging. For example, if two ball mill work index tests at different closing screen sizes were performed on the same sample, and entered with the identical sample name, then the database will average the work index (for modelling) and will also average the test F80, gpr and P80 for display.

Alex Doll at 00:29, 6 December 2013

2013-12-06T00:29:55Z

← Older revision		Revision as of 00:29, 6 December 2013
Line 18:		Line 18:
	[[File:Testwork-NewProgram.png\|thumb\|Screenshot of entering a new testwork Program]]		[[File:Testwork-NewProgram.png\|thumb\|Screenshot of entering a new testwork Program]]
	* '''Program''': Used to group tests that were all part of the same batch of testing. Often this is denoted by the date of testing, lab name or part of the orebody that was being examined. An example Program name is		* '''Program''': Used to group tests that were all part of the same batch of testing. Often this is denoted by the date of testing, lab name or part of the orebody that was being examined. An example Program name is
	[[File:Testwork-~~NewProgram~~.png\|thumb\|Screenshot of ~~entering~~ a ~~new~~ ~~testwork~~ ~~Program~~]]		[[File:Testwork-NewSample.png\|thumb\|Screenshot of dialogue to create new samples]]
	* '''Sample''': Sample name that is unique within a project. This can be a number, a drillhole number:from-to interval, or any other unique identifier. The same sample name will be used in all the tests in order to tell the database that "this is the same sample" when it goes looking to gather information.		* '''Sample''': Sample name that is unique within a project. This can be a number, a drillhole number:from-to interval, or any other unique identifier. The same sample name will be used in all the tests in order to tell the database that "this is the same sample" when it goes looking to gather information.

Line 25:		Line 25:
	If the database finds two different test results (for the same test) with the same '''Sample''' name, then the two test results are merged by arithmetic averaging. For example, if two ball mill work index tests at different closing screen sizes were performed on the same sample, and entered with the identical sample name, then the database will average the work index (for modelling) and will also average the test F80, gpr and P80 for display.		If the database finds two different test results (for the same test) with the same '''Sample''' name, then the two test results are merged by arithmetic averaging. For example, if two ball mill work index tests at different closing screen sizes were performed on the same sample, and entered with the identical sample name, then the database will average the work index (for modelling) and will also average the test F80, gpr and P80 for display.

			===Entering a batch of test results===
	There are three ways to enter a test result:
			* download the [[https://sagmilling.com/articles/19/view/?s=1 test template spreadsheet]]
	# entering one test at a time by filling in the fields for a "[[Testwork: Single result entry\|single test result]]";
			or
⚫	# ~~cutting~~ & ~~pasting~~ a table of values from a spreadsheet in a "[[testwork: Batch entry\|batch]]";
			* using a spreadsheet provided by you laboratory, insert a row above the table of results and insert the '''field names''' for a particular test.
	# cloning an existing test result (won't be available until some values are entered that can be cloned).
			then
		⚫	* cut & paste a table of values from the spreadsheet in a "[[testwork: Batch entry\|batch]]";

	===Test Types===		===Test Types===
Line 36:		Line 38:

	===Summary table, "All" results===		===Summary table, "All" results===
			// IN PROGRESS //
	[[file:Testwork-Summary.png\|thumb\|Screenshot of example listing of test values available for different samples]]
	The summary table of "All" results shows the listing of significant test results against the sample names. This provides a quick reference to check which samples contain sufficient test results to operate a model or to check for misspellings of sample names or programs. In order for a sample to properly match across the different tests, the sample name must be spelled identically in all the different testwork tables.		The summary table of "All" results shows the listing of significant test results against the sample names. This provides a quick reference to check which samples contain sufficient test results to operate a model or to check for misspellings of sample names or programs. In order for a sample to properly match across the different tests, the sample name must be spelled identically in all the different testwork tables.

Line 42:		Line 44:

	===Queries Table===		===Queries Table===
			// IN PROGRESS //
	[[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 "[[Testwork: Queries\|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 "query" table for a Bond/Barratt model will show only those samples that have a [[Testwork: Crushing work index\|crushing work index]] (WiC), [[Testwork: Bond rod mill work index\|Bond rod mill work index]] (WiRM) and a [[Testwork: Bond ball mill work index\|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 list of samples that run through a circuit model is shown in the "[[Testwork: Queries\|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 "query" table for a Bond/Barratt model will show only those samples that have a [[Testwork: Crushing work index\|crushing work index]] (WiC), [[Testwork: Bond rod mill work index\|Bond rod mill work index]] (WiRM) and a [[Testwork: Bond ball mill work index\|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.

Alex Doll at 23:27, 5 December 2013

2013-12-05T23:27:14Z

← Older revision		Revision as of 23:27, 5 December 2013
Line 1:		Line 1:
	[[Category:Howto]]		[[Category:Howto]]
	[[Category:Testwork]]		[[Category:Testwork]]
			==Access Level==
			Anyone with 'user' access level <u>and</u> who has been set by an administrator to have 'read/write' access to a project will be able to enter test results for that project.

			Users with 'read' access will be able to view test results, but not edit them or add new results. Contact your administrator if you need access to edit or add test results.


	==Entering Test Results==		==Entering Test Results==
	[[File:BlankProject.png\|thumb\|Screenshot of a blank newly created project]]		[[File:BlankProject.png\|thumb\|Screenshot of a blank newly created project]]

	A newly created project will require entry of test results before circuit models may be created and run. To enter test results, click the "~~See~~ Testwork ~~results~~" link.		A newly created project will require entry of test results before circuit models may be created and run. To enter test results, click the "Testwork" link.

	The testwork page consists of a series of links to the ~~individual~~ pages for storing different types of test results. It will first show a summary of all the results that have been entered — but since no test results are entered, the ~~summary~~ ~~says~~ ~~"No results found.~~".		The testwork page consists of a series of links to the test pages for storing different types of test results. It will first show a summary of all the test programs and available types of test results that have been entered — but since no test results are entered, the list will be blank".

	===General Concepts===		===General Concepts===
	The testing program should collect a series of samples corresponding to a particular interval of drill core, mine bench or some other reasonably uniform composite. Each sample will then have a series of tests conducted on it depending on which model (or models) are intended to be run. In order to properly index and organize the databases, each sample must have the following:		The testing program should collect a series of samples corresponding to a particular interval of drill core, mine bench or some other reasonably uniform composite. Each sample will then have a series of tests conducted on it depending on which model (or models) are intended to be run. In order to properly index and organize the databases, each sample must have the following:
		⚫	[[File:Testwork-NewProgram.png\|thumb\|Screenshot of entering a new testwork Program]]
		⚫	* '''Program''': Used to group tests that were all part of the same batch of testing. Often this is denoted by the date of testing, lab name or part of the orebody that was being examined. An example Program name is
			[[File:Testwork-NewProgram.png\|thumb\|Screenshot of entering a new testwork Program]]
	* '''Sample''': Sample name that is unique within a project. This can be a number, a drillhole number:from-to interval, or any other unique identifier. The same sample name will be used in all the tests in order to tell the database that "this is the same sample" when it goes looking to gather information.		* '''Sample''': Sample name that is unique within a project. This can be a number, a drillhole number:from-to interval, or any other unique identifier. The same sample name will be used in all the tests in order to tell the database that "this is the same sample" when it goes looking to gather information.
⚫	* '''Program''': Used to group tests that were all part of the same batch of testing. Often this is denoted by the date of testing, lab name or part of the orebody that was being examined.

	The database will only match samples (across the different tests) if both the '''Sample''' and '''Program''' entries are ''identical''. Enter these two values with care, otherwise the database won't be able to gather together the required tests for modelling, and samples will be missed from any calculations.		The database will only match samples (across the different tests) if both the '''Sample''' and '''Program''' entries are ''identical''. Enter these two values with care, otherwise the database won't be able to gather together the required tests for modelling, and samples will be missed from any calculations.
Line 23:		Line 31:

	===Test Types===		===Test Types===
⚫	[[File:Testwork-~~NoResults~~.png\|thumb\|Screenshot of ~~testwork~~ ~~table~~ ~~with~~ ~~no values~~ ~~entered~~]]
	Click on the link of the type of test that you want to enter date for. The abbreviations (on the list of links) for the different tests are:		Click on the link of the type of test that you want to enter date for. The abbreviations (on the list of links) for the different tests are:

Alex Doll: /* Queries Table */

2013-02-03T20:46:24Z

Queries Table

← Older revision		Revision as of 20:46, 3 February 2013
Line 36:		Line 36:
	===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 "query" table for a Bond/Barratt model will show only those samples that have a [[Testwork: Crushing work index\|crushing work index]] (WiC), [[Testwork: Bond rod mill work index\|Bond rod mill work index]] (WiRM) and a [[Testwork: Bond ball mill work index\|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 list of samples that run through a circuit model is shown in the "[[Testwork: Queries\|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 "query" table for a Bond/Barratt model will show only those samples that have a [[Testwork: Crushing work index\|crushing work index]] (WiC), [[Testwork: Bond rod mill work index\|Bond rod mill work index]] (WiRM) and a [[Testwork: Bond ball mill work index\|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 "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.

Alex Doll: /* Laboratory names */

2013-01-28T22:36:06Z

Laboratory names

← Older revision		Revision as of 22:36, 28 January 2013
Line 39:		Line 39:

	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.

	===Laboratory names===
	The laboratory where a test was conducted can be recorded with each sample. This is generally used for quality-control duplicate purposes in large testwork programs.

	The list of laboratory names is pre-populated with a number of laboratories whose results have been used in model calibration during the development of SAGMILLING.COM. The listing of labs is accessible via the "+" button at the top of every set of testwork. This "+" button option "Show lab listing" brings up the list.

	The listing can be modified the same as any testwork value. Clicking the "id" button will allow a row to be edited, and new entries can be added using the "Enter New Result" link at the bottom of the list.

← Older revision		Revision as of 18:59, 25 April 2014
Line 12:		Line 12:
	A newly created project will require entry of test results before circuit models may be created and run. To enter test results, click the "Testwork" link.		A newly created project will require entry of test results before circuit models may be created and run. To enter test results, click the "Testwork" link.

	The testwork page consists of a series of links to the test pages for storing different types of test results. It will first show a summary of all the test programs and available types of test results that have been entered — but since no test results are entered, the list will be blank".		The testwork page consists of a series of links to the test pages for storing different types of test results. It will first show a summary of all the test programs and available types of test results that have been entered — but since no test results are entered, the list will be blank.

	===General Concepts===		===General Concepts===
	The testing program should collect a series of samples corresponding to a particular interval of drill core, mine bench or some other reasonably uniform composite. Each sample will then have a series of tests conducted on it depending on which model (or models) are intended to be run. In order to properly index and organize the databases, each sample must have the following:		The testing program should collect a series of samples corresponding to a particular interval of drill core, mine bench or some other reasonably uniform composite. Each sample will then have a series of tests conducted on it depending on which model (or models) are intended to be run. In order to properly index and organize the databases, each sample must have the following:
	[[File:Testwork-NewProgram.png\|thumb\|Screenshot of entering a new testwork Program]]		[[File:Testwork-NewProgram.png\|thumb\|Screenshot of entering a new testwork Program]]
	* '''Program''': Used to group tests that were all part of the same batch of testing. Often this is denoted by the date of testing, lab name or part of the orebody that was being examined. Example Program names are '2013', 'west extension' or 'infill'.		* '''[[Testwork Program\|Program]]''': Used to group tests that were all part of the same batch of testing. Often this is denoted by the date of testing, lab name or part of the orebody that was being examined. Example Program names are '2013', 'west extension' or 'infill'.
	[[File:Testwork-NewSample.png\|thumb\|Screenshot of dialogue to create new samples]]		[[File:Testwork-NewSample.png\|thumb\|Screenshot of dialogue to create new samples]]
	* '''Sample''': Sample name that is unique within a project. This can be a number, a drillhole number:from-to interval, or any other unique identifier. The same sample name will be used in all the tests in order to tell the database that "this is the same sample" when it goes looking to gather information.		* '''Sample''': Sample name that is unique within a project. This can be a number, a drillhole number:from-to interval, or any other unique identifier. The same sample name will be used in all the tests in order to tell the database that "this is the same sample" when it goes looking to gather information.
Line 26:		Line 26:

	===Entering a batch of test results===		===Entering a batch of test results===
	* download the [[https://sagmilling.com/articles/19/view/?s=1 test template spreadsheet]]		* download the [[https://www.sagmilling.com/articles/19/view/?s=1 test template spreadsheet]]
	or		or
	* using a spreadsheet provided by you laboratory, insert a row above the table of results and insert the '''field names''' for a particular test.		* using a spreadsheet provided by you laboratory, insert a row above the table of results and insert the '''field names''' for a particular test.
Line 39:		Line 39:

	===Summary table, "All" results===		===Summary table, "All" results===
		⚫	The summary table of "All" results shows the listing of significant test results against the sample names. This provides a quick reference to check which samples contain sufficient test results to operate a model.
	// IN PROGRESS //
⚫	The summary table of "All" results shows the listing of significant test results against the sample names. This provides a quick reference to check which samples contain sufficient test results to operate a model ~~or to check for misspellings of sample names or programs~~. ~~In order for a sample to properly match across the different tests, the sample name must be spelled identically in all the different testwork tables.~~

	This summary table is automatically generated and can not be manually edited. In order to adjust a value in this table, it is necessary to modify the individual testwork pages.		This summary table is automatically generated and can not be manually edited. In order to adjust a value in this table, it is necessary to modify the individual testwork pages.