Search the Community
Showing results for tags 'partitions'.
Found 2 results
-
How should the partitions be set up in the near shade for the following scenario? We are using half cut cells with optimizers connecting every two modules. We are importing our shade scene so the tables each represent a singular module in landscape. Based on the guidance for partitions systems with "little" tables partitions should be 1x1, but for the section "Defining rectangles as one module/ module optimizers" indicates that rectangular strings should represent 1 to 2 modules(2 in our case). Additionally the section before "String Optimizers" mentions that for landscape the best model is two partitions per row. So i believe there are two options Partitions of a 1x1 per table which defines a whole module (this is problematic because the optimizers connect every 2 modules). Partitions of a 1x3 per table which cuts a module into three landscape based rectangles (this is problematic because the optimizers connect every 2 modules).
-
Hi, I was wondering if Pvsyst during the shading loss simulation takes into account the half cut technology modules or when a module in landscape is shaded on the lower half PVsyst considers the entire module bypassed ? Second thing, when doing partitions do I need to create a partition that divides the module in half (landscape configuration) to take the half cut modules into account or not and PVsyst considers that already by default ? Thank you
