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

yolov5 train setting #11857

Closed
1 task done
Ellohiye opened this issue Jul 13, 2023 · 2 comments
Closed
1 task done

yolov5 train setting #11857

Ellohiye opened this issue Jul 13, 2023 · 2 comments
Labels
question Further information is requested Stale Stale and schedule for closing soon

Comments

@Ellohiye
Copy link

Search before asking

Question

Hello author! May I ask if you can spare a little time to read my message under this project. https://github.com/C1nDeRainBo0M/AGCA/issues/3 .
I try to improve the backbone of Yolov5 and add an attention mechanism to verify whether it is effective for small target objects.
When I was trying to use other plug-and-play attention mechanisms, such as CBAM, ECA, etc., I found that the model was initialized on the cpu at the beginning, and then when I started training, the model was deployed on the gpu. Since the inputs of these modules are all on the The first-level feature map has no other parameters, so it can run correctly.
But when I use this module, there is a parameter self.A0 that is always deployed on the GPU, so an error will be reported during initialization. However, after I deploy it on the CPU, there is no problem during initialization, but when the actual training starts, other parameters will be placed on the GPU, but A0 is still on the CPU, which makes the module unusable in the backbone. I asked the author who proposed the module, but the conclusion he told me was the training setting problem of Yolov5, so I would like to ask the author what do you think about this issue?
Thank you very much for your patience in reading my problem description and questioning process! Thank you so much and look forward to hearing from you!

Additional

No response

@Ellohiye Ellohiye added the question Further information is requested label Jul 13, 2023
@glenn-jocher
Copy link
Member

@Ellohiye hi there,

Thank you for reaching out to us with your question regarding the YOLOv5 project. We appreciate the effort you put into improving the backbone of YOLOv5 by adding an attention mechanism to test its effectiveness on small target objects.

Regarding your issue with initializing the model on the CPU and then deploying it on the GPU during training, we understand that you are encountering an error due to the self.A0 parameter being deployed on the CPU instead of the GPU. This inconsistency is causing the module to be unusable in the backbone.

While we are unable to provide direct support for modifications made to the YOLOv5 project, we recommend checking the training settings in YOLOv5 to ensure that all parameters are correctly deployed on the GPU during training. Additionally, we encourage you to continue discussing this issue with the author who proposed the attention module, as they may have further insights into the specific training setting problem you are facing.

We commend your dedication and enthusiasm in working on this project and hope you find a solution to your issue. If you have any other questions or need further assistance, please don't hesitate to ask.

Best regards,

@github-actions
Copy link
Contributor

👋 Hello there! We wanted to give you a friendly reminder that this issue has not had any recent activity and may be closed soon, but don't worry - you can always reopen it if needed. If you still have any questions or concerns, please feel free to let us know how we can help.

For additional resources and information, please see the links below:

Feel free to inform us of any other issues you discover or feature requests that come to mind in the future. Pull Requests (PRs) are also always welcomed!

Thank you for your contributions to YOLO 🚀 and Vision AI ⭐

@github-actions github-actions bot added the Stale Stale and schedule for closing soon label Aug 13, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested Stale Stale and schedule for closing soon
Projects
None yet
Development

No branches or pull requests

2 participants