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
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
This commit is a good example of adding implementation for a operator on one or more backends.
A rough instruction -
add a new file (if it doesn't exist) under lib/ops/ for the operator, implement an abstract class derived from Operator with member function initialize, checkInputs and checkInputTypes. Operator attributes are usually put here too.
add a new file under lib/backends/webgl/ops/ for the operator, implement a class that extends the abstract class described in (1) and implement interface WebGLOperator as well.
function run usually implement as calling WebGLOperatorHelper.run(), unless a custom step is required
function createProgramInfo returns the shader and layout
function createRunData returns the texture data and uniform binding (if any)
add resolve rules in /lib/backends/webgl/op-resolve-rules.ts for the newly implemented operator.
add standard node test or custom operator test in unittest-whitelist.jsonc.
Hi, @fs-eire Thanks for your response.
I wanted to know how to do tests. There are .pd files I guess generated from TensorFlow.
I was wondering if we can generate the same from Pytorch?
How would that look like?
Please provide a short guide on how to write ops.
The text was updated successfully, but these errors were encountered: