YIF

Thanks for your attention. We will try our best to solve your problem, but more concrete information is necessary for reproducing your problem.The problem you mentioned has a lot to...

@Mobu59 @GuanLinHu Sorry I haven't reproduced your problem yet, but if there is no problem with the data, it may be caused by multi-threading and deadlock： maybe you can try:OMP_NUM_THREADS=1...

Maybe you can try ‘ls + data-path' to verify the absolute path that is correct？Judging from the current problem, it should still be the problem that the path is not...

Thanks for your attention! We are trying to reproduce your error. Before that, you also can try this solution: https://blog.csdn.net/weixin_35848967/article/details/120200055?spm=1001.2101.3001.6650.1&utm_medium=distribute.pc_relevant.none-task-blog-2%7Edefault%7ECTRLIST%7Edefault-1-120200055-blog-123645660.pc_relevant_multi_platform_whitelistv1_exp2&depth_1-utm_source=distribute.pc_relevant.none-task-blog-2%7Edefault%7ECTRLIST%7Edefault-1-120200055-blog-123645660.pc_relevant_multi_platform_whitelistv1_exp2&utm_relevant_index=2 Might be able to pinpoint your problem more clearly

Thanks for your contribution! We will verify and test the code as soon as possible.

Thanks for your suggestion! We will add structure comparison diagrams as soon as possible to help better understand yolov6.

Thanks for your attention! yolov6 does not completely occupy all graphics card resources during the training process, which is mainly due to the nature of pytorch. On the one hand,...