Alessia

Hi Michele, thank you again, everything is much clearer now. Just to confirm: For the 2×14 structure (a single string across two vertically stacked modules), this matches the 2TU configuration, so I’ll use 2 vertical × 1 horizontal partitions. For the 2×28 structure, with two strings (one per module row), this corresponds to the 2T configuration, so I’ll use 1 vertical × 2 horizontal partitions. That said, would subdividing further (e.g. 4 partitions in height) in the 2T case meaningfully increase accuracy, or is the standard 2‑partition approach sufficient given the partition model’s approximations? Thanks in advance.

Thank you Michele. To make sure I fully understand the implications for my specific case: Since the modules are connected in series (one string per 2x14 structure), shading on the bottom module would affect the performance of the top module as well, even though the top one remains unshaded. If I simply divide top and bottom modules each into two partitions (totaling 4 vertical submodule partitions per string), I am concerned this may miss the fact that shading on the bottom module electrically impacts the top module through the series string connection. How would you recommend managing this configuration? Thanks again.

Dear PVsyst Team, I’m reaching out to ask for your support regarding a 3D scene I’m simulating using trackers in a 2-portrait configuration. In this model, I’m defining the partition on two types of trackers: One with 2×14 modules, corresponding to a single string. Another with 2×28 modules, corresponding to two strings (one on the top row and one on the bottom row of the structure). I have two main questions: In general, is it necessary to define the partition if the module is already specified as a twin half-cell with 3 submodules in the PAN file? If so, how should the partition be configured? In my specific case, where there is only one string per structure, the partition would logically be 1×1. However, if a partition is still required due to the module’s half-cell architecture (as per question 1), how should I define it in this scenario? Thanks.

This occurs on uneven terrain. For example, in a plant with east-to-west slopes and a homogeneous pitch, shadows can differ significantly between morning and afternoon. To minimize shading, it's common to set a lower (fictitious) backtracking pitch than the real one when the tracker is facing uphill (either east or west, depending on the case). I know I could simulate this using two separate PVsyst simulations and then combine the results, but of course, it would be better if this could be configured directly in PVsyst. Thanks!

Hello PVsyst team, I would like to suggest a topic regarding the possibility to set different backtracking strategies for the morning and the afternoon. This request is based on real parameter settings provided by manufacturers for PV plants, and it would be helpful to reflect this functionality within PVsyst. Is this something you are considering implementing in a future update? Thank you, Alessia

Hello, about the value "global incident on ground" and the relative surface area (see image below): How is the "global incident on ground" value calculated? How is the relative surface area calculated? Thanks, Alessia