Solver documentation - #363
Conversation
There was a problem hiding this comment.
Pull request overview
This PR restructures and refreshes the Solver documentation, shifting from older “conceptual + detailed behavior” pages to a concise four-page Solver section (overview, workflow, unknowns, convergence) and updates the documentation-agent guidance to match that new ownership model.
Changes:
- Rewrites the Solver conceptual pages to a shorter, cross-linked set:
solver_main,solver_workflow,solver_unknowns, andsolver_convergence. - Adds a new dedicated “Solved Unknowns” page and removes the deprecated “unknowns and equations” and “solver behavior” pages.
- Updates documentation agent metadata/instructions to reflect the new Solver documentation structure and responsibilities.
Reviewed changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated 7 comments.
Show a summary per file
| File | Description |
|---|---|
| doc/solver/solver_workflow.rst | Rewritten workflow explanation of the solver iteration loop and references to related pages. |
| doc/solver/solver_unknowns.rst | New page documenting the solved unknowns (p, ṁ, u) and related interpretation notes. |
| doc/solver/solver_unknowns_and_equations.rst | Removed legacy page in favor of the new unknowns page. |
| doc/solver/solver_main.rst | Updated landing page with toctree pointing to the new three sibling pages. |
| doc/solver/solver_convergence.rst | Rewritten convergence criteria page with explicit tolerance definition. |
| doc/solver/solver_behavior.rst | Removed; detailed content folded into the four-page Solver section approach. |
| .github/agents/SystemConceptDocAgent.agent.md | Updates agent scope guidance to point Solver content to SolverBehaviorDocAgent. |
| .github/agents/SolverBehaviorDocAgent.agent.md | Redefines this agent’s scope to own the full four-page Solver section. |
| .github/agents/DocumentationCoordinator.agent.md | Updates solver-doc routing guidance; also modifies YAML front matter/tooling metadata. |
| .github/agents/APIReferenceAgent.agent.md | Updates exclusions to reflect the new four-page Solver section ownership. |
| The solver reaches the network state through a fixed-point Newton-Raphson iteration: it | ||
| repeatedly assembles a linear system from the current solution, solves it, transfers the | ||
| result back to the assets and nodes, and tests whether the solution has stopped changing. | ||
| The loop stops when the solution has converged or when an iteration limit is reached. |
| **Assemble.** Each asset and then each node contributes its equations, linearized about the | ||
| current solution, into a single system. The number of equations always matches the number of | ||
| unknowns, so the linear system is square and solvable. |
| **Iteration limit.** The loop is capped at 100 iterations. If convergence is not reached | ||
| within that limit, a warning is logged and the last computed iterate is used as the result. |
| Specific internal energy is used as the thermal state variable rather than temperature | ||
| directly. This keeps the energy-transport terms linear in the solved unknowns: convective | ||
| energy transport appears as the product of mass flow and specific internal energy, both of | ||
| which are solved quantities. Temperature is recovered from the specific internal energy | ||
| through the fluid-property relations; those relations are not re-derived here (see | ||
| :doc:`../physics/physics_main`). |
| description: '>-' | ||
| Coordinate documentation work for SIMULATOR-CORE by classifying requests,: '' | ||
| enforcing the documentation structure, delegating to specialist agents, and: '' | ||
| validating consistency across pages.: '' |
| prompt: '>-' | ||
| Review the page(s) just authored for audience fit, section fit, scope: '' | ||
| correctness, duplication, and cross-link quality.: '' |
| prompt: '>-' | ||
| Validate that the documentation build is clean (toctrees, autodoc: '' | ||
| resolution, rst syntax) for the page(s) just authored/reviewed.: '' |
vanmeerkerk
left a comment
There was a problem hiding this comment.
Sam een paar opmerkingen.
| validating consistency across pages.: '' | ||
| argument-hint: Documentation goal, affected sections/pages, and scope constraints. | ||
| tools: [read, search, edit, execute/runInTerminal, web, agent] | ||
| tools: ['read', 'search', 'edit', 'execute/runInTerminal', 'web', 'agent', 'read_file', 'file_search', 'grep_search', 'insert_edit_into_file', 'replace_string_in_file', 'create_file', 'get_terminal_output', 'open_file', 'ask_questions', 'get_errors', 'list_dir', 'validate_cves', 'run_subagent', 'semantic_search', 'run_in_terminal'] |
There was a problem hiding this comment.
These tools: 'read_file', 'file_search', 'grep_search', 'insert_edit_into_file', 'replace_string_in_file', 'create_file', 'get_terminal_output', 'open_file', 'ask_questions', 'get_errors', 'list_dir', 'validate_cves', 'run_subagent', 'semantic_search', 'run_in_terminal' are uknown on VS Code Copilot.
| description: '>-' | ||
| Coordinate documentation work for SIMULATOR-CORE by classifying requests,: '' | ||
| enforcing the documentation structure, delegating to specialist agents, and: '' | ||
| validating consistency across pages.: '' |
|
|
||
| Limitations | ||
| ----------- | ||
| The absolute term keeps quantities that are near zero from blocking convergence, while the |
There was a problem hiding this comment.
Algemene vraag zouden deze criteria niet uitgewerkt moeten worden in dimensieloze waarde? Zodat alle core quantities evenveel bijdragen aan de tolerance?
| **Assemble.** Each asset and then each node contributes its equations, linearized about the | ||
| current solution, into a single system. The number of equations always matches the number of | ||
| unknowns, so the linear system is square and solvable. |
No description provided.