Seven checkpoints where shading settings in PVSyst make a difference

Table of Contents

• Why shading settings in PVSyst become important

• Checkpoint 1: Have you first organized the sources of shading?

• Checkpoint 2: Are the site conditions and layout conditions matched to reality?

• Checkpoint 3: Are you viewing row spacing and tilt angle as a set?

• Checkpoint 4: Are you not judging the impact of partial shading only by area ratio?

• Checkpoint 5: Are you checking for seasonal and time-of-day biases?

• Checkpoint 6: Are you linking string configuration and electrical impacts?

• Checkpoint 7: Are you back-checking results with alternative proposals and on-site information?

• How to translate PVSyst shading settings into practical outcomes

Why shading settings in PVSyst become important

For practitioners running PV simulations in PVSyst, shading settings are not just auxiliary items. Module capacity, azimuth, tilt angle, PCS conditions, and loss settings are easy to understand and therefore tend to draw attention first. However, on real sites, even when those conditions are well arranged, lax handling of shading can significantly undermine overall result reliability. In other words, shading settings should be regarded not as fine-tuning of energy yield but as prerequisite conditions that support the validity of the entire design.

What often differentiates results in practice is treating shading simply as a question of shade. It matters not only whether shading occurs, but where the shading comes from, at which times it is strongest, and which arrays or strings it affects — all of which fundamentally change the meaning of the results. Even visually similar shading should be handled differently depending on whether it can be improved by design or must be accepted as a baseline condition. Understanding PVSyst’s shading settings is not merely confirming the presence of shadows but translating the character of those shadows into the design.

Shading settings also link directly to how the site is used. Packing arrays tightly to make efficient use of land may look promising on paper in terms of yield. But if winter mornings and evenings or inter-row shadows turn out to be stronger than expected, that layout can be disadvantageous over the course of a year. Conversely, a layout with a little more margin may be disadvantaged in capacity but yield consistently smaller shading impacts and be easier to justify. When using PVSyst in practice, you must check not only the magnitude of the numbers but also the shadow conditions on which those numbers are based.

Moreover, when explaining proposals internally or in comparison materials, you need to explain why you adopted a particular layout, why you selected that row spacing, and why you assumed those losses. If the rationale for the shading settings is well organized, it becomes easier to convey that a proposal is reasonable not just because it shows high yield but because it accounts for shading risk. Conversely, if shading settings are vague, the numbers may exist but the design rationale will appear weak. Therefore, PVSyst’s shading settings should be treated as central to practical decision-making, not merely a supplementary part of yield forecasting.

Checkpoint 1: Have you first organized the sources of shading?

The first place shading settings make a difference is how well you can organize the shading sources. In practice, people tend to think in a binary way — shading or no shading — but what matters in PVSyst is distinguishing where the shading originates. Self-shading between arrays, shadows from slopes or terrain, and shadows from off-site buildings or trees differ in both how easily they can be mitigated and how they affect generation. If you lump sources together without distinguishing them, it becomes hard to see what can be corrected.

For example, self-shading that can be improved by adjusting row spacing has a different design priority than shading caused by an off-site obstacle that is difficult to avoid. If self-shading is the main factor, there is room to improve by reviewing row spacing, tilt angle, and array orientation. On the other hand, if shading is caused by off-site buildings or tall trees, it may be hard to avoid completely, and you need to incorporate that exposure into your baseline assumptions. When performing shading analysis in PVSyst, sorting these differences beforehand makes the results far more practical.

Separating shading sources from the beginning also clarifies the meaning of comparative proposals. One proposal might focus on reducing self-shading, while another might shift arrays toward areas less affected by external obstacles. If you don’t see this difference, it is hard to explain why one proposal is advantageous even if the shading-loss numbers look similar. Because PVSyst summarizes results as annual yield and losses, it is important at the input stage to be conscious of categorizing the shading sources.

As a countermeasure, before entering shading settings, list shading causes inside and outside the site. Further separate those that can be improved from those you must accept as assumptions; this makes actionable design options clearer. When setting shading in PVSyst, don’t treat everything as a single shadow from the start — give meaning to each type of source.

Checkpoint 2: Are the site conditions and layout conditions matched to reality?

The next important point in shading settings is whether the site conditions and layout conditions are matched to reality. In PVSyst you can model arrays and obstacles visually, but if the underlying site conditions and layout assumptions diverge from reality, the results will be less useful in practice. In particular, taking site boundaries, slopes, site preparation conditions, clearances, access routes, and relationships with existing structures lightly can make the shading analysis numbers look neat while producing layouts that are infeasible on site.

A common practical mistake is to first fill the site with arrays in an idealized way and then check shading afterward. This approach often yields optimistic expectations of energy yield but can result in insufficient access routes, inadequate edge clearances, or impractically tight inter-row spacing, which show up as increased shading in reality. PVSyst’s shading analysis is meaningful only when conducted on a viable layout. If the layout itself is unrealistic, comparing shading losses does not lead to practical design decisions.

Matching site and layout conditions to reality also directly affects how well you can explain the results. If you can justify why you chose that row spacing, orientation, or which obstacles you included as shading assumptions, it makes internal review and revision easier. Conversely, vague input conditions leave the shading-loss numbers to stand alone. Because PVSyst is faithful to its input assumptions, the credibility of those inputs is critical.

As a countermeasure, before running shading settings, organize usable and unusable areas, access routes, clearances, and slope directions, and then create candidate layouts. Rather than checking shadows on an idealized layout, check them on layouts that follow site conditions; the results will be far more practical. What causes differences in PVSyst is not just the precision of the shading analysis but the realism of the layout being analyzed.

Checkpoint 3: Are you viewing row spacing and tilt angle as a set?

Whether you view row spacing and tilt angle as a set is another important point where shading settings make a difference. In practice, people sometimes decide the tilt angle first and then adjust row spacing to match, or they simply tighten row spacing to fit the site. But in PVSyst shading evaluation, tilt angle and row spacing must be treated as an integrated condition. Changing the tilt angle alters how shadows fall, and therefore the required spacing changes.

For example, increasing the tilt angle can improve irradiance conditions in some cases, but it also tends to increase shading on adjacent rows. Conversely, lowering the tilt angle can allow tighter row spacing, but it may alter overall yield and seasonal characteristics. PVSyst should be used to check these trade-offs. Optimizing only one variable can obscure the impracticalities that arise in the other.

Viewing row spacing and tilt angle together also makes the meaning of shading-loss numbers easier to understand. Even with the same annual loss, the evaluation changes depending on whether the loss results from prioritizing angle or prioritizing layout efficiency. Since you must ultimately decide on the final angle and spacing in practice, it’s important to read shading differences not merely as gains or losses but as design implications.

As a countermeasure, when setting shading, compare multiple combinations of row spacing and tilt angle. Clarify what you prioritize and what you compromise on so the differences in results are easier to interpret. In PVSyst, the basic approach is to evaluate tilt angle and row spacing together through how shadows form, not to decide them separately.

Checkpoint 4: Are you not judging the impact of partial shading only by area ratio?

A major source of difference in shading settings is judging the impact of partial shading solely by area ratio. In practice, it’s easy to intuitively assume that if the shaded area is small, the impact will be small. But the purpose of PVSyst’s partial-shading handling is to reveal that such simplification is insufficient. How shading affects generation is not determined by a simple percentage but by where the shading occurs and which groupings it impacts.

Even with similar shaded areas, results can differ if shading concentrates on part of a string versus spreading thinly over many modules. Also, shading at a row edge differs in meaning from shading at a critical location within a particular row. When using PVSyst in practice, do not evaluate shading solely by visual area. How shading affects generation depends on both array layout and electrical groupings.

This perspective is important because it changes the direction of design corrections. If you judge shading as negligible based only on area, you might accept it as is. In reality, however, slight changes to string grouping or reviewing row groupings might reduce the impact. Conversely, a visually large shadow might be acceptable when viewed over the whole year. PVSyst’s partial-shading simulation provides materials to interpret these differences.

As a countermeasure, check not only shaded area but also which rows, which groupings, and which time periods the shading affects. Rather than relying on area ratios alone, adopt the mindset of discerning the quality of the impact; this makes the interpretation closer to practical application. The difference PVSyst’s shading settings make is whether you can read the meaning of the shadow, not just how it appears.

Checkpoint 5: Are you checking for seasonal and time-of-day biases?

To correctly evaluate shading impact, you must check for seasonal and time-of-day biases. PVSyst clearly displays annual generation and annual losses, so there is a tendency to judge differences by yearly totals. However, shading does not act uniformly throughout the year. Some shading is strong only in winter, some is conspicuous only in mornings and evenings, and some gradually affects performance year-round. Drawing conclusions without viewing this can lead to misjudging shading importance.

In practice, there are times when you want to intuitively judge “it’s only in winter, so it’s not a big deal” or “it’s only in the morning, so it’s fine.” That intuition can be valid, but when analyzing with PVSyst it is safer to confirm that intuition with numbers and trends. Concentration of loss in particular times or seasons can appear small in annual totals. Conversely, the annual loss might be somewhat large but limited to timing that is acceptable in the design. In short, it’s important to look at the distribution of shading as well as the total.

Understanding seasonal and time-of-day biases also makes it easier to explain comparative proposals. A proposal that slightly widens row spacing may reduce winter-morning shading and, even if the annual difference is small, appear more stable. By contrast, a capacity-prioritized proposal may concentrate shading in specific time bands. PVSyst is a tool that helps read these differences, so you need to look beyond annual totals to the biases.

As a countermeasure, after checking annual values from shading settings, also examine seasonal and time-of-day tendencies. If you know when shadows are effective, it becomes easier to judge whether to adopt a proposal. The difference PVSyst makes is not just whether you ran an analysis but how deeply you read the results.

Checkpoint 6: Are you linking string configuration and electrical impacts?

One major reason shading settings make a difference is whether you connect string configuration and electrical impacts. In practice, people often first look at the existence or area of shading, and then check how generation drops. But when handling partial shading in PVSyst, what’s truly important is how that shading acts within the string configuration. Looking only at layout while ignoring electrical groupings makes it easy to misread the results.

For example, if you treat columns that are easily shaded and columns that are not in the same electrical grouping, you might understand the annual loss but not how that loss actually occurs. Conversely, if you naturally group areas with similar conditions, the shading impact becomes easier to interpret. To connect PVSyst shading analysis to practical design, you must check not only the visual shading but also the naturalness of the units that receive shading.

Holding this perspective also makes it easier to translate shading results into design improvements. If you cannot eliminate shading, you can review which groupings should take the hit or how to partition sections. Many projects cannot completely avoid shading, so how you accept its impacts in the design is crucial. PVSyst provides a basis for that judgment.

As a countermeasure, when checking shading settings, look not only at whether shading exists but at which array sections and string groupings are affected. Being aware of electrical impacts changes the weighting of shading and clarifies the priority of comparative proposals. The difference PVSyst’s shading settings make is whether you understand not only the appearance of shading but also its relationship with the array configuration.

Checkpoint 7: Are you back-checking results with alternative proposals and on-site information?

The final checkpoint that makes a difference is whether you back-check results using alternative proposals and on-site information. PVSyst returns numbers based on the conditions you input, and when the results look tidy it’s easy to assume the assumptions are correct. In practice, however, you need to verify result validity by comparing alternative layouts and cross-checking with on-site conditions. Whether you perform this back-check dramatically affects shading analysis accuracy.

Comparative proposals are effective because they let you see shading impacts relatively — compare proposals that reduce shading with those that prioritize capacity, or layouts that widen access with those that maximize site utilization. Looking at only one proposal makes it hard to judge whether a given loss is large or small and whether it should be accepted. Running comparisons in PVSyst makes design differences visible beyond shading-loss numbers.

But comparison alone is not enough. You must also check results against on-site information to see if they feel naturally consistent. For example, if on-site observations suggest strong obstacle shading but the analysis shows little, or vice versa, you need to revisit the input conditions. PVSyst’s outputs are convenient, but if your understanding of the site is weak, that convenience can be dangerous. That’s why both comparison and site verification are necessary.

As a countermeasure, after reviewing shading results, always perform comparisons with alternative proposals and cross-check against on-site conditions. Reading the meaning of differences via comparisons and testing for inconsistencies with site information increases confidence in the numbers. The difference PVSyst’s shading settings make is not just whether you built a model but how much you questioned and verified the results.

How to translate PVSyst shading settings into practical outcomes

What the seven checkpoints above have in common is that shading settings should not be left as mere loss inputs. Organize shading sources, match site and layout conditions to reality, view row spacing and tilt angle together, don’t judge partial shading by area ratio alone, check for seasonal and time-of-day biases, examine the link with string configuration, and finally back-check with alternative proposals and on-site information. If you follow this flow, PVSyst’s shading settings become the core of design decision-making rather than simple numerical adjustments.

For practitioners, minimizing shading loss is not the only goal. The real value lies in being able to explain how far you reduced shading, how much you accepted, and why you adopted a particular proposal. Faced with multiple constraints — raising site utilization, maintaining constructability, and ensuring maintainability — shading settings provide the material for balancing those factors. It is essential to understand not only the size of the numbers but also what assumptions those numbers rest upon.

Also, to truly improve shading-setting accuracy, do not rely solely on desk-based simulation. If site boundary, slope direction, surrounding structures, access conditions, and existing equipment are ambiguous, the assumptions behind shading settings become unstable. To connect PVSyst results to practice, you need to iterate between site understanding and simulation, continually confirming the meaning of shading.

In that sense, when you want to make on-site positioning and coordinate acquisition more reliable, it is effective to use iPhone-mounted GNSS high-precision positioning devices such as LRTK. When on-site location information and site conditions are easier to organize, the layout assumptions and obstacle conditions used in PVSyst shading settings become clearer. If you can improve desk-comparison accuracy with PVSyst and support field understanding with LRTK, shading settings evolve from mere shadow checks into site-rooted design decisions. Carefully refining shading settings not only increases the accuracy of energy-yield forecasts but also enhances the practical capability to link desk work and field work.