Skip to content

Conversation

@bkuker
Copy link
Contributor

@bkuker bkuker commented Feb 25, 2014

Tumble Drag Bugfix

A bug prevents the BasicTumbleStepper from ever calculating the drag, zero is always used.

Changes to Tumble Transition

  • Do not switch to the tumble stepper under thrust.
    • If a stage wants to switch to tumble under thrust emit a warning.
  • If a booster stage wants to tumble before apogee, let it.
  • If the sustainer wants to tumble, only allow it after apogee.
    • If the sustainer wants to tumble before apogee emit a warning.

Before / After Comparison of Flight Paths

Before this change the lower stages of the three stage example model all appear to follow a parabola without air resistance:

image

After this change they fall much slower, with much more influence from the wind:

image

These images are from some playing around I am doing with visualizing many simulations. Things worth knowing are:

  • The red dots on the ground are high speed impacts
  • The green dots are slow, soft landings
  • In the "After" image the fuchsia color is tumble recovery.
    • The "Before" image does not show tumble in fuchsia, but the lower stages do always begin to tumble just after apogee.

computeTumbleDrag() is never called without this fix.

The one-arg constructor is the only constructor ever used, to init this
status based on the previous status, copying the tumble drag if it can.

The first BasicTumbleStatus is constructed from an RK4 Status, so it's
drag is not copied, but neither is the drag computed. From then on the 0
is copied from one BasicTumbleStatus to the next.
kruland2607 pushed a commit that referenced this pull request Feb 25, 2014
Changes to Tumble Transition & Tumble Bug Fix
@kruland2607 kruland2607 merged commit bd62a1e into openrocket:master Feb 25, 2014
@bkuker bkuker deleted the tumble branch March 29, 2014 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants