Spaces:
Runtime error
Runtime error
Update app.py
Browse files
app.py
CHANGED
|
@@ -325,6 +325,7 @@ Examples:
|
|
| 325 |
...
|
| 326 |
n) final improvement suggestion...
|
| 327 |
|
|
|
|
| 328 |
Only output the suggestions exactly as a numbered list (text)
|
| 329 |
|
| 330 |
Full Report HTML:
|
|
@@ -865,12 +866,17 @@ Keep in mind the:
|
|
| 865 |
- It should start with <html> and end with </html>
|
| 866 |
- Use a responsive design. Do not fix the width of the main container in the generated HTML. Instead, set the meta viewport to "width=device-width, initial-scale=1" and use CSS (such as viewBox attributes in SVG) to ensure the chart scales properly.
|
| 867 |
- Make the visuals content rich, there's no point having a visual if its content has no real value.
|
| 868 |
-
- It has to convey some relevant insights.
|
| 869 |
- Make sure all the items are visible and don't require hovering the mouse to be displayed - this report is meant to be printed.
|
| 870 |
- For any element where text is displayed, if you choose a dark background, the fond has to be white / if you choose a clear background, the font has to be black
|
| 871 |
- Use your judgement to decide between box plots, bubble charts, calendar view, chord diagrams, histograms, ...
|
| 872 |
- Your response should start with <html> and end with </html> - no intro before, no comments after.
|
| 873 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 874 |
// Examples
|
| 875 |
{graph_examples}
|
| 876 |
|
|
@@ -977,6 +983,12 @@ Note: Visual placeholders are solely supposed to generate diagrams not for graph
|
|
| 977 |
- Take in consideration that the resulting iframe content will render 1200px width and and 700px high.
|
| 978 |
- Do not use any [x] reference notation for citations (ex: [1], [2], ...) inside the mermaid code - we will manage sources separately
|
| 979 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 980 |
// Examples
|
| 981 |
Note: Pay attention for each example to what type of parenthesis / bracket is used and respect it scrupulously
|
| 982 |
|
|
@@ -1230,6 +1242,12 @@ Note: the output will be processed through regex and the identifiers removed, bu
|
|
| 1230 |
- Make sure not to bundle together several sources, use one source at a time when mentioning it, do the same for the authors. They can be put together only if both were involved and mentioned in the research results.
|
| 1231 |
Note: LinkedIn is not a source - if you want to use a source related to LinkedIn, you should check the author of the page visited, this is the real source, mention the name of the author as "'authorName' from LinkedIn Pulse"
|
| 1232 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1233 |
// Important
|
| 1234 |
- Make it real, with anecdotes from the content
|
| 1235 |
- Ground the content on the inputs shared above (context and knowledge inputs) with facts and numbers
|
|
|
|
| 325 |
...
|
| 326 |
n) final improvement suggestion...
|
| 327 |
|
| 328 |
+
Note: Discard impractical recommendation (in pdf or gr.html)
|
| 329 |
Only output the suggestions exactly as a numbered list (text)
|
| 330 |
|
| 331 |
Full Report HTML:
|
|
|
|
| 866 |
- It should start with <html> and end with </html>
|
| 867 |
- Use a responsive design. Do not fix the width of the main container in the generated HTML. Instead, set the meta viewport to "width=device-width, initial-scale=1" and use CSS (such as viewBox attributes in SVG) to ensure the chart scales properly.
|
| 868 |
- Make the visuals content rich, there's no point having a visual if its content has no real value.
|
|
|
|
| 869 |
- Make sure all the items are visible and don't require hovering the mouse to be displayed - this report is meant to be printed.
|
| 870 |
- For any element where text is displayed, if you choose a dark background, the fond has to be white / if you choose a clear background, the font has to be black
|
| 871 |
- Use your judgement to decide between box plots, bubble charts, calendar view, chord diagrams, histograms, ...
|
| 872 |
- Your response should start with <html> and end with </html> - no intro before, no comments after.
|
| 873 |
|
| 874 |
+
// Purpose and grounding
|
| 875 |
+
- It has to convey some relevant insights grounded from the context and knowledge input
|
| 876 |
+
- It CANNOT be hallucinated or hypothetical, it has to be factual and based on relevant info
|
| 877 |
+
- You will be penalised if you lie or mix things that are not related to each other
|
| 878 |
+
- Do not "wing it" with clumsy output, have a deep thinking to it
|
| 879 |
+
|
| 880 |
// Examples
|
| 881 |
{graph_examples}
|
| 882 |
|
|
|
|
| 983 |
- Take in consideration that the resulting iframe content will render 1200px width and and 700px high.
|
| 984 |
- Do not use any [x] reference notation for citations (ex: [1], [2], ...) inside the mermaid code - we will manage sources separately
|
| 985 |
|
| 986 |
+
// Purpose and grounding
|
| 987 |
+
- It has to convey some relevant insights grounded from the context and knowledge input
|
| 988 |
+
- It CANNOT be hallucinated or hypothetical, it has to be factual and based on relevant info
|
| 989 |
+
- You will be penalised if you lie or mix things that are not related to each other
|
| 990 |
+
- Do not "wing it" with clumsy output, have a deep thinking to it
|
| 991 |
+
|
| 992 |
// Examples
|
| 993 |
Note: Pay attention for each example to what type of parenthesis / bracket is used and respect it scrupulously
|
| 994 |
|
|
|
|
| 1242 |
- Make sure not to bundle together several sources, use one source at a time when mentioning it, do the same for the authors. They can be put together only if both were involved and mentioned in the research results.
|
| 1243 |
Note: LinkedIn is not a source - if you want to use a source related to LinkedIn, you should check the author of the page visited, this is the real source, mention the name of the author as "'authorName' from LinkedIn Pulse"
|
| 1244 |
|
| 1245 |
+
// Purpose and grounding
|
| 1246 |
+
- It has to convey some relevant insights grounded from the context and knowledge input
|
| 1247 |
+
- It CANNOT be hallucinated or hypothetical, it has to be factual and based on relevant info
|
| 1248 |
+
- You will be penalised if you lie or mix things that are not related to each other
|
| 1249 |
+
- Do not "wing it" with clumsy output, have a deep thinking to it
|
| 1250 |
+
|
| 1251 |
// Important
|
| 1252 |
- Make it real, with anecdotes from the content
|
| 1253 |
- Ground the content on the inputs shared above (context and knowledge inputs) with facts and numbers
|