dfp_integrated_training_batch_pipeline.py appears to be ignoring the --start_time flag.
Passing in --start_time "2022-08-08" still yields this output:
Preprocessed 102 data logs in 2022-08-02T00:37:03.000000000 to 2022-08-02T23:30:48.000000000 in 224.7006893157959 ms
Preprocessed 100 data logs in 2022-08-03T00:01:48.000000000 to 2022-08-03T23:58:52.000000000 in 193.61233711242676 ms
Preprocessed 102 data logs in 2022-08-02T00:37:03.000000000 to 2022-08-02T23:30:48.000000000 in 224.7006893157959 ms
Preprocessed 100 data logs in 2022-08-03T00:01:48.000000000 to 2022-08-03T23:58:52.000000000 in 193.61233711242676 ms
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
[X] I agree to follow Morpheus' Code of Conduct
[X] I have searched the open bugs and have found no duplicates for this bug report
Version
24.06
Which installation method(s) does this occur on?
Source
Describe the bug.
dfp_integrated_training_batch_pipeline.py
appears to be ignoring the--start_time
flag.Passing in
--start_time "2022-08-08"
still yields this output:Minimum reproducible example
Relevant log output
Click here to see error details
Full env printout
Click here to see environment details
Other/Misc.
No response
Code of Conduct