Spaces:
Sleeping
Sleeping
Update app.py
Browse files
app.py
CHANGED
@@ -69,6 +69,7 @@ Return only a JSON object with insights as an array, with no additional text:
|
|
69 |
"""
|
70 |
|
71 |
refine_problem_prompt = """You are an expert consultant specializing in enhancing and refining technical problems to make them more sophisticated, novel, and inventive. Your task is to transform an initial technical problem description into two improved versions by integrating selected insights from technical documents.
|
|
|
72 |
# Instructions:
|
73 |
1. Carefully review the initial technical problem.
|
74 |
2. Consider the selected insights from technical documents that could enhance the problem formulation.
|
@@ -80,22 +81,26 @@ refine_problem_prompt = """You are an expert consultant specializing in enhancin
|
|
80 |
- Add appropriate constraints and technical requirements
|
81 |
- Maintain coherence and technical feasibility
|
82 |
- Suggest innovative directions without fully solving the problem
|
|
|
|
|
83 |
# Output Format:
|
84 |
Return the results in **strictly valid JSON** format with no additional text.
|
85 |
All string values (especially multiline descriptions) must:
|
86 |
- Be enclosed in double quotes
|
87 |
- Escape internal double quotes with backslashes (e.g., \")
|
88 |
-
- Replace newline characters with "\\n" (double backslash-n for JSON)
|
89 |
- Avoid unescaped Markdown if it breaks JSON syntax
|
|
|
|
|
90 |
Reference json:
|
91 |
{
|
92 |
"refined_problem_1": {
|
93 |
"title": "Brief descriptive title for the first refined problem",
|
94 |
-
"description": "
|
95 |
},
|
96 |
"refined_problem_2": {
|
97 |
"title": "Brief descriptive title for the second refined problem",
|
98 |
-
"description": "
|
99 |
}
|
100 |
}
|
101 |
"""
|
|
|
69 |
"""
|
70 |
|
71 |
refine_problem_prompt = """You are an expert consultant specializing in enhancing and refining technical problems to make them more sophisticated, novel, and inventive. Your task is to transform an initial technical problem description into two improved versions by integrating selected insights from technical documents.
|
72 |
+
|
73 |
# Instructions:
|
74 |
1. Carefully review the initial technical problem.
|
75 |
2. Consider the selected insights from technical documents that could enhance the problem formulation.
|
|
|
81 |
- Add appropriate constraints and technical requirements
|
82 |
- Maintain coherence and technical feasibility
|
83 |
- Suggest innovative directions without fully solving the problem
|
84 |
+
- Must follow the structured format: Context, Constraints, and Problem Description
|
85 |
+
|
86 |
# Output Format:
|
87 |
Return the results in **strictly valid JSON** format with no additional text.
|
88 |
All string values (especially multiline descriptions) must:
|
89 |
- Be enclosed in double quotes
|
90 |
- Escape internal double quotes with backslashes (e.g., \")
|
91 |
+
- Replace newline characters with \"\\n\" (double backslash-n for JSON)
|
92 |
- Avoid unescaped Markdown if it breaks JSON syntax
|
93 |
+
- Clearly separate sections using the labels: Context, Constraints, Problem Description
|
94 |
+
|
95 |
Reference json:
|
96 |
{
|
97 |
"refined_problem_1": {
|
98 |
"title": "Brief descriptive title for the first refined problem",
|
99 |
+
"description": "## Context: \\n[Provide relevant background and setting]\\n## Constraints: \\n[List technical and operational constraints]\\n## Problem Description: \\n[State the core problem clearly and inventively]"
|
100 |
},
|
101 |
"refined_problem_2": {
|
102 |
"title": "Brief descriptive title for the second refined problem",
|
103 |
+
"description": "## Context: \\n[Provide relevant background and setting]\\n## Constraints: \\n[List technical and operational constraints]\\n## Problem Description: \\n[State the core problem clearly and inventively]"
|
104 |
}
|
105 |
}
|
106 |
"""
|