Maintenance: convert 50_ode/{00,40}*.md to .ipynb for consistency

Open Beginner friendly
#386 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
70/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
jupyter-notebook, python
Domain
documentation

Research direction

Start with 50_ode/00_Ordinary_Differential_Equation_Exact_Solution.md and 50_ode/40_comparing_with_num_int.md, then inspect nearby .ipynb lessons for the repository's notebook and badge conventions. Convert both files while preserving prose and code-cell structure, and run the standard notebook test runner; done means both lessons are .ipynb files and execute successfully under CI.

Written by the indexing model from the issue text.

Description

Two files in 50_ode/ are markdown rather than notebooks:

  • 50_ode/00_Ordinary_Differential_Equation_Exact_Solution.md
  • 50_ode/40_comparing_with_num_int.md

Every other lesson in the module (and the curriculum at large) is a .ipynb. The two .md files break the "every numbered lesson is an executable notebook" pattern, and they are excluded from notebook-execution CI.

Scope

  • Convert each .md to .ipynb (jupyter nbconvert --to notebook --from markdown, or hand-rebuild if the markdown predates a useful structure).
  • Preserve the markdown prose as markdown cells; promote any code blocks to code cells.
  • Add Colab badges (the existing badge automation will pick them up after merge).
  • Verify the new notebooks execute under the standard test runner.

Why

Consistency: learners arriving at 50_ode/ see a uniform set of notebooks, no special "this lesson is markdown only" exception. CI consistency: the new notebooks become subject to the same execution-as-test guarantee as everything else.

Small, mechanical, low-risk. Good first PR for someone wanting to learn the repo conventions.

Dominant language
Jupyter Notebook
Stars
12
Forks
75
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.