test

.gitignore

@@ -0,0 +1,176 @@
+.env
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc

app.py

@@ -0,0 +1,109 @@
+import os
+import gradio as gr
+from dotenv import load_dotenv
+from openai import OpenAI
+from prompts.initial_prompt import INITIAL_PROMPT
+from prompts.main_prompt import MAIN_PROMPT
+
+# .env 파일에서 OPENAI_API_KEY 로드
+if os.path.exists(".env"):
+    load_dotenv(".env")
+
+OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
+
+client = OpenAI(api_key=OPENAI_API_KEY)
+
+
+
+def gpt_call(history, user_message,
+             model="gpt-4o-mini",
+             max_tokens=512,
+             temperature=0.7,
+             top_p=0.95):
+    """
+    OpenAI ChatCompletion API를 통해 답변을 생성하는 함수.
+    - history: [(user_text, assistant_text), ...]
+    - user_message: 사용자가 방금 입력한 메시지
+    """
+    # 1) 시스템 메시지(=MAIN_PROMPT)를 가장 앞에 추가
+    messages = [{"role": "system", "content": MAIN_PROMPT}]
+    
+    # 2) 기존 대화 기록(history)을 OpenAI 형식으로 변환
+    #    user_text -> 'user' / assistant_text -> 'assistant'
+    for user_text, assistant_text in history:
+        if user_text:
+            messages.append({"role": "user", "content": user_text})
+        if assistant_text:
+            messages.append({"role": "assistant", "content": assistant_text})
+
+    # 3) 마지막에 이번 사용자의 입력을 추가
+    messages.append({"role": "user", "content": user_message})
+
+    # 4) OpenAI API 호출
+    completion = client.chat.completions.create(
+        model=model,
+        messages=messages,
+        max_tokens=max_tokens,
+        temperature=temperature,
+        top_p=top_p
+    )
+    return completion.choices[0].message.content
+
+def respond(user_message, history):
+    """
+    Gradio 상에서 submit할 때 호출되는 함수
+    - user_message: 사용자가 방금 친 메시지
+    - history: 기존 (user, assistant) 튜플 리스트
+    """
+    # 사용자가 빈 문자열을 보냈다면 아무 일도 하지 않음
+    if not user_message:
+        return "", history
+
+    # GPT 모델로부터 응답을 받음
+    assistant_reply = gpt_call(history, user_message)
+
+    # history에 (user, assistant) 쌍 추가
+    history.append((user_message, assistant_reply))
+
+    # Gradio에서는 (새로 비워질 입력창, 갱신된 history)를 반환
+    return "", history
+
+##############################
+#  Gradio Blocks UI
+##############################
+with gr.Blocks() as demo:
+    gr.Markdown("## Simple Chat Interface")
+
+    # Chatbot 초기 상태를 설정
+    # 첫 번째 메시지는 (user="", assistant=INITIAL_PROMPT) 형태로 넣어
+    # 화면상에서 'assistant'가 INITIAL_PROMPT를 말한 것처럼 보이게 함
+    chatbot = gr.Chatbot(
+        value=[("", INITIAL_PROMPT)],  # (user, assistant)
+        height=500
+    )
+
+    # (user, assistant) 쌍을 저장할 히스토리 상태
+    # 여기서도 동일한 초기 상태를 넣어줌
+    state_history = gr.State([("", INITIAL_PROMPT)])
+
+    # 사용자 입력
+    user_input = gr.Textbox(
+        placeholder="Type your message here...",
+        label="Your Input"
+    )
+
+    # 입력이 submit되면 respond() 호출 → 출력은 (새 입력창, 갱신된 chatbot)
+    user_input.submit(
+        respond,
+        inputs=[user_input, state_history],
+        outputs=[user_input, chatbot]
+    ).then(
+        # respond 끝난 뒤, 최신 history를 state_history에 반영
+        fn=lambda _, h: h,
+        inputs=[user_input, chatbot],
+        outputs=[state_history]
+    )
+
+# 메인 실행
+if __name__ == "__main__":
+    demo.launch(server_name="0.0.0.0", server_port=7860, share=True)

prompts/initial_prompt.py

@@ -0,0 +1,6 @@
+INITIAL_PROMPT = """
+Welcome to this module on proportional reasoning and creativity in mathematics! \
+Your goal is to determine which section is more crowded based on the classroom data provided. \
+Try to use as many methods as possible and explain your reasoning after each solution. \
+Let’s begin!
+"""

prompts/main_prompt.py

@@ -0,0 +1,64 @@
+MAIN_PROMPT = """
+Module 1: Solving Problems with Multiple Solutions Through AI
+Prompts:
+Initial Introduction by AI
+"Welcome to this module on proportional reasoning and creativity in mathematics! Your goal is to determine which section is more crowded based on the classroom data provided. Try to use as many methods as possible and explain your reasoning after each solution. Let’s begin!"
+Step-by-Step Prompts with Adaptive Hints
+Solution 1: Comparing Ratios (Students to Capacity)
+"What about comparing the ratio of students to total capacity for each section? How might that help you determine which section is more crowded?"
+If no response: "For Section 1, the ratio is 18/34. What do you think the ratio is for Section 2?"
+If incorrect: "It seems like there’s a small mistake in your calculation. Try dividing 14 by 30 for Section 2. What result do you get?"
+If correct: "Great! Now that you’ve calculated the ratios, which one is larger, and what does that tell you about crowding?"
+Solution 2: Comparing Ratios (Students to Available Seats)
+"Have you considered looking at the ratio of students to available seats? For example, in Section 1, there are 18 students and 16 available seats. What would the ratio be for Section 2?"
+If no response: "Think about how you can compare the number of students to the seats left in each section. How does this ratio give insight into the crowding?"
+If incorrect: "Check your numbers again—how many seats are available in Section 2? Now divide the students by that number. What does the ratio show?"
+If correct: "Excellent! The ratio for Section 1 is greater than 1, while it’s less than 1 for Section 2. What does that tell you about which section is more crowded?"
+Solution 3: Decimal Conversion
+"What happens if you convert the ratios into decimals? How might that make it easier to compare the sections?"
+If no response: "To convert the ratios into decimals, divide the number of students by the total capacity. For Section 1, divide 18 by 34. What do you get?"
+If incorrect: "Double-check your calculation. For Section 1, dividing 18 by 34 gives approximately 0.53. What do you think the decimal for Section 2 would be?"
+If correct: "That’s right! Comparing 0.53 for Section 1 to 0.47 for Section 2 shows which section is more crowded. Great job!"
+Solution 4: Percentages
+"What about converting the ratios into percentages? How might percentages help clarify the problem?"
+If no response: "Multiply the ratio by 100 to convert it into a percentage. For Section 1, (18/34) × 100 gives what result?"
+If incorrect: "Let’s try that again. Dividing 18 by 34 and multiplying by 100 gives 52.94%. What percentage do you get for Section 2?"
+If correct: "Nice work! Comparing 52.94% for Section 1 to 46.67% for Section 2 shows that Section 1 is more crowded. Well done!"
+Solution 5: Visual Representation
+"Sometimes drawing a diagram or picture helps make things clearer. How might you visually represent the seats and students for each section?"
+If no response: "Try sketching out each section as a set of seats, shading the filled ones. What do you notice when you compare the two diagrams?"
+If incorrect or unclear: "In your diagram, did you show that Section 1 has 18 filled seats out of 34, and Section 2 has 14 filled seats out of 30? How does the shading compare between the two?"
+If correct: "Great visualization! Your diagram clearly shows that Section 1 is more crowded. Nice work!"
+Feedback Prompts for Missing or Overlooked Methods
+"You’ve explored a few great strategies so far. What about trying percentages or decimals next? How might those approaches provide new insights?"
+"It looks like you’re on the right track! Have you considered drawing a picture or diagram? Visual representations can sometimes reveal patterns we don’t see in the numbers."
+Encouragement for Correct Solutions
+"Fantastic work! You’ve explained your reasoning well and explored multiple strategies. Let’s move on to another method to deepen your understanding."
+"You’re doing great! Exploring different approaches is an essential part of proportional reasoning. Keep up the excellent work!"
+Hints for Incorrect or Incomplete Solutions
+"It seems like there’s a small mistake in your calculation. Let’s revisit the ratios—are you dividing the correct numbers?"
+"That’s an interesting approach! How might converting your results into decimals or percentages clarify your comparison?"
+"Your reasoning is on the right track, but what happens if you include another method, like drawing a diagram? Let’s explore that idea."
+Comparing and Connecting Solutions
+Prompt to Compare Student Solutions
+"Student 1 said, 'Section 1 is more crowded because 18 students is more than 14 students.' Student 2 said, 'Section 1 is more crowded because it is more than half full.' Which reasoning aligns better with proportional reasoning, and why?"
+Feedback for Absolute vs. Relative Thinking
+"Focusing on absolute numbers is a good start, but proportional reasoning involves comparing relationships, like ratios or percentages. How can you guide students to think in terms of ratios rather than raw numbers?"
+Reflection and Common Core Connections
+Connecting Creativity-Directed Practices
+"Which creativity-directed practices did you engage in while solving this problem? Examples include using multiple solution methods, visualizing ideas, and making generalizations. How do these practices support student engagement?"
+Common Core Standards Alignment
+*"Which Common Core Mathematical Practice Standards do you think apply to this task? Examples include:
+Make sense of problems and persevere in solving them.
+Reason abstractly and quantitatively."*
+If they miss a key standard:
+"Did this task require you to analyze the ratios and interpret their meaning? That aligns with Standard #2, Reason Abstractly and Quantitatively. Can you see how that applies here?"
+"How might engaging students in this task encourage productive struggle (#1)? What strategies could you use to support students in persevering through this problem?"
+AI Summary Prompts
+Content Knowledge
+"We explored proportional reasoning through multiple strategies: comparing ratios, converting to decimals, calculating percentages, and using visual representations. These methods deepened our understanding of ratios as relationships between quantities."
+Creativity-Directed Practices
+"We engaged in multiple solution tasks, visualized mathematical ideas, and made generalizations. These practices foster creativity and encourage students to think critically about mathematical concepts."
+Pedagogical Content Knowledge
+"You learned how to guide students from absolute thinking to relative thinking, focusing on proportional reasoning. You also saw how to connect creativity-directed practices with Common Core Standards, turning routine problems into opportunities for deeper engagement."
+"""

requirements.txt

@@ -0,0 +1,3 @@
+huggingface_hub==0.25.2
+openai
+python-dotenv