PaddlePaddle / PaddlePaddle/FastDeploy
Dynamic input shape model
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 756
- Avg merge
- 19h 28m
- Merged PRs (30d)
- 4
Description
Environment
FastDeploy version: 1.0.0
OS Platform: Windows x64
Hardware: CPU noavx
Program Language: C++
CMake: 3.18, 3.25
Visual Studio: 2019
Code
const std::string& model_file = "C:/modnet-resnet50_vd/model.pdmodel";
const std::string& params_file = "C:/modnet-resnet50_vd/model.pdiparams";
const std::string& config_file = "C:/modnet-resnet50_vd/deploy.yaml";
auto option = fastdeploy::RuntimeOption();
option.UsePaddleInferBackend();
option.UseCpu();
option.SetPaddleMKLDNN(false);
auto model = fastdeploy::vision::matting::PPMatting(model_file, params_file, config_file, option);
Problem description
console output:
1[WARNING] fastdeploy/vision/matting/ppmatting/ppmatting.cc(78)::fastdeploy::vision::matting::PPMatting::BuildPreprocessPipelineFromConfig
Detected dynamic input shape of your model, only Paddle Inference / OpenVINO support this model now.
I specified option.UsePaddleInferBackend();
Why is this model not supported. Should I use a different library?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the warning reported at fastdeploy/vision/matting/ppmatting/ppmatting.cc:78 and review how the PPMatting model is constructed with RuntimeOption and UsePaddleInferBackend(). Reproduce the Windows x64 CPU case using the model and configuration shown; done means determining why the selected backend reports the dynamic input shape as unsupported or documenting the limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100