Spaces:
Running
Running
Update app.py
Browse files
app.py
CHANGED
@@ -582,7 +582,16 @@ STRICT REQUIREMENTS:
|
|
582 |
6. Maintain clear formatting
|
583 |
7. At the end of the solution output, print SymPy code that you would use to solve or verify the main equations in the question
|
584 |
8. Observe the folloiwng SymPy Guidelines
|
585 |
-
{SYMPY_GUIDELINES}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
586 |
|
587 |
#Consider
|
588 |
#When writing SymPy code:
|
|
|
582 |
6. Maintain clear formatting
|
583 |
7. At the end of the solution output, print SymPy code that you would use to solve or verify the main equations in the question
|
584 |
8. Observe the folloiwng SymPy Guidelines
|
585 |
+
{SYMPY_GUIDELINES}
|
586 |
+
9. For problems where the subject is Real Analysis and the question type is proof, observe the following guidelines:
|
587 |
+
- Give detailed reasoning for each step and justify every step.
|
588 |
+
- In delta-epsilon proofs, explain clearly why a given choice of delta will work
|
589 |
+
- Connect each step with a rationale
|
590 |
+
- Always justify the existence of bounds
|
591 |
+
- If you conclude certain terms vanish in a limit, clearly justify why
|
592 |
+
- Label subsections of the proof. Don't just say 'step 1', 'step 2', etc but rather the labels of the subsections
|
593 |
+
themselves should provide a clear outline of the main aspects of the proof
|
594 |
+
- In notes after the proof, if you observe aspects of the problem that might confuse students, address them."""
|
595 |
|
596 |
#Consider
|
597 |
#When writing SymPy code:
|