-
Notifications
You must be signed in to change notification settings - Fork 212
refactor: improve Nx.Defn.Evaluator debugging usability #1644
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
Conversation
…omparison between nodes (see save_as documentation). Created a backend_comparison.livemd file to document comparison between backends for the evaluator. Added the backend_comparison and complex_fft to the mix.exs file
| * **Arguments** - List containing parameters and tensors as strings | ||
| * **Result** - Executable code that reconstructs the output tensor from binary | ||
|
|
||
| ## Verifying Executability |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of a separate section, I think this could just be a ### header on the Examining the Output Files section
…tput Files' and the code now just uses
Chapaman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now the Verifying Executability section is within Examining the Output Files and the code now just uses Code.eval_file()
Changes
evaluator.exto produce.exsfiles that can be executed for comparison between nodes (see save_as documentation).Creates a
backend_comparison.livemdfile to document comparison between backends for the evaluator.Adds the
backend_comparisonandcomplex_fftto themix.exsfile