Pedagogy: move 00_introduction/40_how_to_draw_a_circle → 06_python_advanced/80_circle_case_study

Open Beginner friendly
#401 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
jupyter-notebook, matplotlib, numpy, python
Domain
documentation

Research direction

Wait for the companion content-completion issue to land first. Move 00_introduction/40_how_to_draw_a_circle.ipynb to 06_python_advanced/80_circle_case_study.ipynb, then search README and internal references and update the Colab badge URL. Run the notebook from its new location and verify the acceptance items.

Written by the indexing model from the issue text.

Description

pedagogy

Goal

00_introduction/40_how_to_draw_a_circle.ipynb is a case study using sympy + numpy + matplotlib to express the same circle three ways (closed, implicit, parametric). With the 00_introduction restructure (motivation only), case studies move to 06_python_advanced. The circle case study is a natural capstone after numpy + matplotlib basics.

Scope

Move 00_introduction/40_how_to_draw_a_circle.ipynb06_python_advanced/80_circle_case_study.ipynb. Mechanical move (rename + path adjustment + Colab badge URL update). No content rewrite in this issue.

Suggested ordering within 06_python_advanced/:

  • 60_numpy_basics
  • 70_matplotlib_basics
  • 80_circle_case_study ← uses 60 + 70 + sympy
  • 90_pandas

Dependency

  • Companion content-completion issue must land FIRST (hint + solution + exercises). Then this move is purely mechanical.

Acceptance

  • File moved.
  • Colab badge URL updated to new path.
  • Internal links / README references updated if any.
  • Notebook still runs from new location.
Dominant language
Jupyter Notebook
Stars
12
Forks
75
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from kangwonlee/nmisp

All issues in kangwonlee/nmisp

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.