From 0d5174fc336520ba0897ffd8b213d74d093757f2 Mon Sep 17 00:00:00 2001 From: Knox Lively Date: Sat, 27 Apr 2024 00:49:24 -0600 Subject: [PATCH] removed reference links to parameters --- features/supportedLLMs/BYOLLM.mdx | 6 +++--- features/supportedLLMs/localai.mdx | 8 ++++---- features/supportedLLMs/ollama.mdx | 8 ++++---- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/features/supportedLLMs/BYOLLM.mdx b/features/supportedLLMs/BYOLLM.mdx index c33e62a..174c07d 100644 --- a/features/supportedLLMs/BYOLLM.mdx +++ b/features/supportedLLMs/BYOLLM.mdx @@ -41,9 +41,9 @@ Once you have installed and configured your own LLM provider, you can start usin If you encounter issues while using your own LLM provider with Wave AI, consider the following troubleshooting steps: - **Connection failures:** If Wave AI fails to connect to your own LLM provider or returns an error message, verify that your own LLM provider is running. -- **Timeouts:** If you're unable to complete a query or incur frequent timeouts, try adjusting the [aitimeout](/features/waveAI#customization) parameter to a higher value. This will give your own LLM provider more time to process and respond to your requests, especially if you are running it on a system with limited hardware resources. -- **Incorrect base URL or port:** Ensure that the [aibaseurl](/features/waveAI#customization) parameter points to the correct URL and port number where your own LLM provider is running. If you have changed the default port or are running your own LLM provider on a remote server, update the URL accordingly. -- **Incorrect model selection:** If you have multiple LLMs installed, make sure to set the [aimodel](/features/waveAI#customization) parameter to the specific model you want to use. +- **Timeouts:** If you're unable to complete a query or incur frequent timeouts, try adjusting the `aitimeout` parameter to a higher value. This will give your own LLM provider more time to process and respond to your requests, especially if you are running it on a system with limited hardware resources. +- **Incorrect base URL or port:** Ensure that the `[aibaseurl` parameter points to the correct URL and port number where your own LLM provider is running. If you have changed the default port or are running your own LLM provider on a remote server, update the URL accordingly. +- **Incorrect model selection:** If you have multiple LLMs installed, make sure to set the `aimodel` parameter to the specific model you want to use. - **Unexpected behavior or inconsistent results:** If you encounter unexpected behavior or inconsistent results when using your own LLM provider with Wave AI, try [resetting](#reset-wave-ai) the `aibaseurl` and `aimodel` parameters to their default values and reconfiguring your LLM provider from scratch. This can help rule out any configuration issues that might be causing problems. ## Reset Wave AI diff --git a/features/supportedLLMs/localai.mdx b/features/supportedLLMs/localai.mdx index 86fa987..110abbf 100644 --- a/features/supportedLLMs/localai.mdx +++ b/features/supportedLLMs/localai.mdx @@ -45,10 +45,10 @@ Once you have installed and configured LocalAI, you can start using it in Wave. If you encounter issues while using LocalAI with Wave AI, consider the following troubleshooting steps: - **Connection failures:** If Wave AI fails to connect to LocalAI or returns an error message, [verify that LocalAI is running](https://localai.io/basics/getting_started/#text-generation) and accessible from the system where Wave is installed. Check the LocalAI logs for any error messages or indications of why the connection might be failing. -- **Timeouts:** If you're unable to complete a query or incur frequent timeouts, try adjusting the [aitimeout](/features/waveAI#customization) parameter to a higher value. This will give LocalAI more time to process and respond to your requests, especially if you are running it on a system with limited hardware resources. -- **Incorrect base URL or port:** Ensure that the [aibaseurl](/features/waveAI#customization) parameter points to the correct URL and port number where LocalAI is running. If you have changed the default port or are running LocalAI on a remote server, update the URL accordingly. -- **Incorrect model selection:** If you have multiple LocalAI models installed, make sure to set the [aimodel](/features/waveAI#customization) parameter to the specific model you want to use. -- **Unexpected behavior or inconsistent results:** If you encounter unexpected behavior or inconsistent results when using LocalAI with Wave AI, try [resetting](#reset-wave-ai) the aibaseurl and aimodel parameters to their default values and reconfiguring LocalAI from scratch. This can help rule out any configuration issues that might be causing problems. +- **Timeouts:** If you're unable to complete a query or incur frequent timeouts, try adjusting the `aitimeout` parameter to a higher value. This will give LocalAI more time to process and respond to your requests, especially if you are running it on a system with limited hardware resources. +- **Incorrect base URL or port:** Ensure that the `aibaseurl` parameter points to the correct URL and port number where LocalAI is running. If you have changed the default port or are running LocalAI on a remote server, update the URL accordingly. +- **Incorrect model selection:** If you have multiple LocalAI models installed, make sure to set the `aimodel` parameter to the specific model you want to use. +- **Unexpected behavior or inconsistent results:** If you encounter unexpected behavior or inconsistent results when using LocalAI with Wave AI, try [resetting](#reset-wave-ai) the `aibaseurl` and `aimodel` parameters to their default values and reconfiguring LocalAI from scratch. This can help rule out any configuration issues that might be causing problems. If you continue to face issues after trying these troubleshooting steps, please see the [Additional Resources](#additional-resources) section below for further assistance. diff --git a/features/supportedLLMs/ollama.mdx b/features/supportedLLMs/ollama.mdx index 12b582a..11763ff 100644 --- a/features/supportedLLMs/ollama.mdx +++ b/features/supportedLLMs/ollama.mdx @@ -41,10 +41,10 @@ Once you have installed and configured Ollama, you can start using it in Wave. T If you encounter issues while using Ollama with Wave AI, consider the following troubleshooting steps: - **Connection failures:** If Wave AI fails to connect to Ollama or returns an error message, [verify that Ollama is running](https://github.com/ollama/ollama?tab=readme-ov-file#rest-api) and accessible from the system where Wave is installed. Check the Ollama logs for any error messages or indications of why the connection might be failing. -- **Timeouts:** If you're unable to complete a query or incur frequent timeouts, try adjusting the [aitimeout](/features/waveAI#customization) parameter to a higher value. This will give Ollama more time to process and respond to your requests, especially if you are running it on a system with limited hardware resources. -- **Incorrect base URL or port:** Ensure that the [aibaseurl](/features/waveAI#customization) parameter points to the correct URL and port number where Ollama is running. If you have changed the default port or are running Ollama on a remote server, update the URL accordingly. -- **Incorrect model selection:** If you have multiple Ollama models installed, make sure to set the [aimodel](/features/waveAI#customization) parameter to the specific model you want to use. You can list available models using the ollama list command in your terminal. -- **Unexpected behavior or inconsistent results:** If you encounter unexpected behavior or inconsistent results when using Ollama with Wave AI, try [resetting](#reset-wave-ai) the aibaseurl and aimodel parameters to their default values and reconfiguring Ollama from scratch. This can help rule out any configuration issues that might be causing problems. +- **Timeouts:** If you're unable to complete a query or incur frequent timeouts, try adjusting the `aitimeout` parameter to a higher value. This will give Ollama more time to process and respond to your requests, especially if you are running it on a system with limited hardware resources. +- **Incorrect base URL or port:** Ensure that the `aibaseurl` parameter points to the correct URL and port number where Ollama is running. If you have changed the default port or are running Ollama on a remote server, update the URL accordingly. +- **Incorrect model selection:** If you have multiple Ollama models installed, make sure to set the `aimodel` parameter to the specific model you want to use. You can list available models using the ollama list command in your terminal. +- **Unexpected behavior or inconsistent results:** If you encounter unexpected behavior or inconsistent results when using Ollama with Wave AI, try [resetting](#reset-wave-ai) the `aibaseurl` and `aimodel` parameters to their default values and reconfiguring Ollama from scratch. This can help rule out any configuration issues that might be causing problems. If you continue to face issues after trying these troubleshooting steps, please see the [Additional Resources](#additional-resources) section below for further assistance.