System image
A 3D rendering of the system is shown at the top of the System tab and stays visible across all of its sub-tabs. The image is representative of the current inputs and redraws itself as you change them, so you can confirm the layout, structure and dimensions visually before running a simulation.
The “active” modules are drawn within a wireframe that marks the boundary of the unit system, and the surrounding “ghost” modules represent the infinite field that the unit system tiles into during ray tracing (see Ray tracing methodology). The module colours are for display only and are not based on simulation inputs.
A similar 3D system image is shown on the Output Timestep viewer page.
System image settings
Section link: System image settingsOpen the settings by clicking the menu icon in the top-right corner of the image. This opens the System image settings dialogue. Every option in this dialogue changes the appearance of the image only; none of them affect the simulation.
Display
Section link: DisplayAdjust these settings as needed to examine the 3D scene. Note that there are performance implications for the drawing of the 3D scene. For example, enabling shadows requires more processing power and the image may draw more slowly as a result.
Infinite system, Show or hide the repeated ghost modules that represent the infinite field around the unit system.
Hide output, Hide the simulation output overlay so that only the system geometry is shown. Only applies to the Timestep viewer on the output tab.
Ground type (image only)
Section link: Ground type (image only)The Ground type selector changes how the ground is drawn beneath the system. With one exception, it has no effect on the ground albedo used in the simulation:
- Calculated from material is a special case. The ground is rendered from the actual simulation values, so its brightness and colour reflect the ground’s optical properties. A fully absorbing ground, for example, appears black.
- Grass, grid, sand, dirt, water, water (darker) and snow are decorative tiled textures that make the image look realistic. They bear no relation to the simulated ground.
Actions
Section link: ActionsShow tracker path, Animates a single-axis tracker through its daily range of rotation. Available for tracker systems only.
Module tilt
Section link: Module tiltThe tilt shown depends on the system configuration and where the 3D system is displayed.
On the System input tab, modules in Fixed and Waves systems are drawn at the configured tilt angle. The configured tilt angle is also used for a single-axis tracker with tracking set to None.
For a single-axis tracker with tracking enabled, the modules are drawn at the configured upper tilt limit. This is the upper limit as entered, which is not necessarily the limit with the greatest absolute value.
On the Output Timestep viewer, the modules are drawn at the tilt used to solve the selected timestep.
See Orientation for the corresponding layout inputs.
Collision detection / validation of 3D scene
Section link: Collision detection / validation of 3D sceneSunSolve validates the preview geometry when the scene is first built and whenever an input change rebuilds its geometry. The check runs asynchronously in a separate scene, and is distinct from the full input validation performed before a simulation runs.
The unit-system bounds are checked first. This check allows a tolerance of 0.01 m and detects geometry extending beyond the X or Y boundaries; it does not check the vertical boundary. Module collisions are checked only if the bounds check succeeds. Validation stops at the first failure and displays its message in an orange overlay at the bottom of the image. The overlay is hidden while validation is pending and when validation succeeds.
For Fixed, Waves and non-tracking configurations, module collisions are checked at the configured tilt. For a tracking configuration, SunSolve checks 11 evenly spaced angles, including both limits, across the permitted tilt range. It stops checking when it finds the first collision.
Because validation uses a separate scene, the visible preview does not move through the checked angles or stop at the angle where a collision is found. A warning does not clamp the tracker angle or change the configured inputs.
Warning,, dimensions of scene extends beyond unit system, Part of the scene extends more than 0.01 m beyond the unit-system boundary in the X or Y direction. Review the unit-system dimensions and the position and size of its components.
Warning,, module intersects with object : object name, A module intersects the named structure or object at the configured tilt,, or at one of the sampled tracker angles. Review the module clearance,, structure and tracker tilt limits.
Unit system bounds not found, The preview could not find the boundary required for its geometry check. This normally indicates an incomplete or invalid system definition rather than a clearance problem.
No modules found., The preview could not identify any module geometry to check. Confirm that the system contains a valid module definition.
Navigating the 3D image
Section link: Navigating the 3D imageUse the following controls to examine the system from different positions:
- Drag with the left mouse button to rotate the view around the system.
- Use the mouse wheel or a trackpad pinch gesture to zoom in or out.
- Hold Ctrl while dragging with the left mouse button, or drag with the right mouse button, to pan the view.
- On a touchscreen, drag with one finger to rotate. Use two fingers to pan and pinch to zoom.