fixing cost scaling for gurobi active set (to make consistent with fastqp/gurobiQP)
don't draw the terrain in PlanarRigidBodyVisualizer unless it's appropriate.
removing obsolete atlas example scripts
Merge pull request #122 from kuindersma/remove-old-atlas-examples

removing obsolete atlas example scripts
Merge pull request #118 from kuindersma/fix-gurobi-cost-scaling

fixing cost scaling for gurobi active set
Merge branch 'master' of https://github.com/RobotLocomotion/drake
moved Hubo to dev dir
disable xfoil plotting.  less verbose output in rigidbodywing preprocessing
update known issues, and point them to github
try to fail gracefully for minimal distros
Implement the MATLAB version of FootStepConstraint, will work on C++ implementation
Rename 'FootStepConstraint' to 'FootStepRegionConstraint'
Move the commits from drc sandbox to drake. Almost finished the P step of the bilinear alternation
P step is numerically correct. Need to add some kinematic constraint on the distance between CoM and the contact points, so that the contact position makes sense
add a function addKinematicPolygon in the P step to encode the relative position between contact bodies. Will need to work on RelativeFootPositionPolygon to specify such position constraint
RelativeFOotPositionPolygon is implemented to encode the polygonal constraint on the foot location w.r.t the other foot
P step supports a polygonal region constraint on the xy position between contact bodies
Start to work on the 'F-step' of the bilinear alternation. But I will take a step backward and add the time as decision variables in the formulation first
P-step uses less internal storage for the FootStepRegionContactConstraint
P-step now accepts time scaling as input of the optimization