enable ops to support span #4
Open
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
|
Clarification: chainner does not work to convert span pytorch models to ncnn, you would need to use a script like https://github.com/TNTwise/SPAN-ncnn-vulkan/blob/master/export_span_spandrel.py |
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 is from my fork, https://github.com/TNTwise/SPAN-ncnn-vulkan/tree/master. Span can offer faster render times, while beating even some transformer-based super resolution architectures, and is similar in psnr to SwinIR. It works fine with ncnn, as long as some ops are enabled within ncnn. The models in the span repo should just work with upscayl after these changes, and can be exported with some versions of chainner nightly, https://github.com/chaiNNer-org/chaiNNer-nightly/releases/tag/2024-04-07.