MuPRO SDKEngineering reports · Biweekly progressAll reports

ENGINEERING / BIWEEKLY

Biweekly work and development progress

Results, verification evidence and next steps. Reports normally cover two weeks. The current issue combines a month following conference travel to Shenyang; the next issue returns to the biweekly schedule.

Normal cadence: every 14 daysCurrent issue: combined monthly report · Through 2026-09-12Format: standalone HTML · Archived in Git

Reports

  1. 08.12 — 09.12 · Issue 01 / Combined monthly report

    Monthly review and next two weeks

    HDF5, customer documentation migration, data processing, contribution framework, release evidence and muAFM; Shenyang discussions with Weisheng Cao of Computherm and the plan to update muPREDICT before reconnecting on PanPhaseField SDK; muFerro workflow development and acceptance for September 13–26.

Write the next issue

Next period: 2026-09-13 through 2026-09-26. Copy the blank HTML template, name it after the period's end date, verify the facts and evidence, then add it to the list above. Write all report content in English.

Maintenance and writing guide · Root directory responsibilities · Engineering documentation index

Reports preserve a dated snapshot. Active tasks and acceptance criteria remain in TASK.md. Local test evidence paths identify their availability limits.