The application plan must answer one question: this load is worth equipping with this much new energy and energy storage, and after equipping it, it can balance itself, meet policy indicators, be economically feasible, and operate safely. This skill provides only three things; read whichever is needed:
| What is needed | What to read |
|---|---|
| How to structure the outline, what each chapter demonstrates, and what the hard policy indicators are | references/outline.md |
| Where to find policy documents, reference reports, and public data, and how to check the calculation table | references/source-materials.md |
| What figures each chapter has, from what angles they can be drawn, and how to draw them | references/figures.md |
How to use
- First determine which one the user wants. If they only ask for the outline, give only the outline; if they only ask for materials, give only the data sources. There is no need to go through the full process.
- When writing the application plan, first obtain the official drafting outline according to the province where the project is located (samples are already available for Xinjiang, Jiangxi, etc., see
outline.md), then compare againstsource-materials.mdto list what materials are missing and request them from the user; do not fabricate missing data. - When planning illustrations, select them one by one according to the angles of each type of figure in
figures.md; there is no need to draw all of them. When data charts are needed, you can directly run the reference implementations inscripts/, or just borrow the drawing methods from them. - Use the
markdown-conversionskill to convert Word, PDF, and Excel to Markdown; for scanned PDFs usepdf-transcription; to overlay the site boundary onto a satellite screenshot usegeospatial-converter; for editable electrical main wiring diagrams and control platform architecture diagrams usediagram-creator。 - When no output location is specified, place it according to the repository convention in
projects/<YYYYMMDD>-<项目简称>/. The recommended structure is:0-inputs/(raw materials, read-only),0-materials/(converted drafts, intermediate data),1-drafts/(Markdown for each chapter),2-figures/(illustrations and chart data),8-scripts/(plotting commands for this project).
Reference implementations
scripts/ The scripts under resources/requirements.txtcan be run independently, dependencies are in resources/params.example.json。
| Script | Purpose |
|---|---|
prepare_hourly.py |
Organize the calculation table and PVsyst hourly data into standard 8760 h data and produce an indicator summary |
make_figures.py |
Data charts such as load, output characteristics, operation, and scale comparison |
make_context_figures.py |
Monthly temperature, precipitation, and radiation charts, and power system wiring schematic |
make_site_map.py |
Draw a location schematic from the KML site boundary and load coordinates |
fetch_nasa_power.py |
Download multi-year climate statistics for the site from NASA POWER |
For the input formats, commands, and parameters of each script, see figures.md Section 3.
Working principles
- The scale, load configuration, and site filed by the owner take priority; the report is responsible for supporting the argument, not overturning it. If contradictions are found, tell the user and let the user decide.
- A single number has only one source: electricity quantity, hours, and ratios are all calculated from the same set of hourly data, and financial indicators come from the calculation table worksheet specified by the user; when upstream data changes, regenerate the charts, then go back and revise the main text.
- Cite the calculation table as-is. If formula errors are found, report them to the user first, and correct them only after approval and with a record kept.
- The main text is for the reviewers: do not write internal processes such as "after checking the calculation table" or "we believe," and do not find fault with the owner or policy documents; [To be confirmed by the owner] is only used for facts that the owner needs to supply before delivery.
- Structure follows the reference: when the user provides a format reference or an existing chapter framework, follow its subsection structure and naming, and merge new requirements into the closest existing subsection.