compute capabilities by kushalkolar · Pull Request #1040 · fastplotlib/fastplotlib · GitHub
Conversation
…r can handle 'None' as placeholders in the selection
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
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.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.
Footer
You can’t perform that action at this time.
Starting to prototype the combination of compute and viz, making required modifications to fastplotlib that are required for this. Going to start with creating the basic things we need for masknmf viz. Will put actual compute + viz examples and implementations in https://github.com/kushalkolar/wgpu-linalg
Thoughts:
I think a full basic numpy-like API with .to("wgpu") and to_numpy() calls would be useful. We need TextureArray and all other data-features in fastplotlib to behave identical regardless of where the data is. For TextureArray this means we need the format as well, so dtype etc.