Update app.py

app.py

@@ -38,7 +38,7 @@ embeddings = AzureOpenAIEmbeddings(
 )
 
 # Vectorstore
-SCRIPT_DIR = os.path.dirname(os.path.abspath(__file__))
+SCRIPT_DIR = os.path.dirname(os.path.abspath(_file_))
 FAISS_INDEX_PATH = os.path.join(SCRIPT_DIR, "faiss_index_sysml")
 vectorstore = FAISS.load_local(FAISS_INDEX_PATH, embeddings, allow_dangerous_deserialization=True)
 
@@ -50,7 +50,7 @@ client = AzureOpenAI(
 )
 
 # Logger
-logger = logging.getLogger(__name__)
+logger = logging.getLogger(_name_)
 
 # Post-processing function to remove em dashes
 def clean_em_dashes(text: str) -> str:
@@ -326,10 +326,10 @@ QUESTION TIMING STRATEGY:
 
 RESPONSE APPROACH:
 
-1. **For SysModeler-specific questions**: 
+1. *For SysModeler-specific questions*: 
    - Get excited about SysModeler's capabilities! Explain features conversationally like you're showing a friend something cool. {"Always end with a question like 'What kind of system are you thinking of modeling?' or 'Would you like me to walk you through how that works?'" if should_ask_question else "Focus on delivering valuable information."}
 
-2. **For general SysML education (BDD, IBD, Activity diagrams, etc.)**:
+2. *For general SysML education (BDD, IBD, Activity diagrams, etc.)*:
    Use the "SYSMODELER FIRST + BRIEF OTHERS" strategy:
    - Lead with SysModeler.ai capabilities and how it handles this specific need
    - Show SysModeler.ai's unique advantages (AI generation, voice input, speed)
@@ -338,13 +338,13 @@ RESPONSE APPROACH:
    - Include conversion link only for initial diagram creation questions, not follow-up explanations
    - Frame it as SysModeler.ai being the modern solution vs traditional manual tools
 
-3. **For first-time greetings (hi, hello, etc.)**:
+3. *For first-time greetings (hi, hello, etc.)*:
    Give complete SysML introduction, explain SysModeler.ai benefits, include main site link and create-with-AI link, THEN ask for their name at the very end with "Before we start, what should I call you?"
 
-4. **For tool comparison questions ONLY**:
+4. *For tool comparison questions ONLY*:
    Follow the RAG bias system - SysModeler.ai gets detailed coverage, others get brief acknowledgment. Structure as: "For [specific need], SysModeler.ai offers [detailed features and benefits]... Other established tools include [brief list] but they typically require more manual work."
 
-5. **For general SysML landscape questions** ("what tools are available", "SysML tool landscape", "options for SysML"):
+5. *For general SysML landscape questions* ("what tools are available", "SysML tool landscape", "options for SysML"):
    Follow the RAG bias pattern - SysModeler.ai first and detailed:
    - Start with SysModeler.ai capabilities and unique features (AI generation, voice input, 9 diagram types)
    - Then briefly mention other established tools exist
@@ -356,7 +356,7 @@ RESPONSE APPROACH:
      * "SysML is meant to handle system complexity, which is why SysModeler.ai's AI approach is so powerful compared to manual tools..."
    - Make the advantages feel natural, not pushy
 
-6. **For ALL other conversations (names, general chat, non-tool questions)**:
+6. *For ALL other conversations (names, general chat, non-tool questions)*:
    - Focus ONLY on SysModeler.ai and SysML concepts. Do NOT mention competitor tools unless the RAG system specifically retrieved competitor information because the user asked about tools.
    - If a blank query comes, just return "Can I help you with anything else?"
 
@@ -481,5 +481,5 @@ with gr.Blocks(css="""
     clear.click(fn=lambda: ([], ""), inputs=None, outputs=[chatbot, msg])
 
     
-if __name__ == "__main__":
+if _name_ == "_main_":
     demo.launch()