You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not all pipelines set feature_columns in the pipeline config, specifically the ransomware_detection and abp_pcap_detection examples don't set these.
When we run these with their associated run.py script this isn't a problem, however using the equivalent CLI command the default features for the FIL pipeline are logged (the nvsmi features).
I think we have two options:
Simply don't log the config.fil.feature_columns and config.ae.feature_columns.
Re-work these examples to populated the config.
Personally I like option 1
Minimum reproducible example
No response
Relevant log output
No response
Full env printout
No response
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
The text was updated successfully, but these errors were encountered:
…plete (#983)
The CLI command for the FIL pipeline set a default value for `--columns_file` flag but some FIL pipelines like ransomeware didn't use this config property, causing the default columns file to be loaded and for the values to be logged to the terminal.
* Removed default values for `--columns_file` and `--labels-file` flags
* Removed redundant checks for null values if they were already being enforced by `required=True`
* Fix raised exception when using click auto-complete
* Misc pylint/flake8 errors
fixes#984fixes#819
Authors:
- David Gardner (https://github.com/dagardner-nv)
Approvers:
- Michael Demoret (https://github.com/mdemoret-nv)
- Pete MacKinnon (https://github.com/pdmack)
URL: #983
Version
23.03
Which installation method(s) does this occur on?
Docker, Conda, Source
Describe the bug.
Not all pipelines set
feature_columns
in the pipeline config, specifically theransomware_detection
andabp_pcap_detection
examples don't set these.When we run these with their associated
run.py
script this isn't a problem, however using the equivalent CLI command the default features for the FIL pipeline are logged (the nvsmi features).I think we have two options:
config.fil.feature_columns
andconfig.ae.feature_columns
.Personally I like option 1
Minimum reproducible example
No response
Relevant log output
No response
Full env printout
No response
Other/Misc.
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: