search

dddvision / functionalnavigation

Trajectory Optimization Manager for Multiple Algorithms and Sensors (TOMMAS)
3 stars 4 forks source link

Should findEdges accept a trajectory input? #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
This input would make it possible to compute intercepts with path constraints.

The down side is that you would get a different set of edges for each given 
trajectory.

Original issue reported on code.google.com by dddvis...@gmail.com on 10 Jul 2010 at 12:35

GoogleCodeExporter commented 9 years ago 
A trajectory input has been added to findEdges, though the trajectory is not 
currently used within any components. This feature is experimental but stable, 
as long as no serious problems arise going forward.

Original comment by dddvis...@gmail.com on 5 Aug 2010 at 6:37