[M4-P5] Jupytext Migration: Chamber_Wall_Loss Part 2 (3 notebooks)

[Gorkowski]

Dependencies:

#986 [M4-P4] ──► #THIS [M4-P5]

Dependencies:

• M4-P4: [M4-P4] Jupytext Migration: Particle_Phase Functional + Chamber_Wall_Loss Part 1 (3 notebooks) #986

---

Description

Convert 3 notebooks from the Chamber_Wall_Loss directory to Jupytext paired sync format (.py:percent). This is Phase 5 of the M4 Jupytext Full Migration maintenance plan, completing the wall loss tutorials.

Context

This is part of the M4 maintenance plan to complete Jupytext paired sync migration for all remaining notebooks in docs/Examples/. Continues from M4-P4 which started Chamber_Wall_Loss notebooks.

Value:

• Enables editing notebooks as plain Python files (better diffs, linting, IDE support)
• Validates notebook content through linting
• Completes wall loss tutorial coverage including rectangular geometry and forward simulation

Note: Wall loss API was recently updated - watch for any API changes during execution.

Scope

Estimated Lines of Code: ~50 lines (metadata + formatting changes per .py file)
Complexity: Low

Notebooks to Convert (3):

• docs/Examples/Chamber_Wall_Loss/Notebooks/Rectangular_Wall_Loss_Strategy.ipynb
• docs/Examples/Chamber_Wall_Loss/Notebooks/wall_loss_builders_factory.ipynb
• docs/Examples/Chamber_Wall_Loss/Notebooks/Chamber_Forward_Simulation.ipynb

Files Created:

• docs/Examples/Chamber_Wall_Loss/Notebooks/Rectangular_Wall_Loss_Strategy.py (~100-200 LOC)
• docs/Examples/Chamber_Wall_Loss/Notebooks/wall_loss_builders_factory.py (~100-200 LOC)
• docs/Examples/Chamber_Wall_Loss/Notebooks/Chamber_Forward_Simulation.py (~100-200 LOC)

Acceptance Criteria

Conversion

• All 3 notebooks converted to .py:percent format using validate_notebook --convert-to-py
• Each .py file has proper Jupytext header with py:percent format

Linting

• Run ruff check --fix on all new .py files
• Run ruff format on all new .py files
• Final ruff check passes with no errors

Sync Validation

• Sync .py changes back to .ipynb using validate_notebook --sync
• Validate sync status with validate_notebook --check-sync (must pass)

Execution

• All 3 notebooks execute successfully using run_notebook
• No API deprecation warnings or errors in output
• Review output for any wall loss API issues (document if found)

Technical Notes

Conversion Workflow

For each notebook:

# 1. Convert to .py:percent format
python3 .opencode/tool/validate_notebook.py docs/Examples/Chamber_Wall_Loss/Notebooks/Rectangular_Wall_Loss_Strategy.ipynb --convert-to-py

# 2. Lint the new .py file
ruff check docs/Examples/Chamber_Wall_Loss/Notebooks/Rectangular_Wall_Loss_Strategy.py --fix
ruff format docs/Examples/Chamber_Wall_Loss/Notebooks/Rectangular_Wall_Loss_Strategy.py

# 3. Sync linted .py back to .ipynb
python3 .opencode/tool/validate_notebook.py docs/Examples/Chamber_Wall_Loss/Notebooks/Rectangular_Wall_Loss_Strategy.ipynb --sync

# 4. Validate sync status
python3 .opencode/tool/validate_notebook.py docs/Examples/Chamber_Wall_Loss/Notebooks/Rectangular_Wall_Loss_Strategy.ipynb --check-sync

# 5. Execute to verify notebook works
python3 .opencode/tool/run_notebook.py docs/Examples/Chamber_Wall_Loss/Notebooks/Rectangular_Wall_Loss_Strategy.ipynb

API Validation

During execution, watch especially for wall loss API changes:

• Import path changes (deprecation warnings)
• Function signature changes
• Builder/Factory pattern changes
• Rectangular geometry parameter changes

If API issues are found, fix them

References

Maintenance Plan:

• adw-docs/dev-plans/maintenance/M4-jupytext-full-migration.md - Full migration plan

Related:

• [M4-P4] Jupytext Migration: Particle_Phase Functional + Chamber_Wall_Loss Part 1 (3 notebooks) #986 - M4-P4 (dependency)
• adw-docs/documentation_guide.md - Notebook editing guidelines

[Gorkowski]

[ADW-AGENTS] # 🤖 ADW Workflow Status

Description: Complete workflow: plan → build → validate → test → format → document → ship

ADW ID: 8dbd5d6b
Current Phase: Workflow completed successfully
Started: 2026-01-30T23:25:01.831902Z
Last Update: 2026-01-31T00:29:03.930676Z

Current Status

✅ Workflow completed in 1h 4m

Workflow Plan

• ✅ Generate Multi-Review Implementation Plan (at 2026-01-30T23:30:00.905659Z)
• ✅ Build Implementation (at 2026-01-30T23:33:42.693964Z)
• ✅ Validate Implementation and Fix Gaps (at 2026-01-31T00:04:54.061986Z)
• ✅ Run Tests (at 2026-01-31T00:14:40.881431Z)
• ✅ Format Code and Add Docstrings (at 2026-01-31T00:15:08.348425Z)
• ✅ Generate Documentation (at 2026-01-31T00:25:47.872863Z)
• ✅ Ship Implementation (at 2026-01-31T00:29:02.378280Z)

📋 Recent Activity

[2026-01-31T00:04:54.062013Z] Completed step 3/7: Validate Implementation and Fix Gaps
[2026-01-31T00:04:56.607559Z] Starting step 4/7: Run Tests
[2026-01-31T00:14:40.881451Z] Completed step 4/7: Run Tests
[2026-01-31T00:14:42.489876Z] Starting step 5/7: Format Code and Add Docstrings
[2026-01-31T00:15:08.348441Z] Completed step 5/7: Format Code and Add Docstrings
[2026-01-31T00:15:09.963852Z] Starting step 6/7: Generate Documentation
[2026-01-31T00:25:47.872892Z] Completed step 6/7: Generate Documentation
[2026-01-31T00:25:49.430287Z] Starting step 7/7: Ship Implementation
[2026-01-31T00:29:02.378303Z] Completed step 7/7: Ship Implementation
[2026-01-31T00:29:03.928711Z] Workflow complete finished: 7/7 steps completed

🔍 Archived Updates

[2026-01-30T23:25:01.914322Z] Workflow complete started with 7 steps
[2026-01-30T23:25:03.672526Z] Starting step 1/7: Generate Multi-Review Implementation Plan
[2026-01-30T23:30:00.905683Z] Completed step 1/7: Generate Multi-Review Implementation Plan
[2026-01-30T23:30:02.512677Z] Starting step 2/7: Build Implementation
[2026-01-30T23:33:42.693984Z] Completed step 2/7: Build Implementation
[2026-01-30T23:33:44.256411Z] Starting step 3/7: Validate Implementation and Fix Gaps

---

This comment is automatically updated as the workflow progresses