Filtering can now be performed on the GPU #32
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.
Filtering is now done on either the CPU or GPU depending on which template argument uses in the crfasrnn op. We have two partially specialized functors (one for GPU and one for CPU), which call their respective implementations. There seems to be some issue with using CUDA through tensorflow (tensorflow/tensorflow#18441) so we now directly link against cuda for the g++ stage and use some cuda macors to check results.
I have only tested that the output is the same as when run on CPU, and I only checked it with CUDA 9 and Tensorflow 1.7.