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
In order to integrate the exported app/pipeline to other applications, it is better to include the input and output information like pipeline.graph.input and pipeline.graph.output.
3. Accepts I/O
Accepting input and output for the built app/pipeline.
4. A flag with if packaging models into the output or not.
We support a very big xxx.pipeline file.
Or a file structure like:
XXX.pipeline
model_a.onnx
model_b.tensorrt
A Proposal
Maybe having Input and Output Component.
For example:
self.c1=Input("c1", shape=(B,))
self.t1=Input("t1", shape=(B, 3))
self.t2=Input("t2", shape=(B, 3))
self.stack=stack("stack")
self.out=Output("o", shape=None)
self.c1>>self.stack.inputs.dimself.t1>>self.stack.inputs.tensors.select(0)
self.t2>>self.stack.inputs.tensors.select(1)
self.stack.outputs.out>>self.outpipeline=Pipeline()
pipeline.add_nodes([c1, t1, t2, stack, show])
pipeline.save("mypipeline.pipeline")
# Adding some ONNX-ish APIspipeline.graph.input# returns [c1, t1, t2] and their shapespipeline.graph.output# returns [o] and its shapeout=pipeline.exec([torch.tensor([0.]), np.array([[1, 2, 3.]]), ...])
The text was updated successfully, but these errors were encountered:
That's an interesting feature. Is there any detail for how to implement this feature?
Not so complex if all the classes are serializable. It is more or less a pickle file only. Well, since maybe some model files are involved, we may also append those ONNX files into the pickle object.
An ideal feature but not sure if it is better for
app
orpipeline
. A proper save/load can make the limbus serve as ONNX.1. Save and Load
Requesting a feature to export/save and import/load a built
Pipeline
.Format Candidates:
Then one can load and use with
2. Input/Output Information
In order to integrate the exported app/pipeline to other applications, it is better to include the input and output information like
pipeline.graph.input
andpipeline.graph.output
.3. Accepts I/O
Accepting input and output for the built app/pipeline.
4. A flag with if packaging models into the output or not.
We support a very big xxx.pipeline file.
Or a file structure like:
A Proposal
Maybe having
Input
andOutput
Component.For example:
The text was updated successfully, but these errors were encountered: