It seems like PVSyst is modelling the terrain following trackers wrong (underestimating losses by 3%) because of the way PVCase creates the layouts when using the terrain following tracker option in PVCase.
So now, when this terrain following tracker gets imported into PVSyst it looks like this -
If you look at the shading simulation (grey is the shadow and yellow is the part of the module table that is going out due to the shadow) in the picture above, it seems like shading is calculated by the broken bay rather than the whole string - if bay is shaded, the whole string is not affected, just that portion in the bay and hence underestimating losses. In reality it should look more like this (the picture below) where even if a tiny part of the string is shaded, the whole string should be going out. In comparison, a normal tracker (without the terrain following option enabled in PVCase) imports into PVSyst like the below picture (no broken up bays) - because of shading the whole half string is going out (yellow)
How can this compatibility (PVCase-PVSyst) issue be fixed?
