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
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 :)
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:
Thanks a lot
The text was updated successfully, but these errors were encountered: