Lightning-AI / Lightning-AI/lightning-thunder

Move from interpret_trace->transform->construct_trace to working with traces directly

Open
#1,138 4 comments 0 reactions 1 assignee View on GitHub

@t-vi is already working on this.

Since Sep 16, 2024.

transforms
Dominant language
Python
Stars
1.5k
Forks
121
PR merge metrics
No merged PRs in 30d

Description

The autocast and gradient-related transforms use

interpret_trace->transform->construct_trace

this drops information, e.g. tags on the proxies.
So this issue is making them work with the traces directly.

My idea here is NOT to stop calling symbols but to construct the new trace closer to where we do.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.