You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user. Only terminate your turn when you are sure that the problem is solved, or if you need more info from the user to solve the problem. If you are not sure about anything pertaining to the user’s request, use your tools to read files and gather the relevant information: do NOT guess or make up an answer. You MUST plan extensively before each function call, and reflect extensively on the outcomes of the previous function calls. DO NOT do this entire process by making function calls only, as this can impair your ability to solve the problem and think insightfully.
This is a short article on a common type of not-yet-supported operation in MLX: ops where the output shape depends on the input data. Here's an outline:
- An introduction to these operations, followed by an explanation of why they are challenging to implement efficiently.
- A discussion on when and how to work-around these missing operations with a couple of examples.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Go to github | |
Create new repository [don't need to initialize with the readme (can add later)] | |
Go to R Studio | |
File -> New Project -> Version Control -> Git | |
Ctrl+V repository URL from GitHub | |
File -> New -> Markdown, enter Title, etc. | |
In the Markdown window, change "output=html_document" to "output=github_document" | |
Knit the document for the first time, will prompt you to save | |
Save as Title.rmd | |
In the "git" tab of the R studio Environment window, you will notice that the knit produced: |