Running glide on a per sbd/tbd pair may have been misguided, because it assumed complete profiles. I have noticed incomplete profiles in some of the RIOT data, usually from the upper portion of the climb. The causes profinder to throw an error (I am not sure why).
I am leaning towards a different approach to generating the erdapp data - running over the combined sbd/tbd to avoid this issue.
Running glide on a per sbd/tbd pair may have been misguided, because it assumed complete profiles. I have noticed incomplete profiles in some of the RIOT data, usually from the upper portion of the climb. The causes profinder to throw an error (I am not sure why).
I am leaning towards a different approach to generating the erdapp data - running over the combined sbd/tbd to avoid this issue.