py-ballisticcalc
py-ballisticcalc copied to clipboard
o-murphy
LGPL library for small arms ballistic calculations based on point-mass (3 DoF) plus spin drift.
In the case of multiple winds: `TrajectoryCalc` assumes that `Shot.winds[]` is sorted by `Wind.until_distance` (ascending). However right now we do not enforce that or even check whether that assumption is...
## Files * DragTable: list of {Mach: Cd} pairs sorted by Mach ascending * Weapon: [sight_height], [twist], [zero_elevation] * Ammo: \, \, [powder_temp, temp_modifier] *Problems:* 1. API expects Ammo to...
* make the opperations with raw values available * add an arithmetic support between units of the same type and between different unit types| * make the arithmetic operations to...
I think we can use somethink like [readthedocs](https://docs.readthedocs.io/en/stable/tutorial/) or [pdoc3](https://github.com/pdoc3/pdoc)
The goal of the pull request is to refactor the TrajectoryData class to reduce confusing terms so: distance >> x height >> y look_distance >> distance drop_adj >> drop_angle windage_adj...
As shown in [this discussion](https://github.com/o-murphy/py-ballisticcalc/discussions/75#discussioncomment-10162647), we should try to improve the clarity and accessibility between *look_distance* and *horizontal distance*. Per [this discussion](https://github.com/o-murphy/py-ballisticcalc/discussions/74#discussioncomment-9937546) we should either switch the signs on "adjustments"...