You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tfjs is a JS version of TensorFlow, and successor to the experimental deeplearn.js. When WebGL is available, tfjs will accelerate operation using the GPU. tfjs has functions to create a tensor from a pixel source (with similar restrictions as texImage2D), and to create an image from a tensor.
I would like to combine it with three.js, e.g. to capture "sensory" data from three.js graphics and, conversely, augment three.js graphics with data from tfjs.
Do you think this library would be suitable for such communication, when the goal is increased performance? Or is it better to stick with communication through canvas textures?
The text was updated successfully, but these errors were encountered:
OK. Thanks. I may actually try it (or rather make some limited experiments with it). I suspect many small overheads from the virtualization will add up to something that may be just as bad as the expected overhead from communicating through canvas textures. But it would depend on the application. When (if) I have done some experiments, I will post an update here.
tfjs is a JS version of TensorFlow, and successor to the experimental deeplearn.js. When WebGL is available, tfjs will accelerate operation using the GPU. tfjs has functions to create a tensor from a pixel source (with similar restrictions as
texImage2D
), and to create an image from a tensor.I would like to combine it with three.js, e.g. to capture "sensory" data from three.js graphics and, conversely, augment three.js graphics with data from tfjs.
Do you think this library would be suitable for such communication, when the goal is increased performance? Or is it better to stick with communication through canvas textures?
The text was updated successfully, but these errors were encountered: