Mining Diagram Assistant
Enables readers to quickly understand where engineering objects are located, how they are connected, and what the research focuses on, while retaining the ability to modify and reuse the diagrams later.
Core Capabilities
- From materials to graphical structure: Extract spatial or connection relationships between strata, roadways, stopes, and measurement points, reducing manual effort.
- Purpose-driven selection: Distinguish between diagrams for illustrating geometry, demonstrating processes, or highlighting monitoring layouts; retain key details.
- Editable and verifiable: Generate modifiable source files or plotting code, and cross-check annotations against engineering materials for consistency.
Determine What the Diagram Should Communicate
Confirm the diagram's purpose, audience, and the most important information before reading existing sketches, plans, cross-sections, coordinates, dimensions, relationships, and style requirements. For modifications, prioritize keeping the original legend and expression habits. When precise geometry is unavailable, use clear conceptual schematics.
Only ask for information that changes the structure, such as viewpoint, key connections, or whether to scale. Minor missing items can be noted in the diagram; produce a discussable version first.
Workflow
- Determine the diagram's purpose, perspective, and the issues to highlight; organize objects and connections.
- Draw based on available dimensions; use clear non-proportional schematics when only relationships are known.
- For simple editable layout diagrams, use local SVG scripting; for complex cross-sections or CAD, select tools based on the original materials.
- After rendering, double-check relationships, annotations, legends, and unconfirmed information, then deliver the source files.
Use Resources as Needed
- Before using local tools, read Parameters and Scope, then call scripts/render_network.py. Tools only handle the specified format and capability; they do not represent task completion.
- When first learning the input format, review the synthetic example examples/network.json; demo data should not be treated as actual measurements or specification parameters.
- For method selection, boundary judgment, or complex cases: read references/methods.md.
- When needing to quickly organize deliverables, copy and adapt assets/diagram-brief.md; this is an optional starting point, not a fixed output format.
Deliverables
Prioritize delivering the required diagram and an editable version, along with a short caption and any unconfirmed items affecting understanding. For complex diagrams, consider splitting into an overview and detail views; keep simple tasks as a single diagram. Do not replace diagrams that can be generated with text solutions, nor claim that unrendered code has passed visual inspection.