-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[CodeCamp2023-369] Adding support for FastComposer #2011
Conversation
demo 示例 python mmagic\demo\mmagic_inference_demo.py --model-name deblurganv2 --model-comfig ../configs/deblurganv2/deblurganv2_fpn_inception.py --model-ckpt 权重文件路径 --img 测试图片路径 --device cpu --result-out-dir ./out.png
fix CI test
fix CI test
fix CI test
update model-index
Fix CI Test
CI test fix and update readme.md
fix CI test and update readme.md
Fix CI test
yapf 修正
代码调整,参数名保持一致
doc string coverage
add some doc string
add some doc string
add unit test
add unit test
add unit test
fix unit test
fix a bug
Codecov ReportPatch coverage is
📢 Thoughts on this report? Let us know!. |
change for minimum version cpu check
avoid a windows CI bug which complains not enough memory.
rerun circleci check
@liuwenran Hi, I followed your advice and made the changes, but the CI test on minimum_version_cpu still complains out of the memory. Could it be because I loaded a CLIP image encoder model? |
yes, try not to use "clip_vit_url = 'openai/clip-vit-large-patch14' ", maybe change it to vit base or smaller clip resnet50 model |
add example code which run without gradio to readme add config of clip for running unittest without using "clip_vit_url = 'openai/clip-vit-large-patch14' "
rerun checks of build cu102
a small change
some small changes
add some simple instructions to demo/README.md
resolve conflicts
rerun checks
Hi @liuwenran ,requested changes were completed. |
add device for running with cuda by default
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution bro!
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist
Submitting this pull request means that,
Before PR:
After PR: