These notes are a collaborative teaching resource under active development. Experts in power-system dynamics, stability, scientific machine learning, and system identification — and careful students — are welcome to help over the long term.
Cross-domain collaboration¶
This book is a bridge. A chapter is stronger when a machine-learning reader and a power-systems reader both review it.
| Contribution | Why it helps |
|---|---|
| A glossary row that translates one term into the other field | Gives the next reader a shared word |
| A “Coming from ML” or “Coming from power systems” sentence on a chapter you know | Lets people jump in without reading everything above |
| A paired review (one reader from each field) on a pull request | Catches jargon that only one community understands |
| A teacher overlay (week plan) for Learning paths | Lets another course reuse the same labs |
| Deepening Labs 1–5, a landscape example, or a Lab 4 option — not a new assessed Lab 6 for a new architecture | Keeps one spine; maintainers: docs/guides/lab_spine_policy.md |
A glossary row or a translation sentence is a good first contribution. A single row is enough.
How you can help¶
| Role | Examples |
|---|---|
| Reader | Report typos, broken links, unclear explanations via Feedback |
| Contributor | Fix a page, add an exercise, improve a lab notebook (pull request with DCO sign-off) |
| Reviewer | Comment on chapter proposals and pull requests in your area |
| Section editor | Own Dynamics, Stability, Identification, or Labs once appointed (GOVERNANCE.md) |
Full process: CONTRIBUTING.md.
Conduct: CODE_OF_CONDUCT.md.
Credit: CONTRIBUTORS.md.
What we ask¶
Use published sources only — no sealed research metrics on student pages.
Write in teaching voice; cite neighbors honestly (Related open resources).
Sign every commit (
git commit -s) so contributions come in under the same licences as the book (content CC BY-NC-SA 4.0, code MIT).Keep the three applications — dynamics, stability, identification — as the core unless a governance discussion says otherwise.
Interest in a longer role¶
Open a GitHub issue with the Collaboration / section editor template, or start a Discussion in the Collaborators category once Discussions are enabled. We expect to appoint section editors gradually as the preview matures.
Licence reminder¶
By contributing you agree that your content and code may be distributed under this project’s dual licence. Summary: License.