@jutge.org/toolkit 4.4.9 → 4.4.17

package/README.md

@@ -110,6 +110,7 @@ For a complete walkthrough, see the [Getting Started Guide](docs/getting-started
 
 - **[Getting Started Guide](docs/getting-started-guide.md)** - Complete guide to using the toolkit
 - **[Problem Anatomy](docs/problem-anatomy.md)** - Understanding problem structure and files
+- **[Quiz Anatomy](docs/quiz-anatomy.md)** - Understanding quiz problems and question types
 - **[JutgeAI Features](docs/jutge-ai.md)** - Using AI to generate content
 
 ### Installation Guides

package/assets/prompts/funcs/creators/create-solution.tpl.txt

@@ -0,0 +1,23 @@
+Now, write a solution in {{proglang}} to solve this problem.
+
+Take these instructions into account:
+
+- It must be written in an idiomatic way and only include relevant comments.
+
+- The code must be efficient and handle all edge cases.
+
+- The code should only write the required {{functions}} functions and any helper functions that are needed.
+
+- The code should not execute any statement.
+
+- The code should not define a main program or a main function.
+
+- The code should not define global variables but may define global constants.
+
+- The code must be well written and easy to understand to novices. It cannot use advanced constructs.
+
+- The code does not have to check the preconditions stated in the problem statement.
+
+- Do not use any non-standard libraries.
+
+{{proglangPrompt}}

package/assets/prompts/funcs/creators/create-statement.tpl.txt

@@ -0,0 +1,28 @@
+You are to write the statement of a new {{proglang}} programming problem in {{language}}.
+
+The statement must be written in LaTeX, using a few predefined macros.
+Use LaTeX math syntax for formulas and variables.
+Use \lstinline macros for inline code snippets.
+Use dollars for inline maths and use \[ and \] for display maths.
+Do not add input/output test cases in the statement.
+Separate paragraphs by a blank line and \medskip macro.
+
+Write in the style of programming contests like the ACM ICPC or Jutge.org.
+
+Here is an example for an unrelated problem in English, follow its structure and macros:
+
+{{latexExample}}
+
+The title for the new problem is:
+
+{{title}}
+
+The theme of the new problem is:
+
+{{theme}}
+
+The functions that are requested in the new problem are:
+
+{{functions}}
+
+The headers of the functions must be written in {{proglang}}.

package/assets/prompts/funcs/creators/private-test-cases.tpl.txt

@@ -0,0 +1,12 @@
+Now, write a {{proglang}} program that serves to check the correctness and the efficiency of function {{function}}.
+
+This program should be a sequence of print statements that call {{function}} with some inputs.
+
+Some inputs should cover edge cases and some other inputs should be used to check the efficiency.
+
+Do not include comments now.
+
+Do not use loops.
+
+Do not add any formatting, markdown or code fences.
+

package/assets/prompts/funcs/creators/sample-test-cases.tpl.txt

@@ -0,0 +1,16 @@
+Now, write a {{proglang}} program that serves as sample test cases of the {{functions}} functions.
+
+This program should be a sequence of print statements that call each of the required functions
+with some sample inputs.
+
+Sample test cases must be written in {{proglang}} and follow the specification of the functions.
+
+Sample test cases should be relatively small but cover interesting cases but not all edge cases.
+
+If the problem statement features some examples, include them as part of the sample test cases.
+
+Do not include comments now.
+
+Separate the tests for each function with an empty line.
+
+Do not add any formatting, markdown or code fences.

package/assets/prompts/funcs/creators/sample.dt.tpl.txt

@@ -0,0 +1,15 @@
+Now, write a Python doctest with the same inputs as in this test cases:
+
+{{sampleTests}}
+
+Do not include comments now.
+
+Separate the tests for each function with an empty line.
+
+Do not add any formatting, markdown or code fences. Do not output empty lines.
+
+Output should follow the format of Python doctests. For instance:
+>>> factorial(5)
+120
+>>> factorial(0)
+1

package/assets/prompts/funcs/examples/statement.tex

@@ -0,0 +1,23 @@
+\Problem{Primes everywhere}
+
+\UsePython
+
+\Statement
+
+Carla is a young girl who loves math. She is interested in prime numbers and wants some functions to help her in her mathematical musitations.
+
+\medskip
+
+\begin{enumerate}
+
+    \item Write a function \lstinline|is_prime(n: int) -> bool| that returns True if $n$ is a prime number, and False otherwise.
+
+    \item Write a function \lstinline|next_prime(n: int) -> int| that returns the smallest prime number greater than $n$.
+
+    \item Write a function \lstinline|count_primes(a: int, b: int) -> int| that returns the number of prime numbers between $a$ and $b$ inclusive.
+
+\end{enumerate}
+
+All given values by Carla are non-negative integers.
+
+\SampleSession

package/assets/prompts/funcs/proglangs/py.md

@@ -0,0 +1,9 @@
+# Additional guidelines for Python
+
+- Use f-strings for string formatting when possible.
+
+- Use type hints for function definitions. Do not use old-style type hints such as `List[int]` with `List` imported from `typing`, but use modern syntax such as `list[int]`.
+
+- Ensure that the generated Python3 code follows best practices, including proper indentation, use of functions, use of docstrings, and adherence to PEP 8 style guidelines.
+
+- Each function should be documented with a docstring.

package/assets/prompts/io/examples/statement-coda.tex

@@ -0,0 +1,7 @@
+
+\Observation
+
+This problem has been generated by Jutge$^{\text{AI}}$. Remove this observation after reviewing it carefully.
+
+\Sample
+

package/assets/python/pyexec.py

@@ -1,19 +1,26 @@
 # type: ignore
 
 """
-Execute some Python code given from stdin
+Execute some Python code given from stdin and seed random number generator with argv[1].
 and print all resulting global variables as JSON.
 """
 
 import json
 import sys
 import types
+import random
 
 # Read the code from stdin
 code = sys.stdin.read()
 
+# Seed random number generator
+seed = int(sys.argv[1])
+random.seed(seed)
+
 # Create a namespace for execution
-namespace = {}
+namespace = {
+    'seed': seed    # this makes sure that some variables are always present
+}
 
 # Execute the code in the namespace
 exec(code, namespace)