Lawrence Kincheloe Contract2 - Revision history

Elifarley: Reverted edits by Elifarley (talk) to last revision by Chris F

2013-07-02T22:35:03Z

Reverted edits by Elifarley (talk) to last revision by Chris F

← Older revision		Revision as of 22:35, 2 July 2013
Line 130:		Line 130:
	1. Dediated Project Visit Proposal - https://docs.google.com/Doc?docid=0AR6t4DF2HZ9aZGRrd3NtdzdfMTEwaGZiaGg4Nzg&hl=en&pli=1		1. Dediated Project Visit Proposal - https://docs.google.com/Doc?docid=0AR6t4DF2HZ9aZGRrd3NtdzdfMTEwaGZiaGg4Nzg&hl=en&pli=1

	2. FeF Position Statement - [[Factor_e_Farm_Position_Statement		2. FeF Position Statement - http://openfarmtech.org/index.php?title=Factor_e_Farm_Position_Statement

	3.~~\|]]~~OSE Specifications - [[OSE_Specifications		3. OSE Specifications - http://openfarmtech.org/index.php?title=OSE_Specifications

	4.~~\|]]~~Neosubsistence - [[Neosubsistence		4. Neosubsistence - http://openfarmtech.org/index.php?title=Neosubsistence

	5.~~\|]]~~This contract - [[Lawrence_Kincheloe_Contract2		5. This contract - http://openfarmtech.org/index.php?title=Lawrence_Kincheloe_Contract2

	6.~~\|]]~~Wiki work page - [[Torch_Table_Build		6. Wiki work page - http://openfarmtech.org/index.php?title=Torch_Table_Build

	7.~~\|]]~~Last months contract - [[Lawrence_Kincheloe_Contract		7. Last months contract - http://openfarmtech.org/index.php?title=Lawrence_Kincheloe_Contract

	=Disclaimer=		=Disclaimer=

	If~~\|]]~~you find the above considerations of the FeF experiment overwhelming or unsavory, then you may want to look for a different project. We need to be clear about this point from the start, because the FeF experiment imposes well-defined requirements on its participants. We feel that if you are not aligned clearly with our operational principles, then conflict will be likely to occur as a result. Our goal is to serve the common good, and unnecessary conflict gets in the way of our goal.		If you find the above considerations of the FeF experiment overwhelming or unsavory, then you may want to look for a different project. We need to be clear about this point from the start, because the FeF experiment imposes well-defined requirements on its participants. We feel that if you are not aligned clearly with our operational principles, then conflict will be likely to occur as a result. Our goal is to serve the common good, and unnecessary conflict gets in the way of our goal.

	=Signatures=		=Signatures=

Elifarley: Text replace - "http:\/\/openfarmtech\.org\/index\.php\?title=([^] |])[ |]([^]])" to "$2"

2013-07-02T22:21:25Z

Text replace - "http:\/\/openfarmtech\.org\/index\.php\?title=([^] |]*)[ |]([^]]*)" to "$2"

← Older revision		Revision as of 22:21, 2 July 2013
Line 130:		Line 130:
	1. Dediated Project Visit Proposal - https://docs.google.com/Doc?docid=0AR6t4DF2HZ9aZGRrd3NtdzdfMTEwaGZiaGg4Nzg&hl=en&pli=1		1. Dediated Project Visit Proposal - https://docs.google.com/Doc?docid=0AR6t4DF2HZ9aZGRrd3NtdzdfMTEwaGZiaGg4Nzg&hl=en&pli=1

	2. FeF Position Statement - ~~http://openfarmtech.org/index.php?title=~~Factor_e_Farm_Position_Statement		2. FeF Position Statement - [[Factor_e_Farm_Position_Statement

	3. OSE Specifications - ~~http://openfarmtech.org/index.php?title=~~OSE_Specifications		3.\|]]OSE Specifications - [[OSE_Specifications

	4. Neosubsistence - ~~http://openfarmtech.org/index.php?title=~~Neosubsistence		4.\|]]Neosubsistence - [[Neosubsistence

	5. This contract - ~~http://openfarmtech.org/index.php?title=~~Lawrence_Kincheloe_Contract2		5.\|]]This contract - [[Lawrence_Kincheloe_Contract2

	6. Wiki work page - ~~http://openfarmtech.org/index.php?title=~~Torch_Table_Build		6.\|]]Wiki work page - [[Torch_Table_Build

	7. Last months contract - ~~http://openfarmtech.org/index.php?title=~~Lawrence_Kincheloe_Contract		7.\|]]Last months contract - [[Lawrence_Kincheloe_Contract

	=Disclaimer=		=Disclaimer=

	If you find the above considerations of the FeF experiment overwhelming or unsavory, then you may want to look for a different project. We need to be clear about this point from the start, because the FeF experiment imposes well-defined requirements on its participants. We feel that if you are not aligned clearly with our operational principles, then conflict will be likely to occur as a result. Our goal is to serve the common good, and unnecessary conflict gets in the way of our goal.		If\|]]you find the above considerations of the FeF experiment overwhelming or unsavory, then you may want to look for a different project. We need to be clear about this point from the start, because the FeF experiment imposes well-defined requirements on its participants. We feel that if you are not aligned clearly with our operational principles, then conflict will be likely to occur as a result. Our goal is to serve the common good, and unnecessary conflict gets in the way of our goal.

	=Signatures=		=Signatures=

Chris F: /* See Also */

2011-09-27T19:06:35Z

Chris F at 19:06, 27 September 2011

2011-09-27T19:06:20Z

← Older revision		Revision as of 19:06, 27 September 2011
Line 4:		Line 4:
	'''September 26, 2009'''		'''September 26, 2009'''

			=Overview=
			{{Torch Table}} Development Contract

	=Introduction=		=Introduction=
Line 155:		Line 157:



			=See Also=
			[[Torch Table]]

	[[Category:Lawrence Kincheloe]][[Category:Contracts]]		[[Category:Lawrence Kincheloe]][[Category:Contracts]]

Lawrence: /* Other Considerations */

2009-09-30T18:18:56Z

Other Considerations

← Older revision		Revision as of 18:18, 30 September 2009
Line 106:		Line 106:

	12. There shall be no illegal activity at FeF. Participants are expected to abide by the FeF [[Rules of Conduct]]		12. There shall be no illegal activity at FeF. Participants are expected to abide by the FeF [[Rules of Conduct]]

			13. RD will make good on paying in full the traffic ticket Dev received while fallowing RD back to FeF.

	=Entry and Exit Policy=		=Entry and Exit Policy=

WikiSysop: /* Documentation */

2009-09-27T14:27:12Z

Documentation

← Older revision		Revision as of 14:27, 27 September 2009
Line 35:		Line 35:
	=Documentation=		=Documentation=

	1. 3 blog posts are the minimum requirement. The initial blog shall contain an introduction and proposal. The second blog post shall contain a progress update, as well as crowd funding basket, if needed. The final post, to be published prior to leaving FeF unless otherwise agreed upon, should cover video documentation of the build and other noteworthy results relevant to the FeF Position Statement.		1. 3 blog posts are the minimum requirement. The initial blog shall contain an introduction and proposal. The second blog post shall contain a progress update, as well as crowd funding basket, if needed. The final post, to be published prior to leaving FeF unless otherwise agreed upon, should cover video documentation of the build and other noteworthy results relevant to the FeF Position Statement. Given the ongoing explorations of an open source business model, this model must be communicated in one of the blog posts.

	2. ~~The~~ final blog post must contain video ~~document ation~~ of the build process, showing the important steps for viewers' education. See examples of hardware builds on the blog. In this particular case, computer, controller, and software setup are as important to document as the hardware build.		2. Either the final blog post or earlier post must contain video documentation of the build process, showing the important steps for viewers' education. See examples of hardware builds on the blog. In this particular case, computer, controller, and software setup are as important to document as the hardware build.

	3. Dev will maintain and update the [[Torch Table Build]] wiki page.		3. Dev will maintain and update the [[Torch Table Build]] wiki page.

WikiSysop: /* Entry and Exit Policy */

2009-09-27T14:16:23Z

Entry and Exit Policy

← Older revision		Revision as of 14:16, 27 September 2009
Line 111:		Line 111:
	1. If Dev is not re-invited to apply for a third month contract, then he has one day from October 28 to leave FeF. It is understood that Dev has a ready option to pursue if things don't work out at FeF.		1. If Dev is not re-invited to apply for a third month contract, then he has one day from October 28 to leave FeF. It is understood that Dev has a ready option to pursue if things don't work out at FeF.

	2. At the discretion of either party, this one month contract may be canceled at any time. An agreed upon exit time or one day, whichever is longest, will be given to gather his belongings.		2. At the discretion of either party, this one month contract may be canceled at any time. An agreed upon exit time or one day, whichever is longest, will be given to gather his belongings. Upon early termination, Dev must document his latest work for reasons of project continuity.

	=License and Copyright=		=License and Copyright=

WikiSysop: /* Scope of Project */

2009-09-27T14:12:28Z

Scope of Project

← Older revision		Revision as of 14:12, 27 September 2009
Line 22:		Line 22:
	To keep on track of the FeF experiment, the minimum acceptable performance of the project will be as follows. It is to be understood that this represents the bare minimum to be considered a successful Project Visit and in no way represents the full list of considered tasks. Furthermore it will be understood that mitigating circumstances may change the scope of the project, at which such times the Research Director and the Developer will modify the scope of the project or cancel the contract. A signed affidavit will attest to these changes agreed upon by both parties.		To keep on track of the FeF experiment, the minimum acceptable performance of the project will be as follows. It is to be understood that this represents the bare minimum to be considered a successful Project Visit and in no way represents the full list of considered tasks. Furthermore it will be understood that mitigating circumstances may change the scope of the project, at which such times the Research Director and the Developer will modify the scope of the project or cancel the contract. A signed affidavit will attest to these changes agreed upon by both parties.

	1. Align the Prototype I table in the x, y, and z directions to 1/16" accuracy.		#Align the Prototype I table in the x, y, and z directions to 1/16" accuracy.
			#Demonstrate level of accuracy of x, y, and z motion over the full range of motion of Prototype I by performing and documenting a series of tests from g-code files.
	2. Demonstrate ~~acceptable~~ level of accuracy of x, y, and z motion over the full range of motion of Prototype I.		#Publish at least some key test files to test replicability by Research Director.
			#Characterize Prototype I with regards to accuracy and precision at varying speeds and configurations.
	3. Characterize Prototype I with regards to accuracy and precision at varying speeds and configurations.		#Attach torch head to Prototype I.
			#Demonstrate that slightly over sized 1/2" holes can be torched out on 1 inch centers in a 12" piece of 2"x2"x1/4" square tubing.
	3. Attach torch head to Prototype I.		#Demonstrate that 4 such pieces laid out on the far corners of the table can be torched out successfully to within 1/16" accuracy. #Demonstrate the same as the last point with 1", 16 gauge square tubing, but using 3/8", slightly oversized holes.
			#Compose and publish g-code and procedure for torching out the gantry of Prototype II which incorporates improvements made in Prototype I.
	4. Demonstrate that slightly over sized 1/2" holes can be torched out on 1 inch centers in a 12" piece of 2"x2"x1/4" square tubing.		#Develop a business proposal that takes into account work from the last month for the purpose of bringing the project to product release.
			#Document work as specified in "Documentation".
	5. Demonstrate that 4 such pieces laid out on the far corners of the table can be torched out successfully to within 1/16" accuracy.

	6. Demonstrate the same with 1", 16 gauge square tubing, but using 3/8", slightly oversized holes.

	7. Compose and publish g-code and procedure for torching out the gantry of Prototype II which incorporates improvements made in Prototype I.

	8. Develop a business proposal that takes into account work from the last month for the purpose of bringing the project to product release.

	9. Document work as specified in "Documentation".

	=Documentation=		=Documentation=

207.119.110.67: /* Scope of Project */

2009-09-26T21:17:21Z

Scope of Project

← Older revision		Revision as of 21:17, 26 September 2009
Line 22:		Line 22:
	To keep on track of the FeF experiment, the minimum acceptable performance of the project will be as follows. It is to be understood that this represents the bare minimum to be considered a successful Project Visit and in no way represents the full list of considered tasks. Furthermore it will be understood that mitigating circumstances may change the scope of the project, at which such times the Research Director and the Developer will modify the scope of the project or cancel the contract. A signed affidavit will attest to these changes agreed upon by both parties.		To keep on track of the FeF experiment, the minimum acceptable performance of the project will be as follows. It is to be understood that this represents the bare minimum to be considered a successful Project Visit and in no way represents the full list of considered tasks. Furthermore it will be understood that mitigating circumstances may change the scope of the project, at which such times the Research Director and the Developer will modify the scope of the project or cancel the contract. A signed affidavit will attest to these changes agreed upon by both parties.

	1. Align table in the x, y, and z directions to 1/16" accuracy.		1. Align the Prototype I table in the x, y, and z directions to 1/16" accuracy.

	2. Demonstrate acceptable level of accuracy of x, y, and z motion over the full range of motion of ~~the device~~. ~~Determine replicability and dependence on speed. Suggested procedure:~~		2. Demonstrate acceptable level of accuracy of x, y, and z motion over the full range of motion of Prototype I.

	*Determine maximum speed of travel in the x, y, and z directions.		3. Characterize Prototype I with regards to accuracy and precision at varying speeds and configurations.
	*Demonstrate minimum step size accuracy limit. Minimum Acceptable Performance (MAP) = 1/16". Suggested Procedure (SP): draw a 4 inch long zigzag in the xy plane, from about 1 inch size per line down to ~~the minimum step size.~~
	*Determine dependence of last step on motor speed. SP: run at different speeds at the accuracy ~~limit determined above - down to 1/25 of maximum speed,~~ and ~~oberve if zigzags change by overlaying consecutive zigzags.~~
	*Determine latency limits. SP: determine ability of table to draw curves at full motor speed by drawing a 1 foot diameter circle. Decrease motor speed until a perfect circle is attained. MAP - drawing a circle that closes upon itself and jaggedness of edges is no more than 1/16". Document motor speed required to attain this.
	*Determine limit of drawing curves. MAP: ability to draw a 3/8" circle. Document speed at which this circle can be drawn.
	*Demonstrate accuracy of table in maintaining accuracy over full length of travel. SP: Start at one corner of the table, and draw a 1/2" circle. Demonstrate replicability by moving away from the drawing to the opposite corner of the table, then returning, followed by redrawing the same pattern. MAP: 2 overlaid circles must line up to within 1/16"
	*Demonstrate compounding of errors over short distances. SP: draw a set of twelve 1/2" circles in a line, separated by 1/2". Then attempt to draw over the original circles, and document error. Determine whether error increases with the number of circles.
	*Demonstrate compounding of errors over long distances. SP: Same as last point, but Then move to the opposite corner, draw another set, and return. Then attempt to draw over the original circles, and ~~document resulting overlap errors~~.

	3. Attach torch head.		3. Attach torch head to Prototype I.

	4. ~~Evaluate final prototype fully. SP: demonstrate~~ that slightly ~~oversized~~ 1/2" holes can be torched out on 1 inch centers in a 12" piece of 2"x2"x1/4" square tubing. Demonstrate that 4 such pieces laid out on the far corners of the table can be torched out successfully to within 1/16" accuracy. Demonstrate the same with 1", 16 gauge square tubing, but using 3/8", slightly oversized holes.		4. Demonstrate that slightly over sized 1/2" holes can be torched out on 1 inch centers in a 12" piece of 2"x2"x1/4" square tubing.

	5. ~~Develop improvements into a new design~~ that ~~is fully constructible~~ on the ~~first Torch Table v1.~~		5. Demonstrate that 4 such pieces laid out on the far corners of the table can be torched out successfully to within 1/16" accuracy.
	*Publish dimensionally-correct improvements in a 3D Blender model
	*Compose and publish g-code and procedure for torching out the ~~gantry of Prototype II (x, y, and z components)~~
	*Torch out ~~Prototype II gantry~~
	*Assemble

	6. ~~Develop a business proposal that takes into account work from~~ the ~~last month for the purpose of bringing the project to product release~~.		6. Demonstrate the same with 1", 16 gauge square tubing, but using 3/8", slightly oversized holes.

	7. ~~Consult with Greg Pettengill on~~ improvements.		7. Compose and publish g-code and procedure for torching out the gantry of Prototype II which incorporates improvements made in Prototype I.

	7. Document work as specified in "Documentation".		8. Develop a business proposal that takes into account work from the last month for the purpose of bringing the project to product release.

			9. Document work as specified in "Documentation".

	=Documentation=		=Documentation=

WikiSysop: /* Scope of Project */

2009-09-26T19:19:41Z

Scope of Project

← Older revision		Revision as of 19:06, 27 September 2011
Line 159:		Line 159:

	=See Also=		=See Also=
	[[Torch Table]]		{{Torch Table}}

	[[Category:Lawrence Kincheloe]][[Category:Contracts]]		[[Category:Lawrence Kincheloe]][[Category:Contracts]]

← Older revision		Revision as of 19:19, 26 September 2009
Line 30:		Line 30:
	*Determine dependence of last step on motor speed. SP: run at different speeds at the accuracy limit determined above - down to 1/25 of maximum speed, and oberve if zigzags change by overlaying consecutive zigzags.		*Determine dependence of last step on motor speed. SP: run at different speeds at the accuracy limit determined above - down to 1/25 of maximum speed, and oberve if zigzags change by overlaying consecutive zigzags.
	*Determine latency limits. SP: determine ability of table to draw curves at full motor speed by drawing a 1 foot diameter circle. Decrease motor speed until a perfect circle is attained. MAP - drawing a circle that closes upon itself and jaggedness of edges is no more than 1/16". Document motor speed required to attain this.		*Determine latency limits. SP: determine ability of table to draw curves at full motor speed by drawing a 1 foot diameter circle. Decrease motor speed until a perfect circle is attained. MAP - drawing a circle that closes upon itself and jaggedness of edges is no more than 1/16". Document motor speed required to attain this.
	*Determine limit of drawing curves. MAP: ability to draw a 3/8" circle. Document speed at which ~~1/2"~~ circle can be drawn.		*Determine limit of drawing curves. MAP: ability to draw a 3/8" circle. Document speed at which this circle can be drawn.
	*Demonstrate accuracy of table in maintaining accuracy over full length of travel. SP: Start at one corner of the table, and draw a 1/2" circle. Demonstrate replicability by moving away from the drawing to the opposite corner of the table, then returning, followed by redrawing the same pattern. MAP: 2 overlaid circles must line up to within 1/16"		*Demonstrate accuracy of table in maintaining accuracy over full length of travel. SP: Start at one corner of the table, and draw a 1/2" circle. Demonstrate replicability by moving away from the drawing to the opposite corner of the table, then returning, followed by redrawing the same pattern. MAP: 2 overlaid circles must line up to within 1/16"
	*Demonstrate compounding of errors over short distances. SP: draw a set of twelve 1/2" circles in a line, separated by 1/2". Then attempt to draw over the original circles, and document error.		*Demonstrate compounding of errors over short distances. SP: draw a set of twelve 1/2" circles in a line, separated by 1/2". Then attempt to draw over the original circles, and document error. Determine whether error increases with the number of circles.
	*Demonstrate compounding of errors over long distances. SP: Same as last point, but Then move to the opposite corner, draw another set, and return. Then attempt to draw over the original circles, and document resulting overlap errors.		*Demonstrate compounding of errors over long distances. SP: Same as last point, but Then move to the opposite corner, draw another set, and return. Then attempt to draw over the original circles, and document resulting overlap errors.

Line 41:		Line 41:
	5. Develop improvements into a new design that is fully constructible on the first Torch Table v1.		5. Develop improvements into a new design that is fully constructible on the first Torch Table v1.
	*Publish dimensionally-correct improvements in a 3D Blender model		*Publish dimensionally-correct improvements in a 3D Blender model
	*Compose and publish g-code and procedure for torching out Prototype II		*Compose and publish g-code and procedure for torching out the gantry of Prototype II (x, y, and z components)
	*Torch out Prototype II		*Torch out Prototype II gantry
			*Assemble

	6. Develop a business proposal that takes into account work from the last month for the purpose of bringing the project to product release.		6. Develop a business proposal that takes into account work from the last month for the purpose of bringing the project to product release.

Lawrence Kincheloe Contract2 - Revision history

Elifarley: Reverted edits by Elifarley (talk) to last revision by Chris F

Elifarley: Text replace - "http:\/\/openfarmtech\.org\/index\.php\?title=([^] |]*)[ |]([^]]*)" to "$2"

Chris F: /* See Also */

Chris F at 19:06, 27 September 2011

Lawrence: /* Other Considerations */

WikiSysop: /* Documentation */

WikiSysop: /* Entry and Exit Policy */

WikiSysop: /* Scope of Project */

207.119.110.67: /* Scope of Project */

WikiSysop: /* Scope of Project */

Elifarley: Text replace - "http:\/\/openfarmtech\.org\/index\.php\?title=([^] |])[ |]([^]])" to "$2"