Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Freezing Stale Attributes of the IR at Different Stage of the Flow #18

Open
Victor-Jung opened this issue Dec 2, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@Victor-Jung
Copy link
Member

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?

@Victor-Jung Victor-Jung added the enhancement New feature or request label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant