6c535bff94
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.
2 lines
47 B
Plaintext
2 lines
47 B
Plaintext
Error: Unable to access jarfile OpenRocket.jar
|