In Deeploy, we use the following IRs:
- In the Frontend:
- The GS Graph
- The
NetworkContext
- In the Midend:
- The GS Graph
- The
NetworkContext
- In the Backend:
- The
NetworkContext
- The
ExecutionBlock and CodeTransformer of each Layer from the LayerBinding
It seems to me that the location of the source of truth is not always very clear, especially in the Backend. For instance, the ONNXLayer from the layerBinding carries the gs.Node, the NodeParser (through the mapper), the NodeTemplate (through the binder), the CodeTransformation, and the ExecutionBlock.
Would it be possible to "freeze" some attributes at some stages of the flow, forbidding or warning a user to modify or use them?
In Deeploy, we use the following IRs:
NetworkContextNetworkContextNetworkContextExecutionBlockandCodeTransformerof each Layer from theLayerBindingIt seems to me that the location of the source of truth is not always very clear, especially in the Backend. For instance, the
ONNXLayerfrom thelayerBindingcarries thegs.Node, theNodeParser(through themapper), theNodeTemplate(through thebinder), theCodeTransformation, and theExecutionBlock.Would it be possible to "freeze" some attributes at some stages of the flow, forbidding or warning a user to modify or use them?