Closed BruceJohnJennerLawso closed 7 years ago
looks like a flaw in the axes setting code, its setting the same y min & max
traced the issue to the getGraphBounds function in graphtools. Looks like whenever the min & maxes of the dataset are within the value of snapToNearest of each other, the bounds get set as the same number
fixed it by having the function sanity check its results and adjust if it fucked up. Done as of fcfaf40e8428416ca1850ecaeae415b47d0e9500
Current example is
python teamStatGraph.py nhl postLockout False Defence ADQI
For some weird reason it is putting +9.99 at the bottom right corner and the axes range is really tiny, at 0.000 - 0.020