[Opal-commits] opal todo.txt,1.54,1.55

[tylerstreeter <tyl...@us...>]

Update of /cvsroot/opal/opal
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23596

Modified Files:
	todo.txt 
Log Message:
added VelocitySensor and AccelerationSensor

Index: todo.txt
===================================================================
RCS file: /cvsroot/opal/opal/todo.txt,v
retrieving revision 1.54
retrieving revision 1.55
diff -C2 -d -r1.54 -r1.55
*** todo.txt	13 Mar 2005 23:07:12 -0000	1.54
--- todo.txt	14 Mar 2005 05:18:28 -0000	1.55
***************
*** 3,9 ****
  
  * additional sensors
! 	- vel, accel, incline/orientation; relate these to vestibular senses?
  
! * sensors
  	- parse from xml
  	- add to xml example
--- 3,11 ----
  
  * additional sensors
! 	- incline/orientation relative to an initial orientation
  
! * finish implementing accel and vel sensors
! 
! * accel and vel sensors:
  	- parse from xml
  	- add to xml example
***************
*** 12,15 ****
--- 14,27 ----
  	- add to Blueprint addSensor function
  
+ * implement sensors
+ 	- RaycastSensor (i.e. "PSD (position sensitive detector)" or "rangefinder"): measures distance from sensor to first intersection (attach to a solid [be sure to ignore collisions with the attached solid] or nothing)
+ 		- not updated regularly; must be updated manually by user
+ 	- VolumeSensor (i.e. "proximity sensor?"): similar to RaycastSensor, but for a volume; finds all Solids colliding with a given (attached) Solid
+ 		- not updated regularly; must be updated manually by user
+ 		- should this be combined with trigger solids?  probably not: ProximitySensors are one-time, triggers are always updated (triggers are actually just solids with a ContactSensor and don't generate contact joints)
+ 	- VelocitySensor: linear vel (i.e. "velocimeter") and/or angular vel ("gyroscope") sensor
+ 	- AccelerationSensor (i.e. "accelerometer"): linear and/or angular acceleration sensor
+ 	- InclineSensor (i.e. "inclinometer"): measures angle between initial and current orientation
+ 
  * make trimeshes work
  
***************
*** 28,41 ****
  	- called at the start of a time step
  
- * implement sensors
- 	- RaycastSensor (i.e. "PSD (position sensitive detector)" or "rangefinder"): measures distance from sensor to first intersection (attach to a solid [be sure to ignore collisions with the attached solid] or nothing)
- 		- not updated regularly; must be updated manually by user
- 	- VolumeSensor (i.e. "proximity sensor?"): similar to RaycastSensor, but for a volume; finds all Solids colliding with a given (attached) Solid
- 		- not updated regularly; must be updated manually by user
- 		- should this be combined with trigger solids?  probably not: ProximitySensors are one-time, triggers are always updated (triggers are actually just solids with a ContactSensor and don't generate contact joints)
- 	- VelocitySensor: linear vel (i.e. "velocimeter") and/or angular vel ("gyroscope") sensor
- 	- AccelerationSensor (i.e. "accelerometer"): linear and/or angular acceleration sensor
- 	- InclineSensor (i.e. "inclinometer"): measures angle between initial and current orientation
- 
  * dynamic number of contact joints?
  	- depends on types of objects
--- 40,43 ----