Rust panic

[acpeakhour]

Rust panic

[sudiptoguha]

This is likely the same issue as #374

Would you be able to drop in the cut.rs from the current PR (just changing that one file should not affect anything else)? Or is this arising in the current PR itself? The current PR performs the check against the length.

[sudiptoguha]

And one of the main instigations for the new PR was to not have panics but at least enable the capability of propagating errors (but there are still ways to go in terms of messages and error details -- hopefully they can be handled iteratively)

[acpeakhour]

Amusingly, I just converted the logic from the Java version. I'll try your update.

The RCF v4 update is interesting, I'm trying to understand everything you are saying. We currently struggle with 10gb heap running many multi dimensional trcf's. The way I read that is that we can have a single forest handling many?

[sudiptoguha]

"we can have a single forest handling many" -> yes, with a price. If the time series are very different then precision/recall (measured via implanted anomalies) will reduce because the model can get confounded. This is ameliorated slightly based on the late detection (relative_index field) -- but again, mileage may vary.

[acpeakhour]

I get a new error now, could there be some dependent code elsewhere?

deleting wrong node; looking for 4511 found 5311
want 1.1760913 found 2.0043213
want 0 found 0
want 0 found 0
want 0 found 0
want 0.90309 found 0.69897
want 0 found 0
want 0 found 0
want 0 found 0
want 1.2787536 found 1.1760913
want 0 found 0
want 0 found 0
want 0 found 0
want 1.0791812 found 0.7781513
want 0 found 0
want 0 found 0
want 0 found 0
want 1.7160033 found 1.8129133
want 0 found 0
want 0 found 0
want 0 found 0
want 0.47712123 found 0.60206
want 0 found 0
want 0 found 0
want 0 found 0
want 1.6627579 found 1.6232493
want 0 found 0
want 0 found 0
want 0 found 0
want 0.845098 found 0.845098
want 0 found 0
want 0 found 0
want 0 found 0
thread panicked at 'explicit panic', deps/rcf/Rust/src/samplerplustree/randomcuttree.rs:222:17

[sudiptoguha]

What is happening is that the code is looking for (want) a specific value to delete and finding something else in that position
that explains "deleting wrong node; looking for 4511 found 5311. This would happen if the trees are corrupted (that is, violate the assumption that every point on left is less or equal in that splitting coordinate, and everything on right is greater). If the cut subroutine produces a cut that does not separate the bounding box into two parts (when called from the add subroutine), then the tree could get corrupted. Are you seeing this error using the restored check-pointed/serialized forests or from new ones?

[acpeakhour]

I upgraded to your rcfv4 branch. I'm pleased to report:

• no more crashes
• uses 1/3 of the heap
• runs significantly faster

well done.

[sudiptoguha]

Thanks and thanks for trying the new branch. I am happy that it worked for you.