-
Notifications
You must be signed in to change notification settings - Fork 3
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
Config Registry #130
Merged
Merged
Config Registry #130
Conversation
This file contains 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
|
Additional Functionalities:
Register a custom config:
|
tobiasfshr
approved these changes
Aug 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request aims to close #128 and create a simpler way to resolve config files.
It allows the user to specify a config in the CLI using different ways:
Provide the path to the config file:
-
vis4d [train|test] --config /absolute/path/to/file<.py|.yaml>
-
vis4d [train|test] --config relative/path/to/file<.py|.yaml>
Per default, the framework will try to match these files to an existing config file at the specified absolute or relative location.
If the file does not exist, it will try to resolve the relative path in the vis4d zoo folder.
If the file is still not found, a "did you mean,..." message will be displayed with the closest matching configs, if any exist.
Provide the short name of a zoo config:
The existing configs in the zoo folder can be easily accessed by providing the model name. E.g.
-
vis4d [train|test] --config faster_rcnn_r50_1x_bdd100k
If the file does not exist, a did you mean message will be created:
Example:
vis4d train--config faster_rcnn_50r_x_bdd100k