Update the thrustcurves from the latest Thrustcurve.org data. This
corrects some of the case information.
Fixes#888
Signed-off-by: Billy Olsen <billy.olsen@gmail.com>
some common (but generally not important) errors in thrustcurves, and
not enter thrustcurves that will cause simulation failures into the
database.
(1) Permits thrustcurves to start at time 0 with a nonzero thrust.
Previous code inserted a datapoint with time 0 and thrust 0; this
caused thrust interpolation code to fail while running a simulation.
If the first datapoint is at a time greater than 0 it does enter a
(0, 0) datapoint, as this is the correct documented behavior for RASP
files.
(2) Permits thrustcurves to end with a nonzero thrust. Similarly to
the previous case, the old code entered a new datapoint at the same
time as the previous end of thrust with thrust 0, which would break
thrust interpolation.
(3) Thrustcurves that have a zero-thrust datapoint and a non-zero
thrust datapoint at time 0 have the first datapoint removed.
(4) Thrustcurves with more serious errors -- mainly multiple thrusts
at a single time -- aren't entered into the database, as they will
break thrust interpolation and there is no obvious way to guess which
of the datapoints is correct, or to see how to average them.
availability flag provided by Thrustcurve.org. Change serialization
process to pull current files from Thrustcurve.org using the xml api,
use the corrected data for diameter and length, and use a consistent
motor designation. Added fields to the Motor chooser - case info is a
column in the listing (replacing MotorType), the other info is in the
motor details tab. Added toggle to hide motors which are OOP.
