Initial commit

app.py

@@ -0,0 +1,180 @@
+import os
+import time
+import csv
+import shutil
+from datetime import datetime
+import openai
+import gradio as gr
+import pandas
+
+# Embeddings
+from langchain.embeddings.openai import OpenAIEmbeddings
+from langchain.vectorstores import Chroma
+
+# Chat Q&A
+from langchain.chat_models import ChatOpenAI
+from langchain.schema import AIMessage, HumanMessage, SystemMessage
+
+# This sets up OpenAI embeddings model
+embeddings = OpenAIEmbeddings()
+
+# Loads database from persisted directory
+db_directory = "/docs/2023_12_06_chroma_db"
+db = Chroma(persist_directory=db_directory, embedding_function=embeddings)
+
+# This is code that retrieves relevant documents based on a similarity search (in this case, it grabs the top 2 relevant documents or chunks)
+retriever = db.as_retriever(search_type='similarity', search_kwargs={"k":2})
+
+with open('system_prompt.txt', 'r') as file:
+    ORIG_SYSTEM_MESSAGE_PROMPT = file.read()
+
+openai.api_key = os.getenv("OPENAI_API_KEY")
+
+#chat = ChatOpenAI(model_name="gpt-3.5-turbo",temperature=0) # Faster for experiments
+chat = ChatOpenAI(model_name="gpt-4",temperature=0)
+
+# Make sure we don't exceed estimation of token limit:
+TOKEN_LIMIT = 4096  # GPT-3.5 Turbo token limit
+BUFFER = 100  # Extra tokens to consider for incoming messages
+PERSISTENT_LOG_PATH = "/data/downvoted_responses.csv" # File in which to log downvoted responses
+LOCAL_LOG_PATH = "./data/downvoted_responses.csv"
+
+def estimate_tokens(texts):
+    return sum([len(t.split()) for t in texts])
+
+def truncate_history(history):
+    tokens = estimate_tokens([msg.content for msg in history])
+    while tokens + BUFFER > TOKEN_LIMIT and len(history) > 3:
+        history = history[0:1] + history[3:]
+        tokens = estimate_tokens([msg.content for msg in history])
+    return history
+    
+def get_full_context(input):
+  retrieved_documents = retriever.get_relevant_documents(input)
+  context = ""  # Initialize an empty string
+
+  file_path = "/docs/Troubleshooting_Table.csv"
+  data = pd.read_csv(file_path)
+  for doc in retrieved_documents:
+      index = doc.metadata['index']
+      context += str(data.iloc[[index]])
+
+  return context
+
+
+is_first_run = True  # Flag to check if it's the first run
+
+# Here is the langchain
+def predict(history, input):
+    
+    global is_first_run  # Use the global flag
+    if is_first_run:
+        context = get_full_context(input)
+        print(context)  # For debugging
+        is_first_run = False  # Set the flag to False after the first run
+    else:
+        context = ""
+
+    history_langchain_format = []
+    history_langchain_format.append(SystemMessage(content=f"{ORIG_SYSTEM_MESSAGE_PROMPT}, here is the user information: {user_info_simulated}"))
+    for human, ai in history:
+        history_langchain_format.append(HumanMessage(content=human))
+        history_langchain_format.append(AIMessage(content=ai))
+    history_langchain_format.append(HumanMessage(content=input))
+    history_langchain_format.append(SystemMessage(content=f"Here is a table with some potentially useful information for troubleshooting: {context}"))
+
+    # Truncate if history is too long
+    history_langchain_format = truncate_history(history_langchain_format)
+
+    gpt_response = chat(history_langchain_format)
+
+    # Extract pairs of HumanMessage and AIMessage
+    pairs = []
+    for i in range(len(history_langchain_format)):
+        if isinstance(history_langchain_format[i], HumanMessage) and (i+1 < len(history_langchain_format)) and isinstance(history_langchain_format[i+1], AIMessage):
+            pairs.append((history_langchain_format[i].content, history_langchain_format[i+1].content))
+
+    # Add the new AI response to the pairs for subsequent interactions
+    pairs.append((input, gpt_response.content))
+
+    return pairs
+
+# Function to handle user message (this clears the interface)
+def user(user_message, chatbot_history):
+    return "", chatbot_history + [[user_message, ""]]
+
+# Function to handle AI's response
+def bot(chatbot_history):
+    user_message = chatbot_history[-1][0] #This line is because we cleared the user_message previously in the user function above
+    # Call the predict function to get the AI's response
+    pairs = predict(chatbot_history, user_message)
+    _, ai_response = pairs[-1]  # Get the latest response
+
+    response_in_progress = ""
+    for character in ai_response:
+        response_in_progress += character
+        chatbot_history[-1][1] = response_in_progress
+        time.sleep(0.05)
+        yield chatbot_history
+
+def log_to_csv(question, answer):
+    """Append a line to a CSV. Create a new file if needed."""
+    now = datetime.today().strftime("%Y%m%d_%H:%M:%S")
+    if not os.path.isfile(PERSISTENT_LOG_PATH):
+        # Add the column names to the CSV
+        with open(PERSISTENT_LOG_PATH, "w+") as csv_file:
+            writer = csv.writer(csv_file)
+            writer.writerow(["datetime", "user_question", "bot_response"])
+
+    # Write the disliked message to the CSV
+    with open(PERSISTENT_LOG_PATH, "a") as csv_file:
+        writer = csv.writer(csv_file)
+        writer.writerow([now, question, answer])
+
+    # Copy file from persistent storage to local repo
+    shutil.copyfile(PERSISTENT_LOG_PATH, LOCAL_LOG_PATH)
+
+def get_voted_qa_pair(history, voted_answer):
+    """Return the question-answer pair from the chat history, given a 
+    particular bot answer. Note: This is required because the 'vote'
+    event handler only has access to the answer that was liked/disliked.
+    """
+    for question, answer in history:
+        if answer == voted_answer:
+            return question, answer
+
+def vote(data: gr.LikeData, history):
+    """This is a function to do something with the voted information"""
+    print(history)
+    if data.liked:
+        print("You upvoted this response: " + data.value)
+    else:
+        print("You downvoted this response: " + data.value)
+        # Find Q/A pair that was disliked
+        question, answer = get_voted_qa_pair(history, data.value)
+        log_to_csv(question, answer)
+        
+def reset_flag():
+    global is_first_run
+    is_first_run = True
+
+# The Gradio App interface
+with gr.Blocks() as demo:
+    gr.Markdown("""<h1><center>DylanAI by CIONIC</center></h1>""")
+    gr.Markdown("""<p><center>For best results, please ask DylanAI one question at a time. Unlike Human Dylan, DylanAI cannot multitask.</center></p>""")
+    chatbot = gr.Chatbot(label="DylanAI")
+    textbox = gr.Textbox(label="Type your question here")
+    clear_button = gr.ClearButton(components=[chatbot])
+    clear_button.click(reset_flag, None, None)
+    
+    # Chain user and bot functions with `.then()`
+    textbox.submit(user, [textbox, chatbot], [textbox, chatbot], queue=False).then(
+        bot, chatbot, chatbot,
+    )
+    chatbot.like(vote, chatbot, None)
+
+# Enable queuing
+demo.queue()
+demo.launch(debug=True, share=True)
+
+

docs/2023_12_05_chroma_db_v2/02adf51d-efcc-4c3c-a866-2bede598855a/data_level0.bin

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f18abd8c514282db82706e52b0a33ed659cd534e925a6f149deb7af9ce34bd8e
+size 6284000

docs/2023_12_05_chroma_db_v2/02adf51d-efcc-4c3c-a866-2bede598855a/header.bin

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:effaa959ce2b30070fdafc2fe82096fc46e4ee7561b75920dd3ce43d09679b21
+size 100

docs/2023_12_05_chroma_db_v2/02adf51d-efcc-4c3c-a866-2bede598855a/length.bin

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9d2a767b41f7386b467051f0f9d5709b98c6234d5385b741ddcb3496f9fa98fb
+size 4000

docs/2023_12_05_chroma_db_v2/02adf51d-efcc-4c3c-a866-2bede598855a/link_lists.bin

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
+size 0

docs/Troubleshooting_Table.csv

@@ -0,0 +1,172 @@
+Symptoms,Core Issue,Steps to Solve,Related Issues,Escalation,Images
+Device is not compatible,App-compatible devices,"Confirm the user is using one of the following compatible devices:
+iPhone: iPhone 11 and newer (recommended); iOS 15.x or later.
+iPad: iPad (7th generation) or newer, iPad Pro (4th generation) or newer, iPad Air (4th generation) or newer, iPad Mini (6th generation) or newer; iPadOS 15.x or later.
+Android: recommended device info TBD; Android 10 (API 29) or later.",None,Escalate if user's device is not on the compatibility list and no alternative compatible device is available.,
+"Font is too big, font is too small",,Change font size in phone settings,Some expected visual elements missing on some screens due to large font sizes.,Escalate if changing font size does not resolve the issue or if it causes functionality problems in the app.,
+"Issues with camera or audio, camera won't flip, camera won't swap, cannot hear technician",Software issues- tech portal,"Camera:
+Turn on phone camera
+Disconnect and then reconnect in the portal 
+
+User cannot hear technician:
+Turn on speaker","Device is not compatible, Bluetooth pairing/connection issues",Escalate if basic troubleshooting (like restarting device or checking settings) fails.,
+"Not able to find Control Unit (range issue or Control Unit is not powered on) Connections repeatedly fail (Control Unit is paired to another phone) Able to connect, but seeing a “--” for battery level in the app’s hub side menu (pairing issue) Seeing “Encryption is insufficient” in the app log from a reported issue (pairing issue)",Bluetooth pairing/connection issues,"Things to check:
+Check Control Unit distance from phone - must be near phone (< 20 ft)
+Check that airplane mode on the phone is turned off and that Bluetooth is turned on
+Verify that the phone and Control Unit have sufficient battery levels
+Remove phone case, if any
+Things to try:
+Restart Control Unit from hub side menu and/or power cycle Control Unit
+Move to a different location. Other electronic devices that use the 2.4GHz frequency band can cause interference and impact the performance of BLE devices.
+Turn Bluetooth off/on on phone
+Force quit/restart app
+Power cycle phone
+Try to connect from a different phone/tablet Note: If the user is switching phones, need to unpair/factory reset from the old phone before it can be paired with the new phone","Issues changing parameters, Sleeve keeps getting unplugged.",Escalate if all troubleshooting steps fail to establish a connection.,
+"Cannot connect to control unit after previous slow/incomplete disconnection, Cannot connect to control unit after backgrounding the app
+",Bluetooth pairing/connection issues,Force quit + restart app. Phone reboot may also be required.,"Not able to find Control Unit (range issue or Control Unit is not powered on), Battery not charging, battery not charging enough, poor charging",Escalate if force quitting and restarting the app or rebooting the phone does not resolve the issue.,
+"Plug control unit into the sleeve, don't see 3 flashing green lights that indicate a proper connection",Sleeve cable issues,"1.Instruct user to put Control Unit in the pocket first and then plug in the connector/cable; make sure that the DC is in the pocket
+2. Visually check for proper insertion of the sleeve connector
+3. Make sure user knows to press in side buttons before removing cable
+4. Verify that the LED on the Control Unit flashes green 3x after plugging in the cable (this is different from “breathing green” when the Control Unit is powered on while adequately charged)
+5. If 3x green LED flashes are not seen, try restarting the Control Unit from the app's hub side menu and/or power cycle the Control Unit by long-pressing the button until the LED goes off (about 3 seconds), then pressing the button again to turn it back on. Then reattempt cable insertion.","Errors when upgrading sleeve, errors when upgrading control unit, Firmware upgrade issues","Escalate if repeated attempts at reconnection, including restarting the Control Unit, fail.",
+Sleeve keeps getting unplugged,Sleeve cable issues,"Instruct user to put Control Unit in the pocket first and then plug in the connector/cable; make sure that the DC is in the pocket
+Visually check for proper insertion of the sleeve connector
+Make sure user knows to press in side buttons before removing cable
+Verify that the LED on the Control Unit flashes green 3x after plugging in the cable (this is different from “breathing green” when the Control Unit is powered on while adequately charged)
+If 3x green LED flashes are not seen, try restarting the Control Unit from the app's hub side menu and/or power cycle the Control Unit by long-pressing the button until the LED goes off (about 3 seconds), then pressing the button again to turn it back on. Then reattempt cable insertion.","Plug control unit into the sleeve, don't see 3 flashing green lights that indicate a proper connection, Notification of weak signal from electrodes, impedance check errors",Escalate if issue persists after ensuring proper insertion and restarting the Control Unit.,
+"Notification of weak signal from electrodes, impedance check errors",Impedance check error,"Pat down electrodes
+When was the last time they changed their electrodes?","Stuck in electrode calibration phase, failed impedance check, Gel electrodes falling off/ won't adhere to the skin",Escalate if patting down electrodes and changing them does not solve the problem.,
+"Stuck in electrode calibration phase, failed impedance check",Impedance check error,,"Loss of stimulation, Stimulation with the wrong timing",Escalate if recalibration attempts fail consistently.,
+Loss of stimulation,Stim issues; gel electrode issues,"Verify electrodes placement on body (especially for TA)
+Verify the settings in the FES configuration and the slider in the capp screen
+Replace electrodes
+Possible muscle fatigue","Stimulation errors, Battery not charging, battery not charging enough, poor charging",Escalate if verifying settings and electrode placement does not restore functionality.,
+Stimulation with the wrong timing,Stim issues; gel electrode issues,"Prompt the user to recalibrate properly, and see if the problem disappears. ","Stimulation errors, Skeleton on app looks odd",Escalate if recalibration does not correct the timing issue.,
+Stimulation errors,Stim issues; gel electrode issues,"Prompt the user to recalibrate properly, and see if the problem disappears. ","Battery not charging, battery not charging enough, poor charging, Errors when upgrading sleeve, errors when upgrading control unit",Escalate if recalibration does not resolve the errors.,
+"Battery not charging, battery not charging enough, poor charging",Battery issues,"The battery needs a high power charger for adequate charging. The user must use the cable and charger that is provided for charging their device (""Charger has limited power to charge"" notification may be seen otherwise). Failure to do so will result in poor charging.","Cannot connect to control unit after previous slow/incomplete disconnection, Cannot connect to control unit after backgrounding the app, Device is not compatible",Escalate if using the correct charger and cable does not solve the charging issue.,
+"Errors when upgrading sleeve, errors when upgrading control unit",Firmware upgrade issues,Ask user for code/error message,"Firmware upgrade issues, Plug control unit into the sleeve, don't see 3 flashing green lights that indicate a proper connection",Escalate if error codes persist after asking the user for specific messages and attempting basic troubleshooting.,
+Gel electrodes falling off/ won't adhere to the skin,Gel electrode issues,"Make sure skin is clean of any lotions/oils
+Recommend moisturizing overnight so skin is not dry
+Trim any extra leg hair
+Change gel electrode pads    
+Slippage in hot weather (sweat)
+Dry skin
+Replace gel electrodes
+","Notification of weak signal from electrodes, impedance check errors, Skin irritation",Escalate if skin preparation and electrode replacement do not fix the issue.,
+Difficulty placing electrodes,,Palpating TA (try on unaffected leg first),"Stuck in electrode calibration phase, failed impedance check, Gel electrodes falling off/ won't adhere to the skin",Escalate if palpation techniques do not aid in correct placement.,
+Skin irritation,,"(redness persisting more than a few hours, skin breakdown, burn)
+If redness, contact us 
+If a burn, discontinue use and contact
+If open skin, discontinue use and contact","Gel electrodes falling off/ won't adhere to the skin, Residue of goopy balls on skin",Immediate escalation for burns or open skin; escalate for persistent redness.,
+Residue of goopy balls on skin,,"Use a cloth to clean skin when removing the sleeve, Use the back of the gel pad to blot at fabric to pick up any gel residue","Skin irritation, Gel electrodes falling off/ won't adhere to the skin",No escalation,
+Velcro coming undone,,"Check electrode connection
+Sleeve is indicated for gait, not other movements",,Escalate if checking connections and ensuring correct usage does not solve the problem.,
+Skeleton on app looks odd,,"Prompt the user to recalibrate properly, and see if the problem disappears.","Stimulation with the wrong timing, Stimulation errors",Escalate if recalibration does not correct the display issue.,
+Issues changing parameters,,"Neuropathy–try adjusting frequency to determine if higher or lower frequencies improve sensitivity.  Contact Cionic if neuropathy increases
+Initial sensation uncomfortable–instruct customer in getting past the sensory level to the motor level which is often more comfortable","Not able to find Control Unit (range issue or Control Unit is not powered on), Battery not charging, battery not charging enough, poor charging",Escalate if adjusting frequencies and guidance on sensory to motor level transition do not work.,
+Login issues,,"Is an account created on cionic.com (same one as signed up with)?
+Invalid credentials
+Needs new email for log in
+Email deliverability issues
+Create individual login and send separate email","Device is not compatible, Some expected visual elements missing on some screens due to large font sizes",Escalate if account verification and troubleshooting email issues do not resolve the problem.,
+Some expected visual elements (ex: buttons) are missing on some screens due to large font sizes,,"Ask user to reduce system or accessibility font sizes
+Do they have a Galaxy Fold? If yes, please use the front cover screen which is similar to a normal phone screen and does not hide buttons","Font is too big, font is too small, Device is not compatible",Escalate if adjusting font sizes or using alternative displays (like front cover screen on Galaxy Fold) does not resolve the issue.,
+"No steps recorded in the app, incorrect number of steps recorded in app",,"Bring app out of the background to reconnect
+Powering off the Control Unit (long press on Control Unit button) stops stimulation and ends a protocol, but because of this, steps cannot be fetched
+Short-press can stop stimulation and then go into the app to stop a protocol
+Control Unit ran out of battery before the program was stopped 
+BLE disconnect just before the recording stopped, steps could not be fetched
+Make sure not to stop a program with BLE disconnected","Cannot connect to control unit after previous slow/incomplete disconnection, Cannot connect to control unit after backgrounding the app"", Bluetooth pairing/connection issues",Escalate if ensuring proper app usage and troubleshooting connectivity issues do not correct the step count.,
+Issue with reporting an issue,,"Ensure that the Control Unit is Bluetooth-connected to the app
+Make sure that you have a good network connection (WiFi recommended) before submitting issues","Login issues, Device is not compatible",Escalate if ensuring proper network connection and Bluetooth connectivity does not allow issue submission.,
+"100
+ALERT_NOCARD
+
+
+",missing sd card,,,,
+"101
+ALERT_CHARGED
+",battery charged,,,,
+"102
+ALERT_CHARGING
+",battery charging,"The battery needs a high power charger for adequate charging. The user must use the cable and charger that is provided for charging their device (""Charger has limited power to charge"" notification may be seen otherwise). Failure to do so will result in poor charging.",,,
+"103
+ALERT_NOMUSCLE
+",no muscle,,,,
+"104
+ALERT_STIM_LL
+",stim low level error,,,,
+"105
+ALERT_STIM_BUF
+",stim buffer error,,,,
+"106
+ALERT_STIM_PW
+",stim pulse width out of bounds,,,,
+"107
+ALERT_STIM_DAC",stim intensity out of bounds,,,,
+"108
+ALERT_STIM_TIM",stim timer error,,,,
+"109
+ALERT_STIM_CRC",stim crc error,Check cable connections,,,
+"110
+ALERT_STIM_MUSCLE",stim mux configuration invalid,,,,
+"111 (old FW) or 149 + channel (150-159)
+ALERT_STIM_MAX",stim above maximum load threshold,check electrodes,,,
+"112
+ALERT_STIM_FREQ
+
+",stim frequency out of bounds,,,,
+"113  (old FW) or 159 + channel (160-169)
+ALERT_STIM_MIN",stim below minimum load threshold,check electrodes,,,
+"114
+ALERT_STIM_GENERIC
+
+",stim error generic,,,,
+"115  (old FW) or 169 + channel (170-179)
+ALERT_STIM_TIMEOUT",single muscle stimulated for more than 5 seconds,,,,
+"116
+ALERT_STIM_CURRENT
+",stim current out of boounds,,,,
+"117
+ALERT_STIM_SAFETY
+",stim is in safety mode,,,,
+"118  (old FW) or 179 + channel (180-189)
+ALERT_STIM_ELECTRODE",one or more electrodes detached,check electrodes,,,
+"119
+ALERT_SELF_TEST
+",FES hardware issue,,,,
+"120
+ALERT_BAD_CHARGER
+",charger cannot provide enough power to charge DC,,,,
+"121
+ALERT_ELECTRODE_TEST",FES electrode hardware issue,,,,
+FES hardware fault code c0,,"Restart the app and try again. If error persists, escalate immediately to CIONIC support",,,
+internalError = 99,should never happen,Immediately escalate,,,
+currentVersionsUnavailable = 100,Deprecated - not used anymore,N/A,,,
+imageDownloadChannelOpenError = 101,Unable to open Bluetooth L2CAP data channel to transfer image file,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+imageDownloadWriteFileError = 102,Failed to transfer image file over Bluetooth L2CAP,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+dcSerialUnavailable = 103,Could not fetch version info from DC,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+sendCommandUnpacking = 200,Bluetooth error trying to unpack the image file,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+sendCommandCheckingVersions = 201,Bluetooth error trying to check FW versions,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+sendCommandUpgradingDC = 202,Bluetooth error trying to upgrade the DC component,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+sendCommandUpgradingBLE = 203,Bluetooth error trying to upgrade the BLE component,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+sendCommandUpgradingSI = 204,Bluetooth error trying to upgrade the sleeve,Ensure sleeve cable is plugged in securely and try again. Reboot Control Unit and try again.,,,
+sendCommandUpgradingFES = 205,Bluetooth error trying to upgrade the FES component,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+unpackTimeout = 300,Unpacking the image did not complete within the specified time,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+upgradeDCTimeout = 311,Upgrading the DC component did not complete within the specified time,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+upgradeBLETimeout = 312,Upgrading the BLE component did not complete within the specified time,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+upgradeSITimeout = 313,Upgrading the sleeve did not complete within the specified time,Ensure sleeve cable is plugged in securely and try again. Reboot Control Unit and try again.,,,
+upgradeFESTimeout = 314,Upgrading the FES component did not complete within the specified time,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+restartTimeout = 302,Timed out waiting for the DC to reconnect after upgrading a component,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+unpackError = 400,Error unpacking the image file,"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+upgradeDCError = 401,Error upgrading the DC component (also see FW upgrade codes below for the second code),"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+upgradeBLEError = 402,Error upgrading the BLE component (also see FW upgrade codes below for the second code),"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+upgradeSIError = 403,Error upgrading the sleeve (also see FW upgrade codes below for the second code),Ensure sleeve cable is plugged in securely and try again.,,,
+upgradeFESError = 404,Error upgrading the FES component (also see FW upgrade codes below for the second code),"Reboot Control Unit and try again, turn Bluetooth off/on, reboot phone",,,
+upgradeRestartError = 405,Unexpected DC restart during the upgrade process,"Ensure Control Unit proximity and try again. If error persists, reboot Control Unit.",,,
+upgradeMismatchError = 406,Upgraded components do not match what was downloaded after a successful upgrade.,Escalate immediately,,,
+serverHashCheckNoImages = 500,No components found in the image file,"Try again. If that fails, escalate",,,
+serverHashCheckMissingDCVersion = 501,No DC component found in the image file.,Escalate immediately,,,
+serverHashCheckError = 502,Server failed to verify the image file or there was a network error,Check network connection and try again.,,,
+serverUpgradeCheckFailed = 503,Could not download an image file from the server or there was a network error,"Check network connection and try again. If error persists, make sure that phone has enough free storage (> 5MB).",,,
+serverNoUpgradesAvailable = 504,Not an error - server reported that no upgrades were available for the Control Unit/Sleeve,N/A,,,

requirements.txt

@@ -0,0 +1,5 @@
+openai == 0.28.1
+langchain == 0.0.308
+chromadb == 0.4.13
+tiktoken == 0.5.1
+pandas == 1.5.3

system_prompt.txt

@@ -0,0 +1,18 @@
+You are DylanAI, a friendly troubleshooting chatbot that helps users troubleshoot issues with their CIONIC Neural Sleeve.
+You walk through troubleshooting step by step, asking the user after each step of the process to confirm they understand.
+Don't have the user do more than 1 things at once. USERS SHOULD ONLY DO ONE THING AT A TIME.
+
+Rules (you must follow all the rules):
+* If you cannot answer using the sources, say you don't know.
+* DO NOT GIVE USERS ADVICE THAT IS OUTSIDE OF THE SOURCES YOU ARE PROVIDED WITH. This is very important. It is most helpful to only give answers directly from the sources.
+* Make things easy to understand, explain all jargon and acronyms, and explain uncommon words.
+* Be concise
+* You should only answer questions that are about Cionic and the Cionic Neural Sleeve.
+* USERS SHOULD ONLY DO ONE THING AT A TIME.
+
+If the user asks another question not related to the first issue, divert them to create another issue using: |*|ISSUE WIDGET (IN DEMO PRESS CLEAR BUTTON)|*| . 
+A new topic should trigger you to create another issue using |*|ISSUE WIDGET (IN DEMO PRESS CLEAR BUTTON)|*| . 
+
+You may need to escalate an issue to the CIONIC Support team. 
+Follow the appropriate escalation strategy defined in the Escalation column in the table you are provided.
+When escalating to CIONIC Support, use: |*|ESCALATION WIDGET|*| .