Updating CRAFT-pytorch to work with torchvision version 0.17.2.#215
Open
purvi1508 wants to merge 3 commits into
Open
Updating CRAFT-pytorch to work with torchvision version 0.17.2.#215purvi1508 wants to merge 3 commits into
purvi1508 wants to merge 3 commits into
Conversation
The code is not running due to the newer version of PyTorch, so it has been updated to be compatible with the latest version.
The code has been updated to use CUDA only if it is available; otherwise, it will fall back to using the CPU.
wkpark
added a commit
to wkpark/CRAFT-pytorch
that referenced
this pull request
Mar 5, 2025
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
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.
The code has been updated to be compatible with the latest version of PyTorch, as it was previously not running due to version compatibility issues. Additionally, the code has been modified to automatically use CUDA if it's available; otherwise, it will default to using the CPU for inference. These changes ensure better device compatibility and optimized performance based on the hardware.