forked from pytorch/executorch
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add LLM subpages to navi (pytorch#5475)
Summary: Pull Request resolved: pytorch#5475 Reviewed By: guangy10 Differential Revision: D62992589 Pulled By: kirklandsign fbshipit-source-id: ddfa3aa4c034326cfc776dacc909335fe43b3071
- Loading branch information
1 parent
8ef6c79
commit 73244a9
Showing
18 changed files
with
19 additions
and
155 deletions.
There are no files selected for viewing
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
This file contains 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
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,141 +1,2 @@ | ||
| # ExecuTorch Llama Android Demo App | ||
|
|
||
| We’re excited to share that the newly revamped Android demo app is live and includes many new updates to provide a more intuitive and smoother user experience with a chat use case! The primary goal of this app is to showcase how easily ExecuTorch can be integrated into an Android demo app and how to exercise the many features ExecuTorch and Llama models have to offer. | ||
|
|
||
| This app serves as a valuable resource to inspire your creativity and provide foundational code that you can customize and adapt for your particular use case. | ||
|
|
||
| Please dive in and start exploring our demo app today! We look forward to any feedback and are excited to see your innovative ideas. | ||
|
|
||
|
|
||
| ## Key Concepts | ||
| From this demo app, you will learn many key concepts such as: | ||
| * How to prepare Llama models, build the ExecuTorch library, and model inferencing across delegates | ||
| * Expose the ExecuTorch library via JNI layer | ||
| * Familiarity with current ExecuTorch app-facing capabilities | ||
|
|
||
| The goal is for you to see the type of support ExecuTorch provides and feel comfortable with leveraging it for your use cases. | ||
|
|
||
| ## Supporting Models | ||
| As a whole, the models that this app supports are (varies by delegate): | ||
| * Llama 3.1 8B | ||
| * Llama 3 8B | ||
| * Llama 2 7B | ||
| * LLaVA-1.5 vision model (only XNNPACK) | ||
|
|
||
|
|
||
| ## Building the APK | ||
| First it’s important to note that currently ExecuTorch provides support across 3 delegates. Once you identify the delegate of your choice, select the README link to get a complete end-to-end instructions for environment set-up to exporting the models to build ExecuTorch libraries and apps to run on device: | ||
|
|
||
| | Delegate | Resource | | ||
| | ------------- | ------------- | | ||
| | XNNPACK (CPU-based library) | [link](docs/delegates/xnnpack_README.md) | | ||
| | QNN (Qualcomm AI Accelerators) | [link](docs/delegates/qualcomm_README.md) | | ||
| | MediaTek (MediaTek AI Accelerators) | [link](docs/delegates/mediatek_README.md) | | ||
|
|
||
| ## How to Use the App | ||
|
|
||
| This section will provide the main steps to use the app, along with a code snippet of the ExecuTorch API. | ||
|
|
||
| For loading the app, development, and running on device we recommend Android Studio: | ||
| 1. Open Android Studio and select "Open an existing Android Studio project" to open examples/demo-apps/android/LlamaDemo. | ||
| 2. Run the app (^R). This builds and launches the app on the phone. | ||
|
|
||
| ### Opening the App | ||
|
|
||
| Below are the UI features for the app. | ||
|
|
||
| Select the settings widget to get started with picking a model, its parameters and any prompts. | ||
| <p align="center"> | ||
| <img src="../_static/img/opening_the_app_details.png" width=800> | ||
| </p> | ||
|
|
||
|
|
||
|
|
||
| ### Select Models and Parameters | ||
|
|
||
| Once you've selected the model, tokenizer, and model type you are ready to click on "Load Model" to have the app load the model and go back to the main Chat activity. | ||
| <p align="center"> | ||
| <img src="../_static/img/settings_menu.png" width=300> | ||
| </p> | ||
|
|
||
|
|
||
|
|
||
| Optional Parameters: | ||
| * Temperature: Defaulted to 0, you can adjust the temperature for the model as well. The model will reload upon any adjustments. | ||
| * System Prompt: Without any formatting, you can enter in a system prompt. For example, "you are a travel assistant" or "give me a response in a few sentences". | ||
| * User Prompt: More for the advanced user, if you would like to manually input a prompt then you can do so by modifying the `{{user prompt}}`. You can also modify the special tokens as well. Once changed then go back to the main Chat activity to send. | ||
|
|
||
| > [!TIP] | ||
| > Helpful ExecuTorch API in app | ||
| ```java | ||
| // Upon returning to the Main Chat Activity | ||
| mModule = new LlamaModule( | ||
| ModelUtils.getModelCategory(mCurrentSettingsFields.getModelType()), | ||
| modelPath, | ||
| tokenizerPath, | ||
| temperature); | ||
| int loadResult = mModule.load(); | ||
| ```{include} ../../../examples/demo-apps/android/LlamaDemo/README.md | ||
| ``` | ||
|
|
||
| * `modelCategory`: Indicate whether it’s a text-only or vision model | ||
| * `modePath`: path to the .pte file | ||
| * `tokenizerPath`: path to the tokenizer .bin file | ||
| * `temperature`: model parameter to adjust the randomness of the model’s output | ||
|
|
||
|
|
||
| ### User Prompt | ||
| Once model is successfully loaded then enter any prompt and click the send (i.e. generate) button to send it to the model. | ||
| <p align="center"> | ||
| <img src="../_static/img/load_complete_and_start_prompt.png" width=300> | ||
| </p> | ||
|
|
||
| You can provide it more follow-up questions as well. | ||
| <p align="center"> | ||
| <img src="../_static/img/chat.png" width=300> | ||
| </p> | ||
|
|
||
| > [!TIP] | ||
| > Helpful ExecuTorch API in app | ||
| ```java | ||
| mModule.generate(prompt,sequence_length, MainActivity.this); | ||
| ``` | ||
| * `prompt`: User formatted prompt | ||
| * `sequence_length`: Number of tokens to generate in response to a prompt | ||
| * `MainActivity.this`: Indicate that the callback functions (OnResult(), OnStats()) are present in this class. | ||
|
|
||
| [*LLaVA-1.5: Only for XNNPACK delegate*] | ||
|
|
||
| For LLaVA-1.5 implementation, select the exported LLaVA .pte and tokenizer file in the Settings menu and load the model. After this you can send an image from your gallery or take a live picture along with a text prompt to the model. | ||
|
|
||
| <p align="center"> | ||
| <img src="../_static/img/llava_example.png" width=300> | ||
| </p> | ||
|
|
||
|
|
||
| ### Output Generated | ||
| To show completion of the follow-up question, here is the complete detailed response from the model. | ||
| <p align="center"> | ||
| <img src="../_static/img/chat_response.png" width=300> | ||
| </p> | ||
|
|
||
| > [!TIP] | ||
| > Helpful ExecuTorch API in app | ||
| Ensure you have the following functions in your callback class that you provided in the `mModule.generate()`. For this example, it is `MainActivity.this`. | ||
| ```java | ||
| @Override | ||
| public void onResult(String result) { | ||
| //...result contains token from response | ||
| //.. onResult will continue to be invoked until response is complete | ||
| } | ||
|
|
||
| @Override | ||
| public void onStats(float tps) { | ||
| //...tps (tokens per second) stats is provided by framework | ||
| } | ||
|
|
||
| ``` | ||
|
|
||
| ## Reporting Issues | ||
| If you encountered any bugs or issues following this tutorial please file a bug/issue here on [Github](https://github.com/pytorch/executorch/issues/new). |
This file contains 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
Binary file not shown.
Binary file removed
BIN
-264 KB
examples/demo-apps/android/LlamaDemo/docs/screenshots/chat_response.png
Binary file not shown.
Binary file removed
BIN
-1.72 MB
examples/demo-apps/android/LlamaDemo/docs/screenshots/llava_example.png
Binary file not shown.
Binary file removed
BIN
-127 KB
...demo-apps/android/LlamaDemo/docs/screenshots/load_complete_and_start_prompt.png
Binary file not shown.
Binary file not shown.
Binary file removed
BIN
-371 KB
...ples/demo-apps/android/LlamaDemo/docs/screenshots/mtk_changes_to_shell_file.png
Binary file not shown.
Binary file removed
BIN
-502 KB
examples/demo-apps/android/LlamaDemo/docs/screenshots/mtk_output.png
Binary file not shown.
Binary file removed
BIN
-194 KB
examples/demo-apps/android/LlamaDemo/docs/screenshots/opening_the_app_details.png
Binary file not shown.
Binary file removed
BIN
-98.8 KB
examples/demo-apps/android/LlamaDemo/docs/screenshots/settings_menu.png
Binary file not shown.
This file contains 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