2015:Programming - Revision history

Programming: remove useless lights section

2015-04-26T18:36:13Z

remove useless lights section

← Older revision		Revision as of 11:36, 26 April 2015
Line 1:		Line 1:
	~~== Lights! ==~~

	*Goal: state signaling
	*Current probably viable plan:
	**On driver command, lights flash white
	**Horizontal Light strip on top brace of lifter (back only):
	***Match gripper position (single L-R bar, with value 0 to 1), with green horizontal progress-bar-thingy
	***Use red to off gradient from corresponding side when the gripper is at end of travel
	***Add a blue component to lights when tote is (measured) present
	**Identical vertical light strips on sides of lifter elevator (probably top 1/3rd of lifter, back only):
	***Match lifter position with green vertical progress-bar-thingy
	***Use red to off gradient again as end of travel warning
	***When brakeing, change progress bar to yellow
	***Broken sensors have a red progress bar
	***It turns blue when it is at the requested height
	**Use Adafruit Neopixel light strips, controlled by Arduino Micro
	**(Net cost ~$100)

	== Google Docs ==		== Google Docs ==

Programming at 22:11, 7 February 2015

2015-02-07T22:11:54Z

← Older revision		Revision as of 15:11, 7 February 2015
Line 39:		Line 39:
	== Programming Sub-pages and Links ==		== Programming Sub-pages and Links ==

			*[[2015:Autonomous\|2015:Autonomous]]
	*Documentation		*Documentation
	**[http://wpilib.screenstepslive.com/s/4485 WPILib_Screensteps]		**[http://wpilib.screenstepslive.com/s/4485 WPILib_Screensteps]

Programming at 20:38, 6 February 2015

2015-02-06T20:38:10Z

← Older revision		Revision as of 13:38, 6 February 2015
Line 1:		Line 1:
	== Lights! ==		== Lights! ==

			*Goal: state signaling
	*Current probably viable plan:		*Current probably viable plan:
	**On driver command, lights flash white		**On driver command, lights flash white
	**Light strip on top of lifter (back only):		**Horizontal Light strip on top brace of lifter (back only):
	***Match gripper position (single L-R bar, with value 0 to 1), with green horizontal progress-bar-thingy		***Match gripper position (single L-R bar, with value 0 to 1), with green horizontal progress-bar-thingy
	***Use red to off gradient from corresponding side when the gripper is at end of travel		***Use red to off gradient from corresponding side when the gripper is at end of travel
	***Add a blue component to lights when tote is (measured) present		***Add a blue component to lights when tote is (measured) present
	**Identical light strips on sides (probably top 1/3rd of lifter, back only):		**Identical vertical light strips on sides of lifter elevator (probably top 1/3rd of lifter, back only):
	***Match lifter position with green vertical progress-bar-thingy		***Match lifter position with green vertical progress-bar-thingy
	***Use red to off gradient again as end of travel warning		***Use red to off gradient again as end of travel warning
Line 13:		Line 14:
	***Broken sensors have a red progress bar		***Broken sensors have a red progress bar
	***It turns blue when it is at the requested height		***It turns blue when it is at the requested height
			**Use Adafruit Neopixel light strips, controlled by Arduino Micro
			**(Net cost ~$100)

	== Google Docs ==		== Google Docs ==

Programming: add possible lights

2015-02-06T19:14:58Z

add possible lights

← Older revision		Revision as of 12:14, 6 February 2015
Line 1:		Line 1:
			== Lights! ==

			*Current probably viable plan:
			**On driver command, lights flash white
			**Light strip on top of lifter (back only):
			***Match gripper position (single L-R bar, with value 0 to 1), with green horizontal progress-bar-thingy
			***Use red to off gradient from corresponding side when the gripper is at end of travel
			***Add a blue component to lights when tote is (measured) present
			**Identical light strips on sides (probably top 1/3rd of lifter, back only):
			***Match lifter position with green vertical progress-bar-thingy
			***Use red to off gradient again as end of travel warning
			***When brakeing, change progress bar to yellow
			***Broken sensors have a red progress bar
			***It turns blue when it is at the requested height

	== Google Docs ==		== Google Docs ==

Programming: link fix (no more redirect on SVN)

2015-02-03T16:01:07Z

link fix (no more redirect on SVN)

← Older revision		Revision as of 09:01, 3 February 2015
Line 11:		Line 11:
	[http://tom.preston-werner.com/2009/05/19/the-git-parable.html Introduction to Git]		[http://tom.preston-werner.com/2009/05/19/the-git-parable.html Introduction to Git]

			[http://stackoverflow.com/questions/tagged/c++-faq?page=1&sort=votes&pagesize=300 C++FAQ on Stackoverflow]

			*A list of questions, some of which explain things you'll want to know (pointers, const, and memory), others which you don't (prvalues, lambda, SFINAE)

	[http://~~stackoverflow~~.com/~~questions~~/~~tagged~~/c++-faq~~?page=1&sort=votes&pagesize=300 C++FAQ on Stackoverflow~~]		Reading all of [http://www.parashift.com/c++-faq-lite/index.html http://www.parashift.com/c++-faq-lite/index.html] takes a while as well, but helps

	*A list of questions, some of which explain things you'll want to know (pointers, const, and memory), others which you don't (prvalues, lambda, SFINAE)
	*Reading all of [http://www.parashift.com/c++-faq-lite/index.html http://www.parashift.com/c++-faq-lite/index.html] takes a while as well, but helps
	*Caveat: Just because fancy techniques exist doesn't mean you should use them		*Caveat: Just because fancy techniques exist doesn't mean you should use them

Line 33:		Line 33:
	*SVN (up to 2013)		*SVN (up to 2013)
	**[[SVN Setup]]		**[[SVN Setup]]
	**[http://www.svn.penfieldrobotics.com/ Online browsing of our ~~<span data-scaytid="2" data-scayt_word="SVN">~~SVN~~</span>~~ Tree]		**[http://www.svn.penfieldrobotics.com/viewvc/viewvc.cgi/ Online browsing of our SVN Tree]
	*[[Jaguar Firmware Notes]]		*[[Jaguar Firmware Notes]]
	*[[2015:Robot IO Map]]		*[[2015:Robot IO Map]]

Programming: reshuffle

2015-02-03T15:53:59Z

reshuffle

← Older revision		Revision as of 08:53, 3 February 2015
Line 11:		Line 11:
	[http://tom.preston-werner.com/2009/05/19/the-git-parable.html Introduction to Git]		[http://tom.preston-werner.com/2009/05/19/the-git-parable.html Introduction to Git]

	~~[http://www.stack.nl/~dimitri/doxygen/manual/commands.html Doxygen Comment Rules]~~

	[http://stackoverflow.com/questions/tagged/c++-faq?page=1&sort=votes&pagesize=300 C++FAQ on Stackoverflow]		[http://stackoverflow.com/questions/tagged/c++-faq?page=1&sort=votes&pagesize=300 C++FAQ on Stackoverflow]
Line 22:		Line 22:

	*Documentation		*Documentation
	**[http://wpilib.screenstepslive.com/s/4485 ~~Screensteps~~]		**[http://wpilib.screenstepslive.com/s/4485 WPILib_Screensteps]
	**[http://first.wpi.edu/FRC/roborio/release/docs/cpp/annotated.html WPILib ~~Doxygen~~]		**[http://first.wpi.edu/FRC/roborio/release/docs/cpp/annotated.html WPILib documentation]
	*Doxygen		*Doxygen
	**Update~~<span style="font-size:small;">~~site:~~ <span style="font-family:times new roman,times,serif;">~~[http://download.gna.org/eclox/update http://download.gna.org/eclox/update]~~</span></span>~~		**[http://www.stack.nl/~dimitri/doxygen/manual/commands.html Doxygen Comment Rules]
			**Update site: [http://download.gna.org/eclox/update http://download.gna.org/eclox/update]
	*Git (2014 and beyond)		*Git (2014 and beyond)
	**[[Git Setup\|Git Setup]]		**[[Git Setup\|Git Setup]]

Programming: added doxygen update site

2015-01-31T15:52:21Z

added doxygen update site

← Older revision		Revision as of 08:52, 31 January 2015
Line 24:		Line 24:
	**[http://wpilib.screenstepslive.com/s/4485 Screensteps]		**[http://wpilib.screenstepslive.com/s/4485 Screensteps]
	**[http://first.wpi.edu/FRC/roborio/release/docs/cpp/annotated.html WPILib Doxygen]		**[http://first.wpi.edu/FRC/roborio/release/docs/cpp/annotated.html WPILib Doxygen]
			*Doxygen
			**Update<span style="font-size:small;">site: <span style="font-family:times new roman,times,serif;">[http://download.gna.org/eclox/update http://download.gna.org/eclox/update]</span></span>
	*Git (2014 and beyond)		*Git (2014 and beyond)
	**[[Git Setup\|Git Setup]]		**[[Git Setup\|Git Setup]]

Programming: rename section

2015-01-30T15:33:14Z

rename section

← Older revision		Revision as of 08:33, 30 January 2015
Line 1:		Line 1:
	== ~~Design Ideas~~ ==		== Google Docs ==

	[https://drive.google.com/folderview?id=0B-ZUOfYjCF0yTk1zSFNENWgtR0U&usp=drive_web 2015 Google Docs Folder]		[https://drive.google.com/folderview?id=0B-ZUOfYjCF0yTk1zSFNENWgtR0U&usp=drive_web 2015 Google Docs Folder]

Programming: add documentation

2015-01-30T15:32:22Z

add documentation

← Older revision		Revision as of 08:32, 30 January 2015
Line 21:		Line 21:
	== Programming Sub-pages and Links ==		== Programming Sub-pages and Links ==

			*Documentation
			**[http://wpilib.screenstepslive.com/s/4485 Screensteps]
			**[http://first.wpi.edu/FRC/roborio/release/docs/cpp/annotated.html WPILib Doxygen]
	*Git (2014 and beyond)		*Git (2014 and beyond)
	**[[Git Setup\|Git Setup]]		**[[Git Setup\|Git Setup]]

Programming at 22:44, 29 January 2015

2015-01-29T22:44:03Z

← Older revision		Revision as of 15:44, 29 January 2015
Line 11:		Line 11:
	[http://tom.preston-werner.com/2009/05/19/the-git-parable.html Introduction to Git]		[http://tom.preston-werner.com/2009/05/19/the-git-parable.html Introduction to Git]

	[[www.stack.nl/~dimitri/doxygen/manual/commands.html\|Doxygen Comment Rules]]		[http://www.stack.nl/~dimitri/doxygen/manual/commands.html Doxygen Comment Rules]

	[http://stackoverflow.com/questions/tagged/c++-faq?page=1&sort=votes&pagesize=300 C++FAQ on Stackoverflow]		[http://stackoverflow.com/questions/tagged/c++-faq?page=1&sort=votes&pagesize=300 C++FAQ on Stackoverflow]