We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
During calculation of sweep score, if the anomalyPoint is in the anomaly windows you divide by windowWidth (https://github.com/numenta/NAB/blob/master/nab/sweeper.py#L176) and if the anomalyPoint is outside the anomaly window, you divide by windowWidth - 1 (https://github.com/numenta/NAB/blob/master/nab/sweeper.py#L188) is there any reason for it or is it a bug?
The text was updated successfully, but these errors were encountered:
I agree that it seems strange to change the window width. In the window the position formula is
-(curWindowRightIndex - i + 1) / curWindowWidth
After the window the formula is
abs(prevWindowRightIndex - i) / float(prevWindowWidth - 1)
I doubt it makes an important difference to the scores.
Sorry, something went wrong.
No branches or pull requests
During calculation of sweep score, if the anomalyPoint is in the anomaly windows you divide by windowWidth (https://github.com/numenta/NAB/blob/master/nab/sweeper.py#L176) and if the anomalyPoint is outside the anomaly window, you divide by windowWidth - 1 (https://github.com/numenta/NAB/blob/master/nab/sweeper.py#L188) is there any reason for it or is it a bug?
The text was updated successfully, but these errors were encountered: