This repository was archived by the owner on Feb 29, 2024. It is now read-only.
Fallback to predefined_classes in yolo_io #882
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Use default predefined_classes.txt if folder contains no classes.txt.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
1 participant
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.
Currently the program stops if I try to open a folder which does not contain a classes.txt (in yolo mode). I think it could be a nice addition to just use the default predefined_classes.txt in case that no classes.txt can be found. The first save creates an exact copy of predefined_classes.txt inside the current folder as classes.txt. So it only really affects the first time a folder is opened.