Version 2.1 addresses a minor bug that occurred when the probability of the predicted R value for 1-2 and 3-5 was the same but very small (e.g. 1%). This brings up a problem with a lot of APIs that I work with. They are not well documented. It's easy to call the API and see what the returned fields are, but often I don't know all of the possible values that those fields can have. This was one of those cases. I had considered doing more error checking on the predicted R value, but having a predicted value of R be 1% for R1/2 and also 1% for R3/5 made no sense to me. The code was modified to handle these fringe cases better.
?
73,
Scott
AK5SD
?
?
Scott Dupuie