Update app.py

app.py

@@ -54,15 +54,13 @@ def talk_to_llm(user_prompt):
     }
 
     prompt_text = f'''
-    As StarGateVR, your role is specialized in customizing ADQL (Astronomical Data Query Language) queries for astronomers. Your focus is particularly on integrating specific 'WHERE' clauses into a standard query template. We will put your WHERE clause into the completed query template.
+    As StarGateVR, your role is specialized in customizing ADQL (Astronomical Data Query Language) queries for astronomers. Your focus is particularly on integrating specific 'WHERE' clauses into a standard query template. We will put your WHERE clause into the completed query template. In some cases, you may need to add additional parameters to the SELECT clause.
 
     The query includes essential fields like source_id, positional data (RA, DEC), motion data (pmra, pmdec), light parameters, and placeholders for additional parameters. 
 
-    Customizing 'WHERE' Clause: Your primary task is to adapt the 'WHERE' clause to fit the user's specific astronomical requirements. This often involves filtering stars based on various criteria such as distance, location in the sky, brightness, etc. Always include the SELECT and FROM clauses exactly as given in the template. Note that the WHERE clause must reference variables by the field name and not the "AS" name. There is a special case for the part of the SELECT that is " '#' || source_id as source_id", in the WHERE clause this field should always be referred to by "source_id".
+    Customizing 'WHERE' Clause: Your primary task is to adapt the 'WHERE' clause to fit the user's specific astronomical requirements. This often involves filtering stars based on various criteria such as distance, location in the sky, brightness, etc. Always include the SELECT and FROM clauses exactly as given in the template. Note that the WHERE clause must reference variables by the field name and not the "AS" name. There is a special case for the part of the SELECT that is " 'Gaia DR3 ' || source_id as source_id", in the WHERE clause this field should always be referred to by "source_id".
 
-    Note that if new parameters are added to the SELECT clause, they should be given unique names ending in "_mag" if they are in units of Magnitude. This is important for compatibility with StarGateVR.
-
-    If new parameters are added to the WHERE clause, they should be referenced by their field name in the database, and included in the SELECT clause.
+    Note that all parameter used in the WHERE clause should also be included in the SELECT clause. 
 
     Here is an example of the WHERE clause: