Refactor Reflection into Boundary
elykwilliams opened this issue · comments
Currently, the reflection is a part of the motion model class. This was done originally thinking that we simply call the update_point() function after the velocity had been updated.
In thinking forward, with #5 using only elastic collisions, this becomes a geometry problem and has nothing to do with the model of motion being used. We simply need the old_point, and new_point, to compute where the sensor should end up.
Ideally we will refactor the reflection to work for any boundary interface, but for now each boundary should implement their own reflection. Until it is fully refactored, we will be limited to elastic collision only.