Six Fundamentals to Understand Partial Shading Simulation in PVSyst

Contents

• Why partial shading simulation becomes important in PVSyst

• Fundamental 1 Partial shading is not just a matter of “getting a little darker”

• Fundamental 2 Separate the shading source and the time of occurrence

• Fundamental 3 Do not separate array layout from string configuration

• Fundamental 4 Read not only annual values but seasonal and time-of-day biases

• Fundamental 5 Use comparative simulations to determine the impact of shading

• Fundamental 6 Reverse-check results against on-site conditions

• How to apply PVSyst partial shading simulation in practice

Why partial shading simulation becomes important in PVSyst

For practitioners performing solar PV simulations with PVSyst, understanding partial shading is an unavoidable topic. When evaluating power generation, module output, azimuth, tilt, PCS capacity, loss settings, and so on tend to attract attention, while partial shading is often treated lightly as just another input item. In reality, if the approach to partial shading is weak, not only the annual generation estimate but also the validity of the array design and the evaluation of alternative proposals can become unstable.

What requires particular attention in practice is that partial shading is not simply an issue of shaded area. Even if only part of a module is shaded, the way generation falls is not necessarily proportional to the shaded area. The result depends greatly on where the shading occurs, at what times of day it occurs, and how the strings are configured. In other words, partial shading is a practical concern that spans layout design, electrical design, and generation forecasting.

Moreover, how partial shading is handled affects the quality of layout assessments. If you pack arrays tightly to use the site efficiently, the layout may look good on paper. However, if that causes severe shading at particular seasons or times of day, the realized generation may fall short of expectations. Conversely, designs that conservatively account for shading may look inefficient in terms of layout density but can be superior in annual stability and ease of explanation.

Also, in internal comparisons and report writing, you need to explain why you chose a given layout. If you can present not only generation figures but also how you assessed partial shading, the persuasive power of the design proposal increases. Understanding PVSyst’s partial shading simulation is not only about quantifying shading losses but also about building the rationale for design decisions.

Below we organize six basics that practitioners should grasp to understand partial shading simulation in PVSyst. The focus is not only on operational steps but also on how to read results and connect them to design.

Fundamental 1 Partial shading is not just a matter of “getting a little darker”

The first point to grasp when understanding partial shading is not to treat shading simply as reduced irradiance. In practice, it is common to intuitively think that if part of the area is shaded, generation will drop roughly in proportion to that fraction. But the significance of handling partial shading in PVSyst is precisely that such simplification is insufficient. Depending on how the shading occurs, the impact on generation can be greater than it appears.

Even visually similar shading can produce different losses depending on which position on the module is shaded, which column is affected, or which group it affects. For example, a thin shadow at the lower edge of a column and shading concentrated on a part of a string have different characteristics in terms of annual energy impact. If you use PVSyst in practice, you must look at the quality of the shading, not just its presence. If this is left ambiguous, the evaluation of alternative designs will be shallow.

Partial shading is not only a reduction in irradiance. Shading can cause differences in the cohesion of arrays and in per-string behavior. When that happens, the generation loss manifests not just as a reduction in light absorption but as a systemic response of the whole system. If you don’t understand this in practice, you are likely to underestimate the impact of slightly tighter layout packing.

To internalize this fundamental, stop thinking about partial shading in terms of area ratios. When inspecting partial shading in PVSyst, be mindful of where, to what extent, and under what conditions shading occurs. If you understand shading as a phenomenon at the intersection of layout conditions and electrical conditions rather than merely a dark patch, your interpretation of results becomes much more practical.

Fundamental 2 Separate the shading source and the time of occurrence

To understand partial shading simulation, it is important to separate the shading source from the time periods when it occurs. In practice, discussions often proceed as a binary “shading or not,” but that perspective alone is insufficient in PVSyst. The evaluation changes depending on where the shading originates, whether it occurs mainly in the morning and evening, whether it is strong in winter, or whether it gradually affects performance year-round.

For example, shading from adjacent arrays is closely related to inter-row spacing and tilt design. On the other hand, shading from surrounding trees or structures relates to understanding off-site conditions or existing conditions. The approach differs between shading that can be mitigated in design and shading that must be accepted as a premise. When reading PVSyst results, organizing which source the shading comes from makes it easier to consider countermeasures.

Time-of-day considerations are also important. Shading that appears briefly only in the morning and evening has a different implication for annual generation than shading that extends long into winter. In practice, hearing that there is shading may sound like a major issue, but depending on the time of occurrence and season, it may be acceptable for the project. Conversely, a seemingly minor shadow concentrated in a specific time slot that affects critical output ranges should be treated carefully.

As a countermeasure, when evaluating partial shading, first organize the shading sources and then check in which time periods or seasons the impact is pronounced. The purpose of performing partial shading simulation in PVSyst is not just to confirm the existence of shading but to understand the character of that shading. Simply separating the types of shading and their time windows makes layout evaluation much clearer.

Fundamental 3 Do not separate array layout from string configuration

To correctly understand partial shading, it is important not to treat array layout and string configuration separately. PVSyst allows you to input layout and electrical conditions individually, but in practice the two are deeply connected. Shading arises from the array layout, but how that shading manifests in generation depends on how strings are grouped electrically.

For example, if columns that are prone to shading and columns that are not are placed within the same string group, interpreting the simulation results becomes difficult. It becomes hard to pinpoint why a loss occurred or which block has issues. Conversely, if areas with similar conditions are naturally separated into distinct arrays and string groups, the impact of partial shading becomes easier to read. PVSyst’s partial shading simulation is a tool for checking layout validity and for inspecting the quality of electrical grouping.

In practice, you may be tempted to fill the site with arrays first and then organize the string configuration afterward. That approach tends to mix shading effects and makes problems apparent later. Especially for sites with tight constraints, if you don’t consider layout and stringing simultaneously, you can end up with a design that looks workable but has widely varying shading conditions that are hard to manage.

As a countermeasure, when examining partial shading simulations, confirm not only the presence of shading but also which combinations of array layout and string configuration produce the observed impacts. To understand partial shading in PVSyst, you need to evaluate shading within the connection between layout design and electrical design, not as an isolated loss. With this mindset, simulation results become design improvement hints rather than mere numbers.

Fundamental 4 Read not only annual values but seasonal and time-of-day biases

To understand partial shading simulation, it is also important not to judge solely by annual generation. PVSyst clearly shows final annual values, so attention naturally goes there. However, the impact of partial shading is not uniform throughout the year. Because shading often shows seasonal and time-of-day biases, the annual total alone may not reveal the full character of a proposal.

For example, shading that is strong in winter mornings and evenings has a different design implication from shading that works slightly year-round, even if the annual loss looks the same. Some shading may appear small in the annual figure but is concentrated in certain time slots and can affect the relative merits of alternative proposals. Conversely, losses that appear larger in the annual total may be limited to a restricted season and therefore be acceptable in design. In practice, the ability to read this difference changes the quality of judgment.

Also, by observing seasonal and time-of-day biases you can more easily explain why a given layout is advantageous or disadvantageous. Rather than concluding simply that the annual value is low so shading is bad, organizing the degree of impact by season makes your internal explanations more persuasive. PVSyst makes it easy to read monthly and hourly trends, so use that strength when evaluating partial shading.

As a countermeasure, when reviewing partial shading simulation results, pay attention not only to annual generation but also to seasonal differences and time-of-day biases. Doing so makes it easier to judge how significant the shading is for the design. When understanding partial shading in PVSyst, use the annual total as an entry point but follow through to look at the bias in how impacts appear.

Fundamental 5 Use comparative simulations to determine the impact of shading

To make partial shading simulation useful in practice, it is essential to use comparative simulations to determine shading impacts. PVSyst allows you to analyze a single proposal in detail, but in practice the significance of shading often becomes clear only when compared with alternatives. For example, comparing proposals with slightly wider inter-row spacing, reduced tilt, or more aisles helps reveal the trade-off between shading losses and layout efficiency.

In practice, you may want to avoid shading simply by increasing spacing, but that can reduce site utilization and capacity. Conversely, packing arrays densely may increase shading impacts. Which is better cannot be determined by general rules. The point of running comparative simulations in PVSyst is to confirm which balance is appropriate for the specific project. Eliminating shading losses entirely is not necessarily the right answer; deciding how much shading to accept is part of design judgment.

Also, comparative simulations make it less likely to overestimate or underestimate shading effects. Looking at a single proposal can make shading appear either a major problem or a minor one. But when multiple proposals are lined up, it becomes clear what is lost by reducing shading and what is gained by accepting it. This perspective is very important when deciding on the final proposal in practice.

As a countermeasure, for projects where partial shading is a key issue, always create multiple layout proposals and compare them. When doing so, keep conditions other than the points you want to compare as similar as possible so that differences are easily read as the effects of shading. To understand partial shading in PVSyst, it is important not only to evaluate a single proposal absolutely but also to read the meaning of shading relatively through comparison.

Fundamental 6 Reverse-check results against on-site conditions

Finally, it is important to reverse-check simulation results against on-site conditions. PVSyst is excellent at turning organized conditions into numbers, but if the input assumptions diverge from on-site understanding, the results will diverge as well. Partial shading in particular is closely related to site boundaries, surrounding structures, slope orientation, aisles, and existing equipment, so relying only on desk-based assumptions can be dangerous.

In practice, when simulation numbers look neat you may be tempted to accept them as-is. But what you should really check is whether the pattern of shading matches on-site impressions. For example, if shading should be strong in the morning on site but the results do not show that, or vice versa, you need to review layout assumptions and shading modeling. Because PVSyst’s numbers can look precise, reconciling them with on-site intuition is indispensable.

Reverse-checking against on-site conditions also makes it easier to translate partial shading simulation results into design improvements. You will see concrete improvements such as where moving arrays slightly would reduce shading, which aisle locations would improve cohesion, or which blocks should be separated to allow natural string configurations. The value of partial shading simulation is not only knowing losses but gaining hints about where to modify the design.

As a countermeasure, after viewing simulation results, always return to site conditions and layout assumptions. By iterating between drawings, site conditions, aisle planning, surrounding obstacles, and results, partial shading evaluation becomes closer to practice. Understanding partial shading in PVSyst means not just reading numbers on the screen but verifying their meaning against the field.

How to apply PVSyst partial shading simulation in practice

What is common across the six fundamentals above is the avoidance of treating partial shading simulation as merely a loss check. Understand the nature of partial shading, separate sources and time windows, keep array layout and string configuration linked, read seasonal and time-of-day biases as well as annual values, confirm the meaning of shading with comparative simulations, and finally reverse-check results against site conditions. When this flow is followed, PVSyst partial shading simulation becomes not just number checking but a basis for design decisions.

For practitioners, the goal is not only to reduce shading losses close to zero. The real value is understanding how important the shading is within the project, how much to accept, and what to improve—and being able to explain those choices. A shallow understanding of partial shading can lead to overestimating site utilization efficiency or, conversely, an excessive fear of shading that wastes usable area. The purpose of using PVSyst is to find that balance through comparison and verification.

Also, improving the accuracy of partial shading requires not completing the process with desk-based simulation alone. If site information such as site boundaries, slope direction, surrounding structures, aisles, and existing conditions is ambiguous, shading modeling will be weak. To connect PVSyst results to practice, you need to iterate between site understanding and simulation to refine how shading appears. Partial shading is not something solved purely in calculations; it must be evaluated together with site conditions.

In that sense, when you want to secure position confirmation or coordinate acquisition more reliably in the field, it can be effective to utilize high-precision GNSS positioning devices mounted on an iPhone, such as LRTK. If on-site position information and site conditions are easier to organize, the layout assumptions and surrounding conditions for PVSyst partial shading simulation become clearer. By improving desktop comparison accuracy with PVSyst and supporting on-site understanding with LRTK, partial shading evaluation shifts from mere loss confirmation toward site-grounded design judgment. Carefully understanding partial shading simulation not only improves the accuracy of generation forecasts but also enhances the practical capability to link desk work and field work.