PV & renewable system design
Design PV systems and simulate yield to a target.
20 project-authored proposals · taxonomy v1.1 · 0 new benchmark runs. Verifiers and partial-credit rules below are designs, not executed results.
- Typical applications
- PVsyst · SAM · HelioScope
- Class GUI-need label
G2· GUI-essential
Task proposals · 20
Expand to inspect the complete original wording and proposed checks. Original proposal text remains English in both interfaces.
R07.08.01.02-T01 Model a residential PVWatts system in SAM and report annual energy
Original instruction
In NREL SAM (desktop), create a PVWatts / Residential case for a 7.2 kWdc roof array at the site in input/weather_denver.csv (TMY), tilt 25 deg, azimuth 190 deg, 14% system losses, DC/AC 1.2. Run the simulation, save output/res_pv.sam and write the annual AC energy (kWh) to output/answer.txt.
- Platforms
mac· macOSwin· Windows- Applications
- SAM
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP07· Simulation result- Conditions
- None declared
- Proposed difficulty
- 2 / 5
Proposed verifier
Grader opens the .sam file with SAM's SSC runner: inputs match spec exactly and recomputed annual energy within 0.5% of answer.txt. PySAM and the SSC library are absent from the agent VM and SAM's LK script editor is disabled; a .sam not saved by the SAM desktop app fails version-metadata checks.
Proposed partial credit
40% case inputs correct; 30% simulation saved; 30% annual energy within tolerance.
R07.08.01.02-T02 Size strings for a 100 kWp PVsyst project inside the inverter window
Original instruction
In PVsyst, create a grid-connected project for the site in input/site_lyon.SIT with weather input/lyon_tmy.MET. Use module 'Synth 450M' and inverter 'Synth 50K' from the project database, 100 kWp +/-2%. Choose string length and count so Vmpp stays in the MPPT window from -10 C to 70 C and Voc(-10 C) is below 1000 V, simulate and report PR and specific yield.
- Platforms
win· Windows- Applications
- PVsyst
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP07· Simulation result- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Grader reopens the .PRJ/.VCi in a clean PVsyst: string config satisfies voltage limits computed from the PAN/OND files, kWp in range, warnings list empty; re-simulated PR and yield within 0.5% of reported. PVsyst batch mode is disabled in the agent license and project/variant files edited outside PVsyst fail its checksum on reopen, so the work must be done in the PVsyst GUI.
Proposed partial credit
30% kWp and string config valid; 20% no PVsyst sizing warnings; 50% PR and yield match re-simulation.
R07.08.01.02-T03 Build a PVsyst near-shading scene from a roof plan
Original instruction
From input/roof_plan.pdf (dimensioned roof, 2 parapets, chimney, 3 PV rows at 15 deg), build the 3D near-shading scene in PVsyst for project fixtures/warehouse.PRJ, compute the shading factor table, use 'according to strings' electrical effect and simulate. Report the near-shading and electrical shading losses.
- Platforms
win· Windows- Applications
- PVsyst
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clickdrag· Drag & dropgeom· Precise geometryvis· Visual judgment- Work product
WP04· 3D/spatial model- Conditions
licensed· Licensed pro applong· Long-horizon- Proposed difficulty
- 4 / 5
Proposed verifier
Grader exports scene objects from the saved .SHD: object dimensions/positions within 0.1 m of the plan, PV rows match field orientation; shading loss within 0.3 pts and electrical loss within 0.3 pts of reference. 3D scene import and PVsyst batch mode are disabled in the agent license, and project/variant/.SHD files edited outside PVsyst fail its checksum on reopen, so the work must be done in the PVsyst GUI.
Proposed partial credit
40% scene geometry within tolerance; 20% shading table computed and electrical mode set; 40% losses within tolerance.
R07.08.01.02-T04 Lay out a 250 kWp rooftop array in HelioScope with keepouts
Original instruction
In the sandbox HelioScope project 'Depot 7' with the attached aerial image, draw the roof field segment, add keepouts for 3 HVAC units with 1 m setback and a 0.9 m fire-code edge setback, and fill with the specified 440 W module at 10 deg landscape so DC size is 250 kWp +/-2%. Run the energy simulation.
- Platforms
web· Any OS (web)- Applications
- HelioScope
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clickpath· Continuous pathgeom· Precise geometry- Work product
WP04· 3D/spatial model- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Grader exports the design (field segment and keepout polygons, module list): no module polygon within 1 m of HVAC keepouts or 0.9 m of roof edge; DC kWp in range; simulation exists. Designs created through the HelioScope API key are detected via audit log and fail.
Proposed partial credit
25% roof and keepouts drawn; 35% setback compliance; 25% DC size in range; 15% simulation run.
R07.08.01.02-T05 Optimize battery size for a commercial PV+storage case in SAM
Original instruction
In SAM, set up a Detailed PV + Battery / Commercial case using input/load_8760.csv, the TOU tariff in input/tariff_b19.json and a 300 kWdc array. Run a parametric sweep of battery capacity 0-600 kWh in 50 kWh steps (C-rate 0.5) and report the size with the highest after-tax NPV and its NPV in output/answer.txt.
- Platforms
mac· macOSwin· Windows- Applications
- SAM
- Interfaces
desk· Desktop GUI- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP12· Answer/decision- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
Grader re-runs the sweep from the saved .sam with SSC; reported optimum size exact and NPV within 1%. Parametric table must exist in the saved case.
Proposed partial credit
30% case built with load and tariff; 30% parametric sweep configured; 40% optimum and NPV correct.
R07.08.01.02-T06 Design a 5 MWac bifacial tracker plant to a specific-yield target
Original instruction
In PVsyst, design a ground-mount plant at input/site_atacama.SIT: single-axis trackers with backtracking, bifacial module 'Synth 580B', central inverters, 5 MWac, DC/AC 1.20-1.35. Choose GCR and pitch to reach >=2,050 kWh/kWp specific yield while staying within the 18 ha boundary in input/parcel.kml. Report GCR, DC/AC and yield.
- Platforms
win· Windows- Applications
- PVsyst · Google Earth Pro
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & formsgeom· Precise geometryvis· Visual judgment- Work product
WP07· Simulation result- Conditions
licensed· Licensed pro appmultiapp· Multi-applong· Long-horizon- Proposed difficulty
- 5 / 5
Proposed verifier
Grader re-simulates the saved project: yield >=2,050 kWh/kWp, DC/AC in range, 5 MWac exact; tracker field footprint (rows x pitch x length) fits the parcel area. Bifacial model and backtracking must be enabled. PVsyst batch mode is disabled in the agent license and project/variant files edited outside PVsyst fail its checksum on reopen, so the work must be done in the PVsyst GUI.
Proposed partial credit
20% plant configured (trackers, bifacial, backtracking); 20% DC/AC and AC size; 20% footprint fits; 40% yield target met.
R07.08.01.02-T07 Design a homeowner system in Aurora offsetting annual usage
Original instruction
In the Aurora Solar sandbox project 'Lee residence', trace the 4 roof planes from imagery, mark the vent and skylight obstructions, and place 400 W panels to offset 95-105% of the annual consumption in input/utility_bills_2025.pdf. No panels on the north plane. Save the design and export the performance report.
- Platforms
web· Any OS (web)- Applications
- Aurora Solar
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clickpath· Continuous pathgeom· Precise geometrymulti· Cross-app- Work product
WP04· 3D/spatial model- Conditions
licensed· Licensed pro app- Proposed difficulty
- 4 / 5
Proposed verifier
Grader reads the saved design via an admin export: roof plane pitch/azimuth within 3 deg of ground truth, no panel intersects obstruction polygons or the north plane, modeled offset 95-105% of the bill total (12-month sum read by grader). The sandbox tenant issues no Aurora API key, so the design can only be created in a browser session; the admin export records the creating session.
Proposed partial credit
25% roof planes traced within tolerance; 20% obstructions honored; 15% no north-plane panels; 40% offset in range.
R07.08.01.02-T08 Create a PVsyst module file from a manufacturer datasheet
Original instruction
From input/module_datasheet.pdf, create a new PV module in PVsyst's database with the STC and NOCT electrical values, temperature coefficients, dimensions and cell count, and save it as Synth_455_HC.PAN. Do not edit any existing database entries.
- Platforms
win· Windows- Applications
- PVsyst
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
type· Text & formsclick· Point & click- Work product
WP09· Files & folders- Conditions
licensed· Licensed pro app- Proposed difficulty
- 2 / 5
Proposed verifier
Grader parses the .PAN: Pnom, Voc, Isc, Vmpp, Impp, muIsc, muVoc, dimensions and cell count exactly match datasheet; PVsyst-fitted one-diode params and PVsyst's version stamp present (created by PVsyst's module tool, not a template copy); database-folder writes by other processes are detected via the file audit log. Database hashes of other files unchanged.
Proposed partial credit
60% electrical/thermal values exact; 20% mechanical data; 20% saved without collateral edits.
R07.08.01.02-T09 Estimate wind farm AEP with wakes in SAM
Original instruction
In SAM, set up a Wind / Single Owner case using input/wind_site.srw and the turbine power curve in input/synth_3p6MW.csv for the 12-turbine layout in input/layout.csv, with the Simple Wake model and 12% non-wake losses. Report net AEP (MWh) and capacity factor in output/answer.txt and save output/wind.sam.
- Platforms
mac· macOSwin· Windows- Applications
- SAM
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP07· Simulation result- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
Grader reruns the saved case: layout coordinates, curve and losses exact; AEP within 0.5% and capacity factor within 0.2 pts of answer. PySAM and the SSC library are absent from the agent VM and SAM's LK script editor is disabled; a .sam not saved by the SAM desktop app fails version-metadata checks.
Proposed partial credit
40% inputs correct; 20% wake model set; 40% AEP and CF within tolerance.
R07.08.01.02-T10 Configure a multi-orientation roof with two-MPPT inverters in PVsyst
Original instruction
In PVsyst, model a roof with east (90 deg), west (270 deg) and south (180 deg) planes as three orientations, connected to two 2-MPPT inverters so that no MPPT input mixes orientations. Use the strings listed in input/roof_strings.xlsx, simulate and report the mismatch and inverter clipping losses.
- Platforms
win· Windows- Applications
- PVsyst · Excel
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G3· GUI-only- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP07· Simulation result- Conditions
licensed· Licensed pro appmultiapp· Multi-app- Proposed difficulty
- 3 / 5
Proposed verifier
Grader reopens the project: 3 orientations, MPPT assignment matches spreadsheet, no MPPT mixes orientations; re-simulated losses within 0.2 pts of report. PVsyst batch mode is disabled in the agent license and project/variant files edited outside PVsyst fail its checksum on reopen, so the work must be done in the PVsyst GUI.
Proposed partial credit
30% orientations defined; 40% MPPT assignment valid; 30% losses match re-simulation.
R07.08.01.02-T11 Compute the same system yield in pvlib (control pair of T02)
Original instruction
Control pair of T02: with pvlib-python only, model the 100 kWp system from T02 (same weather, PAN/OND parameters exported in input/t02_params.json, same string configuration and loss assumptions) and write output/yield.json with annual energy, PR and specific yield.
- Platforms
mac· macOSwin· Windowslin· Linux- Applications
- pvlib · Python
- Interfaces
term· Terminal- GUI need · task setting
CL· CLI-sufficient- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
code· Code & commands- Work product
WP07· Simulation result- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
Control pair of T02: compare to the PVsyst reference run; specific yield within 3% and PR within 2 pts. Script must run deterministically from the provided inputs.
Proposed partial credit
30% model runs end to end; 40% specific yield within tolerance; 30% PR within tolerance.
R07.08.01.02-T12 Find the least-cost renewable microgrid in HOMER Pro
Original instruction
In HOMER Pro, model an island grid with the load in input/island_load.csv, solar resource from input/ghi.csv, diesel fuel at $1.40/L and the component costs in input/costs.xlsx. Search PV 0-800 kW, battery 0-4 MWh and one 500 kW genset to find the least-COE system with 0% unmet load and >=70% renewable fraction.
- Platforms
win· Windows- Applications
- HOMER Pro · Excel
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G3· GUI-only- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP07· Simulation result- Conditions
licensed· Licensed pro appmultiapp· Multi-app- Proposed difficulty
- 4 / 5
Proposed verifier
Grader reopens the .homer file, re-runs optimization: chosen system feasible (0% unmet, RF>=70%) and its COE within 1% of the true optimum within the search space. Search space and costs must match inputs. HOMER's MATLAB Link add-on is disabled in the agent license and no other optimizer is installed; .homer files written outside HOMER Pro are detected via the file audit log.
Proposed partial credit
25% resources and loads loaded; 25% search space and costs; 20% constraints set; 30% optimal system selected.
R07.08.01.02-T13 Add a far-horizon profile and quantify its loss in PVsyst
Original instruction
Open fixtures/alpine_school.PRJ in PVsyst. Import the horizon profile from input/horizon.csv (azimuth, elevation), keep a copy of the variant without horizon, simulate both and report the horizon loss in percent in output/answer.txt.
- Platforms
win· Windows- Applications
- PVsyst
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G3· GUI-only- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP07· Simulation result- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Grader reads both variants: horizon points match CSV within 0.5 deg; difference in annual energy within 0.2 pts of reported loss. PVsyst batch mode is disabled in the agent license and project/variant files edited outside PVsyst fail its checksum on reopen, so the work must be done in the PVsyst GUI.
Proposed partial credit
40% horizon imported correctly; 30% two variants simulated; 30% loss reported.
R07.08.01.02-T14 Wire a carport plus rooftop design in HelioScope within loss limits
Original instruction
In HelioScope sandbox project 'Civic Center', design a carport field over parking polygon A and a rooftop field on building B, assign two inverter types per input/equipment.xlsx, define wiring zones with string lengths 14-18 modules and combiner placement so DC wiring loss is <=1.5%. Run simulation and export the CAD layout.
- Platforms
web· Any OS (web)- Applications
- HelioScope · Excel
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clickpath· Continuous pathgeom· Precise geometrymulti· Cross-app- Work product
WP04· 3D/spatial model- Conditions
licensed· Licensed pro applong· Long-horizonmultiapp· Multi-app- Proposed difficulty
- 5 / 5
Proposed verifier
Grader exports the design: both fields inside their polygons, string lengths within 14-18, inverter types per sheet, reported DC wiring loss <=1.5%, simulation present; DXF export exists and parses. The sandbox issues no HelioScope API key, so the design can only be built in a browser session; the project audit log is checked for non-UI edits.
Proposed partial credit
25% fields placed correctly; 25% inverter/strings; 30% wiring loss target; 20% simulation + CAD export.
R07.08.01.02-T15 Calibrate SAM soiling and degradation to a year of meter data
Original instruction
Open fixtures/school_pv.sam (Detailed PV). Using input/meter_2025.csv (monthly kWh) and input/weather_2025.csv, adjust monthly soiling losses (0-10%) and first-year degradation (0-1%) so modeled monthly energy matches the meter with CV(RMSE) <=5%. Save output/calibrated.sam and output/calib.csv.
- Platforms
mac· macOSwin· Windows- Applications
- SAM · Excel
- Interfaces
desk· Desktop GUI- GUI need · task setting
HY· Hybrid- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & formsvis· Visual judgment- Work product
WP07· Simulation result- Conditions
multiapp· Multi-app- Proposed difficulty
- 4 / 5
Proposed verifier
Grader reruns the saved case: monthly CV(RMSE) vs meter <=5% (partial up to 10%), parameters within allowed ranges, weather file swapped to 2025 data.
Proposed partial credit
20% weather file replaced; 20% parameters in range; 60% CV(RMSE) score (full credit at <=5 pct).
R07.08.01.02-T16 Design a residential system with optimizers in SolarEdge Designer
Original instruction
In SolarEdge Designer (sandbox account), create a site at the address in input/site.txt, draw the two roof planes from the provided image, place 22 panels, assign power optimizers and an inverter so string design rules pass with zero errors, and save the project and its PDF report.
- Platforms
web· Any OS (web)- Applications
- SolarEdge Designer
- Interfaces
brow· Browser- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clickpath· Continuous pathgeom· Precise geometry- Work product
WP04· 3D/spatial model- Conditions
- None declared
- Proposed difficulty
- 3 / 5
Proposed verifier
Grader reads the saved project export: 22 panels, roof planes within 3 deg of reference, string/optimizer validation shows zero errors, PDF report present and matches project ID. Designer has no project-creation API and the sandbox account holds no API key, so the project can only be built in a browser session.
Proposed partial credit
30% roof planes; 20% panel count; 40% electrical validation passes; 10% report exported.
R07.08.01.02-T17 Report LCOE change after a PPA escalation edit in SAM
Original instruction
Open fixtures/utility_pv.sam in SAM. Change the PPA escalation rate from 1.0% to 2.5% per year, rerun, and report real LCOE before and after (cents/kWh, 2 decimals) in output/answer.txt. Save as output/utility_pv_esc.sam.
- Platforms
mac· macOSwin· Windows- Applications
- SAM
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
CL· CLI-sufficient- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP12· Answer/decision- Conditions
- None declared
- Proposed difficulty
- 2 / 5
Proposed verifier
Grader verifies only the escalation input changed (diff of saved case variables) and recomputes LCOE values; both within 0.02 cents/kWh. PySAM and the SSC library are absent from the agent VM and SAM's LK script editor is disabled; a .sam not saved by the SAM desktop app fails version-metadata checks.
Proposed partial credit
30% correct single edit; 70% before/after LCOE values.
R07.08.01.02-T18 Produce a P50/P90 bankability report in PVsyst
Original instruction
For fixtures/solarpark_12MW.PRJ in PVsyst, set the uncertainty inputs from input/uncertainty_memo.pdf (meteo interannual variability, model, module, soiling), run the simulation and P50-P90 evaluation, export the PDF report and record P50, P90 (single year) and P90 (10-year) in output/p_values.csv.
- Platforms
win· Windows- Applications
- PVsyst
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G3· GUI-only- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP01· Document- Conditions
licensed· Licensed pro app- Proposed difficulty
- 4 / 5
Proposed verifier
Grader reopens the variant: each uncertainty value equals the memo; recomputed P50/P90 values within 0.5%; PDF report text parsed for the same values. PVsyst batch mode is disabled in the agent license and project/variant files edited outside PVsyst fail its checksum on reopen, so the work must be done in the PVsyst GUI.
Proposed partial credit
35% uncertainty inputs exact; 15% report exported; 50% P-values match.
R07.08.01.02-T19 Micro-site a 10-turbine wind farm in WAsP to an AEP target
Original instruction
In WAsP, load the terrain map input/ridge.map, roughness and the generalized wind climate input/site.lib. Place 10 turbines of input/synth_4MW.wtg inside the boundary input/lease.kml with minimum 4D crosswind and 7D downwind spacing so net AEP is >=118 GWh. Save the workspace and export the turbine site list.
- Platforms
win· Windows- Applications
- WAsP · Google Earth Pro
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clickdrag· Drag & dropgeom· Precise geometryvis· Visual judgment- Work product
WP04· 3D/spatial model- Conditions
licensed· Licensed pro applong· Long-horizonmultiapp· Multi-app- Proposed difficulty
- 4 / 5
Proposed verifier
Grader recomputes: all turbines inside the lease, spacing rules met per prevailing sector, net AEP from WAsP rerun >=118 GWh (partial above 112). PyWAsP is not installed and WAsP automation is disabled in the agent VM; workspace files edited outside WAsP are detected via the file audit log.
Proposed partial credit
20% inputs loaded; 25% turbines inside boundary; 25% spacing rules; 30% AEP target.
R07.08.01.02-T20 Size an off-grid telecom PV system in PVsyst for 3-day autonomy
Original instruction
In PVsyst, design a stand-alone system for a 48 V telecom shelter with the constant 1.2 kW load in input/load_profile.csv at input/site_kenya.SIT: battery autonomy 3 days, loss-of-load probability <=1%, minimal PV array. Report PV kWp, battery Ah and LOL in output/answer.txt.
- Platforms
win· Windows- Applications
- PVsyst
- Interfaces
desk· Desktop GUI- GUI need · task setting
G2· GUI-essential- GUI need · ordinary access
G2· GUI-essential- Interaction primitives
click· Point & clicktype· Text & forms- Work product
WP07· Simulation result- Conditions
licensed· Licensed pro app- Proposed difficulty
- 3 / 5
Proposed verifier
Grader reopens and re-simulates: LOL <=1% and autonomy >=3 days; PV size within 10% of minimal feasible kWp computed by grader search. PVsyst batch mode is disabled in the agent license and project/variant files edited outside PVsyst fail its checksum on reopen, so the work must be done in the PVsyst GUI.
Proposed partial credit
30% stand-alone system configured; 40% LOL and autonomy met; 30% PV size near minimum.
Mapped research references
No benchmark reference is assigned to this class in the current mapping.