Closed nghiadanh26 closed 4 years ago
Relates to this issue.
@nghiadanh26 thanks for opening this PR, I took a look at the changes.
While it does run significantly faster, I am hesitant to pursue this further at the moment as it seems your changes alter the results a non-negligible amount versus the results from the original paper.
The below plot shows the LoOP values calculated for a set of values from the original paper.
The file examples/multiple_gaussian_2d.py
can be used to create a plot very similar to that provided in the original work, which can be used as a check to ensure that the PyNomaly implementation is as close to the original work as possible. When using the current PyNomaly code, we get the following result:
And using the code in this PR:
It looks like your proposed changes would increase the difference between the results provided from PyNomaly versus those from the original work. Do you think you would be able to identify the cause of this increased error in the results when compared to the original work?
Hi @vc1492a, Thanks for looking at my code. I understood your consideration, but now I cannot answer why the differences between PR's results and original results are non-negligible. I'll go deeper inside my code and also LoOP algorithm and I hope I can explain it soon.
Any updates @nghiadanh26?
Not yet. But I will be soon!
Any updates @nghiadanh26? I'd close to close this PR soon if there isn't a plan to explore the above, thanks!
Closing this PR and issue #38 due to inactivity and not resolving the above concern (discrepancy with original paper).
Updated my code to loop.py, including a function name "distance_dn" to calculate distance_matrix and "distance_point_dn" calculate distance from a point to training data. Added some time.time() functions to estimate time for my code.