Two values of GCR appear in the Report

[mgrms]

Hello,

In the report of my simulations using bifacial modules, the GCR value that appears in "Backtracking strategy" is different from the one that appears in "Bifacial system". I did the maths, and it appears that it is because they do not take into account the same parameters to calculate the collector width :

- in "Backtracking strategy" : L = length module + module spacing (defined in near shadings)

- in "Bifacial system" : L = length module + module spacing (defined in near shadings) + frame (also defined in near shadings)

In both situation the pitch is equal.

Which GCR should I take into account in the end ?

I would also be glad to hear any other explanation for the difference of GCR.

Thank you for your help !

[MNWild]

Bothersome phenomonon indeed.  Wish I didn't have to work around this and trick clients or claim pvsyst doesn't let us type in the correct values.  Either your GCR will read wrong (not equal to module datasheet length/pitch), or your backtracking limit angle will be wrong, or your sensitive area, or your actual 3d scene module width or length idk which.  It's very inconsistent.

Inactive Band Left Right, Inactive Band Top Bottom, bandwidth

X spacing, Y spacing

Frame L/R T/B

Backtracking Limit angle,

GCR, and

bifacial section's version of above conflicts on report

batch version of above

We have to parameterize all this information and test every revision to understand what pvsyst thinks it's doing, vs what it says it's doing, vs what help file says its supposed to do, vs what is on report, vs what forums answers say, vs orientation tab, vs 3d scene, vs bifacial page. All definitions overlap and change depending on if you are in shading scene or elsewhere in program.