No speed difference between sparsities #3
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.
Thanks for your great work!
I have some trouble running tests with your code, but I could not submit any issues so I'm leaving messages here...
Q1: When I ran
test.sh
on cityscapes dataset, it gave me the warning:what does it mean?
Q2: There is no speed difference between sparsities. I noticed you had implemented
soft_to_channel_sparse
ininject.py
, and I think it is used to convert masked convs to sparse normal ones, which have fewer flops. Could you tell me how to use it to boot inference at runtime?Thanks in advance.