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

Different optimization traces & optim on a shared code #17

Open
doxav opened this issue Nov 15, 2024 · 1 comment
Open

Different optimization traces & optim on a shared code #17

doxav opened this issue Nov 15, 2024 · 1 comment
Assignees

Comments

@doxav
Copy link
Contributor

doxav commented Nov 15, 2024

Is it possible to support different traces & optimization on shared functions/nodes using decorators ? What would be the best practice ?

In my case, I need to do different traces & optimization on shared code files/functions:

  • within each of my LLM agents.
  • in a workflow involving all my different agents
  • in a workflow involving 2 of my agents (overlapping the one above and one below)
  • in a workflow involving 3 of my agents (overlapping the two above)

Thanks a lot

@chinganc
Copy link
Collaborator

Good question! In Trace, you can have multiple optimizers (each attends to separate parameters). The paths where those parameter are used can be shared. After calling backward, each optimizer will receive their respective minimal subgraph.

Is this what you meant? It will be helpful if you can help clarify your scenario. E.g.,

Do you mean using different optimizers for different parameters?
Do you mean optimizing them in different frequencies?
Do different traces touch on shared parameters/

I think it will be most clear if you can write down a toy example of such a case, so I can better help :)

@chinganc chinganc self-assigned this Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants