Closed dbookstaber closed 6 months ago
Implemented in https://github.com/dbookstaber/py_ballistics/commit/41025d0c2b6dcc8208916743c5eeec5f3f9e742e
Also fixed: get_calc_step()
was weird, taking the range distance step and applying a confusing function that would produce smaller calculation step sizes when running large TrajectoryData steps. Before the step size could go from as high as 0.5ft down to 0.1ft unexpectedly. Now it just ensures that we're running 0.25ft steps (half the Settings._MAX_CALC_STEP_SIZE
) unless a smaller value is explicitly requested.
Not quite there; changing to delta_time = calc_step / velocity
needs some other changes to work; had to roll back for now.
Current version of trajectory calculator takes time steps that are a function of
velocity.x
– typically thecalc_step
is 0.5ft, and:I.e., we change the time step so that each step advances 0.5ft along the x-axis. This will degrade accuracy when bullet is following high angles. Instead we should determine the time step by bullet speed – i.e.,
velocity_vector.magnitude()
– so that resolution does not depend on trajectory.