Quote:
Originally Posted by tuffspotz
I have a BU v BB sim srp, when I run a report on the turn probe node to see all turns, I notice the data in the report doesn't quite match the actual frequencies displayed if I load each turn individually (takes 30sec or so). The disparity is a bit larger than I am comfortable with. I ran my sim with the 'Medium storage (~8mB)' option. Is there a way to improve the accuracy of these turn reports?
If you use "Basic storage" or "Medium storage" then the turn reports will be calculated by the main solve. However, the turn data itself is not stored in these storage methods, and needs to be recalculated on the fly. As a result, the frequencies in the turn report and the frequencies from the recalc are from different solves, and it's possible for there to be differences in the frequencies.
If you want them to match exactly, the use "Extensive storage". Now, the turns are stored as well, and turn data does not need to be derived from on-the-fly recalcs.
That being said, the smaller dEV (or Nash distance) is for the main solve, the more accurate the frequencies in the turn reports will be. If you were to solve all the way to 0% then the frequencies should match exactly. For any value greater than 0% there will always be a difference; usually small, but in some cases it can appear to be signficant.