Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

detect.py - images always saved #2029

Closed
taqpoly2 opened this issue Jan 24, 2021 · 3 comments
Closed

detect.py - images always saved #2029

taqpoly2 opened this issue Jan 24, 2021 · 3 comments
Labels
bug Something isn't working Stale Stale and schedule for closing soon

Comments

@taqpoly2
Copy link

Hello, thanks for this incredible tool.

It seems that in detect.py save_img is always set to True - the piece of code in this piece of code.below is default
Btw It would be nice to have option to switch saving images in script call like detect.py --saveimages. Thanks.

Set Dataloader

vid_path, vid_writer = None, None
if webcam:
    view_img = True
    cudnn.benchmark = True  # set True to speed up constant image size inference
    dataset = LoadStreams(source, img_size=imgsz)
else:
    save_img = True
    dataset = LoadImages(source, img_size=imgsz)
@taqpoly2 taqpoly2 added the bug Something isn't working label Jan 24, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Jan 24, 2021

👋 Hello @taqpoly2, thank you for your interest in 🚀 YOLOv5! Please visit our ⭐️ Tutorials to get started, where you can find quickstart guides for simple tasks like Custom Data Training all the way to advanced concepts like Hyperparameter Evolution.

If this is a 🐛 Bug Report, please provide screenshots and minimum viable code to reproduce your issue, otherwise we can not help you.

If this is a custom training ❓ Question, please provide as much information as possible, including dataset images, training logs, screenshots, and a public link to online W&B logging if available.

For business inquiries or professional support requests please visit https://www.ultralytics.com or email Glenn Jocher at glenn.jocher@ultralytics.com.

Requirements

Python 3.8 or later with all requirements.txt dependencies installed, including torch>=1.7. To install run:

$ pip install -r requirements.txt

Environments

YOLOv5 may be run in any of the following up-to-date verified environments (with all dependencies including CUDA/CUDNN, Python and PyTorch preinstalled):

Status

CI CPU testing

If this badge is green, all YOLOv5 GitHub Actions Continuous Integration (CI) tests are currently passing. CI tests verify correct operation of YOLOv5 training (train.py), testing (test.py), inference (detect.py) and export (export.py) on MacOS, Windows, and Ubuntu every 24 hours and on every commit.

@glenn-jocher
Copy link
Member

@taqpoly2 thanks for the feedback, we will take it into consideration. The current settings are mainly to demo the inference capability, with the assumption that users will customize to their own needs as appropriate.

You might also want to see YOLOv5 PyTorch Hub inference as an alternative to detect.py, this provides much greater customizability (and images are not saved by default there):
https://github.com/ultralytics/yolov5#pytorch-hub

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale Stale and schedule for closing soon label Feb 24, 2021
@github-actions github-actions bot closed this as completed Mar 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Stale Stale and schedule for closing soon
Projects
None yet
Development

No branches or pull requests

2 participants