[BUG]: abp_nvsmi_detection doesn't detect any anomalous rows

[dagardner-nv]

Version

24.10

Which installation method(s) does this occur on?

Source

Describe the bug.

24.06 found 188 anomalous rows. I've reproduced this using triton launched from a 24.06 repo, which leads me to believe this is a code issue and not an issue with the model.

$ wc -l detections.jsonlines 
1242 detections.jsonlines
$ grep false detections.jsonlines | wc -l
1242

Minimum reproducible example

Follow example as documented
examples/abp_nvsmi_detection/README.md

Relevant log output

Click here to see error details

[Paste the error here, it will be hidden by default]

Full env printout

Click here to see environment details

[Paste the results of print_env.sh here, it will be hidden by default]

Other/Misc.

No response

Code of Conduct

• I agree to follow Morpheus' Code of Conduct
• I have searched the open bugs and have found no duplicates for this bug report

[dagardner-nv]

Results of the examples/abp_pcap_detection don't match 24.06 results (24.06 results match 24.03 results).

$ ./scripts/compare_data_files.py ../morpheus-24.06.01/pcap_out.jsonlines pcap_out.jsonlines 

Results do not match. Diff 437241/537241 (81.386380 %). First 10 mismatched rows:

[dagardner-nv]

log_parsing also yields mis-matched rows.
24.10 compared to 24.06 yields 96.8% yields
24.06 compared to 24.03 yields 2.6% yields