- Notifications
You must be signed in to change notification settings - Fork506
[feat] AutoLayoutModel and flexible model configs#69
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
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
Closed
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
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.
Uh oh!
There was an error while loading.Please reload this page.
After this update, layout-parser will provide more flexible ways of initializing the models and specifying the model configs:
New
AutoLayoutModelclass that supports the convenient loading of the models from different backends. There are several different ways of specifying the models:AutoLayoutModel("lp://<detector-name>/<dataset-name>/<model-arch>/config")will create a model of the<detector-name>backed using the"lp://<dataset-name>/<model-arch>/config".AutoLayoutModel("lp://<detector-name>/<dataset-name>/<model-arch>")is more concise: it works the same as the command above, while you don't need to specify theconfigin the input.AutoLayoutModel("lp://<detector-name>/<dataset-name>")will automatically find the corresponding<model-arch>for you as long as there are models trained for this dataset.Here are some examples:
lp.AutoLayoutModel("lp://efficientdet/PubLayNet/tf_efficientdet_d0/config")lp.AutoLayoutModel("lp://efficientdet/PubLayNet/tf_efficientdet_d0")lp.AutoLayoutModel("lp://efficientdet/PubLayNet")Similar level of flexibility is also supported for existing
LayoutModels:lp.XXLayoutModel("lp://<dataset-name>/<model-arch>/config")lp.XXLayoutModel("lp://<dataset-name>/<model-arch>")lp.XXLayoutModel("lp://<dataset-name>")