Add flag to omit timestamp in output directory #253
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What is this PR?
Why is this PR needed?
At the moment each run of the command
detect-and-track
will generate a timestamped directory for the outputs (csv with detections and optionally frames and tracked video).If we use a bash script to run this command over a set of videos (as we do in the cluster, see #251), we create one timestamped output directory per video, which is inconvenient and confusing.
An easy way to put all outputs from a set of videos under the same directory is to optionally remove the timestamp suffix that is applied by default to each output directory.
What does this PR do?
prep_outputs
method of the tracker classReferences
Another option could be for the user to be responsible of specifying the full path to the output directory. This is covered in #246. I opted for this option for now, to keep in line with the model evaluation script and the
save_frames
andframes_output_dir
flags, but this can be reviewed in the future.How has this PR been tested?
Tests pass locally and in CI.
Does this PR require an update to the documentation?
A comment about the new flag has been added to the README.
Checklist: