Spaces:

whoami02
/

gradio_101

Sleeping

App Files Files Community

whoami02 commited on Mar 26, 2024

Commit

506d318

verified ·

1 Parent(s): 2c7032a

Update prompts.py

Browse files

Files changed (1) hide show

prompts.py +38 -30

prompts.py CHANGED Viewed

@@ -13,36 +13,44 @@ table_info = """
     In order to assist you, I have given the table information below -
     Information:
     ShiftDownTimeDetails table has
-             ID: gives the id of the record.
-             dDate: The date on which the given instance was recorded.
-             Shift: Read Shift-A or First or "First Shift" as Shift-1 from the column and so on for Shift 2 and 3. So shift-B or second or Second or 'Second Shift' will be read as Shift-2. Same for shift 3.
-             MachineID: Identification of a machine. Can be used to recognize or identify a machine which might be specified in the user question.
-             OperationNo: The operation which was taking place on the machine when the current instance was recorded.
-             OperationID: The operator which was undertaking the given operation.
-             StartTime: The starting time of Downtime.
-             EndTime: The ending time of Downtime.
-             DownCategory: Specifies what kind of fault lead to the Downtime. Each instance of Downtime is divided into major categories, this column captures these categories.
-             DownCategory_reason: Also called DownID column. Use this column to answer questions related to the reasons of downtime. Specifies the reason behind the occurance of DownCategory and Downtime.
-             Downtime: It shows the time interval for which the machine was not working or machine was down as well as for any other synonyms. It is given in seconds. If anything related to downtime is asked, check this column.
-             ML_flag: When the downtime exceed a preset threshold, the value of ML_flag changes to 1 or ML_flag is raised.
-             Threshold: Represents a fixed amount of time for which Downtime is acceptable for the current instance. Exceeding of the threshold by Downtime raises an ML_flag.
     ShiftProductionDetails table has
-             ID: gives the id of the record.
-             pDate: The date on which the given instance was recorded.
-             Shift: Read Shift-A or First or "First Shift" as Shift-1 from the column and so on for Shift 2 and 3. So shift-B or second or Second or 'Second Shift' will be read as Shift-2. Same for shift 3.
-             MachineID: Identification of a machine. Can be used to recognize or identify a machine which might be specified in the user question.
-             OperationNo: The operation which was taking place on the machine when the current instance was recorded.
-             OperationID: The operator which was undertaking the given operation.
-             Prod_Qty: Represents the quantity produced.
-             Sum_of_ActCycleTime: Records the total time it took for an operation of OperatioNo to complete undertaken by a Operator.
-             Sum_of_ActLoadUnload: Time between load and unload
-             CO_StdMachiningTime: standard machining time to complete 1 cycle
-             CO_StdLoadUnload: standard time between 2 cycles.
-             Rework_Performed: How many times rework was needed.
-             Marked_for_Rework: Bit value - 1 - marked; 0 - not marked
-             ActMachiningTime_Type12: Time taken for machine operation
-             ActLoadUnload_Type12: Time taken between 2 machine operations
     If the query returns a null value then return as such.
     If you could not find any relevant answer then reply so, do not make up answers randomly.
-    """

     In order to assist you, I have given the table information below -
     Information:
     ShiftDownTimeDetails table has
+            ID: gives the id of the record.
+            dDate: The date on which the given instance was recorded.
+            Shift: Read Shift 1 or First or shift-A as Shift="First Shift" from the column and so on for Shift 2 and 3. So shift 2 or second or Second or shift-B will be read as 'Second Shift'. Same for shift 3.
+            MachineID: Identification of a machine. Can be used to recognize or identify a machine which might be specified in the user question.
+            OperationNo: The operation which was taking place on the machine when the current instance was recorded.
+            OperationID: The operator which was undertaking the given operation.
+            StartTime: The starting time of Downtime.
+            EndTime: The ending time of Downtime.
+            DownCategory: Specifies what kind of fault lead to the Downtime. Each instance of Downtime is divided into major categories, this column captures these categories.
+            DownID: Also called DownCategory_Reasons column. Use this column to answer questions related to the reasons of downtime. Specifies the reason behind the occurance of DownCategory and Downtime.
+            Downtime: It shows the time interval for which the machine was not working or machine was down as well as for any other synonyms. It is given in seconds. If anything related to downtime is asked, check this column.
+            ML_flag: When the downtime exceed a preset threshold, the value of ML_flag changes to 1 or ML_flag is raised.
+            Threshold: Represents a fixed amount of time for which Downtime is acceptable for the current instance. Exceeding of the threshold by Downtime raises an ML_flag.
     ShiftProductionDetails table has
+            ID: gives the id of the record.
+            pDate: The date on which the given instance was recorded.
+            Shift: Read Shift 1 or First or shift-A as Shift="First Shift" from the column and so on for Shift 2 and 3. So shift 2 or second or Second or shift-B will be read as 'Second Shift'. Same for shift 3.
+            MachineID: Identification of a machine. Can be used to recognize or identify a machine which might be specified in the user question.
+            OperationNo: The operation which was taking place on the machine when the current instance was recorded.
+            OperationID: The operator which was undertaking the given operation.
+            Prod_Qty: Represents the quantity produced.
+            Sum_of_ActCycleTime: Records the total time it took for an operation of OperatioNo to complete undertaken by a Operator.
+            Sum_of_ActLoadUnload: Time between load and unload
+            CO_StdMachiningTime: standard machining time to complete 1 cycle
+            CO_StdLoadUnload: standard time between 2 cycles.
+            Rework_Performed: How many times rework was needed.
+            Marked_for_Rework: Bit value - 1 - marked; 0 - not marked
+            ActMachiningTime_Type12: Time taken for machine operation
+            ActLoadUnload_Type12: Time taken between 2 machine operations
+    Focas_AlarmHistory table has
+            ID: ID of the record.
+            AlarmNo: Represents the alarm number, is unique for a similar kind of alarms. Use this column to reference an instance of alarm.
+            AlarmGroupNo: Group number for alarms.
+            AlarmMSG: Use this column to answer anything related to the reason of alarm occurance, or why, which type questions related to alarms.It contains description of why the alarm was triggered.
+            AlarmAxisNo: Axis number for alarm type
+            AlarmTime: Records the time at which alarm was triggered. The format of the time is YYYY-MM-DD HH:mm:ss:000 where Y is year, M is month, D is day, H is hour, m is minutes, s is seconds. Carefully analyze this and return whatever is asked correctly.
+            MachineID: Identification of a machine. Can be used to recognize or identify a machine on which alarm was triggered in the user question.
     If the query returns a null value then return as such.
     If you could not find any relevant answer then reply so, do not make up answers randomly.
+"""