SSScoring needs your bad jump files! Version 2.0.31 is out and features new functionality requested by ISC judges and has several minor bug fixes. The biggest change is in how speed accuracy is reported. A jump is declared invalid if the value of speed accuracy exceeds a threshold of 3.0. While SSScoring detected that condition and flagged the jump as invalid, there were no hints beyond an opaque banner. In this new version of the API and SSScore, the performance window and all the skydive data are displayed for analysis. SSScore now displays the ISC threshold (3.0 at this time) and plots the speed accuracy values in the speed graph. And here’s where I need your help: I have a very limited number of bad speed tracks. I’d appreciate if you could share with me any competition or training files that were flagged as bad, for any reason. If you know they blew the ISC speed accuracy threshold even better. I need a wider data sample to figure out the best way of plotting the “bad jumps” in a graph. This will help the application evaluators (and judges in the future) determine what and how something went wrong during the jump.
My very small dataset includes files that show exit altitudes > 16,000 ft, a very limited number of data rows, and speed accuracy values in excess of 25.0.
Looking forward to hearing from you, blue skies, and go fast!