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 May 31, 2024. It is now read-only.
That would turn the graph into a gorgonia exprgraph by walking the graph starting from the input and creating the node accordingly.
Example. Assume an equation y = a * x + b that would produce this graph:
y -> add
add -> mul
add -> b
mul -> a
mul -> x
properly encoded into a Weighted Graph.
The ToExprGraph would then walk the graph (still have to figure out how to efficiently walk the graph) and create:
a:=gorgonia.NodeFromAny(aT) // aT is already a tensor.Tensorx:=gorgonia.NodeFromAny(xT) // ...// ...m:=gorgonia.Must(gorgonia.Mul(a,x))
add:= gorgonia.Must(gorgonia.Add(m. b)
Do you get the drill?
What do you think?
The text was updated successfully, but these errors were encountered:
For the POC, Gorgonia has been heavily tweaked to fit the gonum's GraphBuilder interface.
The tweaked version has been vendored as an example. This leads to a maintenance problem.
It's merely impossible to add new features to the backend.
The Gorgonia team is working on a significant refactor of the API.
Meanwhile, I am considering rewriting the Gorgonia backend to use the actual API.
My idea is to use something similar to what I did with
gorgonnx
some time ago.We can create a simple
GorgoniaGraph
in the backend fulfilling the interfaces:gonum.WeightedGraphBuilder
OperationCarrier
TensorCarrier
and then a method
That would turn the graph into a gorgonia exprgraph by walking the graph starting from the input and creating the node accordingly.
Example. Assume an equation
y = a * x + b
that would produce this graph:properly encoded into a Weighted Graph.
The
ToExprGraph
would then walk the graph (still have to figure out how to efficiently walk the graph) and create:Do you get the drill?
What do you think?
The text was updated successfully, but these errors were encountered: