pvsyst_import_house_pv_scene
Imports a generated house/PV scene into an open PVsyst project, assigns regions to source orientations, verifies native geometry, and saves a new variant for simulation.
Instructions
[Projects & Variants] Import a generated house/PV scene using the already open native PVsyst GUI. This bounded Windows path targets Chinese PVsyst 8.1.6 rev49278 with native logical DPI96 and the recorded physical window metrics, with the matching workspace and recipe project already open on its project page. Supports one or two PV regions; creation/standard export retains its 64-region limit. Unknown GUI metrics, dialogs, source/PAN mismatches and unsupported scene dialects stop rather than patching private VC data or guessing control positions. dry_run reads state only: no activation, key/mouse input or clipboard access. Execute with dry_run=false AND confirm=true, then leave the native desktop alone: selects the clean source variant, imports PVC2 and assigns its regions to the declared source orientation(s). The bounded two-orientation path explicitly places each table and verifies native SHD/saved VC geometry and a real GUI reload. It then runs PVsyst's scene-validity check and shading table, and saves a NEW native variant with the explicit display title variant_name (1..80 printable UTF-8 bytes). Native warnings beyond the expected beta notice stop; invalid geometry is returned as the software's own text. Any failure leaves the current window for inspection; an already-created variant path is disclosed even if postchecks fail. No automatic retry, source overwrite, application start/exit or INI modification is performed. Native validity text replaces the clipboard only after this confirmed operation; only the newly copied native text is read, never the earlier clipboard. imported/native_geometry_verified become true only after native persistence checks; native_consumption_verified stays false until a separate native simulation. shading_mode=module_layout additionally uses native placement and automatic string allocation, then selects detailed electrical shading. This opt-in requires two fixed source groups, one landscape zero-spacing table and one independent string (1..100 modules, one inverter/MPPT) per source array1/2. The saved module cells and native table/array links are checked; the selected mode is checked after GUI reload. Use pvsyst_run_simulation on the returned variant for energy/shading consumption. method="native" (opt-in) builds a NEW native input variant from the same supported recipe without any GUI, INI, clipboard, licence or engine action. It supports only two fixed orientations, two landscape zero-spacing tables, source arrays 1/2 with one independent string/inverter/MPPT each and the same PAN/OND; unsupported recipes stop before writing. dry_run builds and verifies the native records in memory only. Execution requires dry_run=false AND confirm=true and writes one new variant; the status is native_variant_created; stored_geometry_verified/stored_module_layout_verified reflect the STORED record only, while native_geometry_verified/native_module_layout_verified, native_consumption_verified and imported stay false because PVsyst has not loaded or consumed it; run an explicit simulation to verify consumption. dry_run writes nothing and keeps both stored flags false but still reports the passed precheck. The source variant/PAN are never modified.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| method | No | gui | |
| confirm | No | ||
| dry_run | No | ||
| scene_name | Yes | ||
| shading_mode | No | linear | |
| variant_name | Yes |