Average orientation

It is now possible to explicitly define averaged orientations. This allows for example to define:

• Projects with several tables in different azimuths (like rotunda),
• BIPV projects with different planes of orientation, close to each others,
• Distributed tables orientations on a hill. This was already the case in V7 when importing a 3D scene, but the procedure is strongly simplified.

Basic concept

Orientations definitions

In the 3D scene, each table has its own orientation, defined by its parameters Tilt, Azimuth, and BaseSlope. When the base slope is defined, the true orientation (true tilt, true azimuth) will be calculated.

In the Orientation parameters, you can define a "nominal" orientation (tilt and azimuth) or let PVsyst calculates an average of the true orientations (average true tilt and average true azimuth) of all the concerned tables, weighted by their area. Analysing tools will evaluate the average angle difference between normals of each table with respect to the normal of the nominal orientation. The nominal values should be chosen for minimizing this discrepancy.

Use in simulation

During the simulation:

• Mutual shadings are calculated from the real positions of each table.
• Irradiance calculation (transposition) is done for a single orientation, which is the calculated average of tilts and azimuths. This approximation obviously induces an error on the GlobInc real value. A specific tool for the evaluation of this error is not yet available; it is on our roadmap for a next version.