Recalculation of shading factors table required in batch mode?

[laurahin]

Hi,

This might be considered a feature rather than a bug, but it's still a problem.

I am rerunning a project in PVsyst 7.4.6 that had previously been run in 7.4.5.  Despite the electrical loss/shading error in 7.4.5, this run remains our required reference.   I would therefore like to keep the 7.4.5 shading scene that creates the electrical loss error.  According to the version log, a change for 7.3.2 was 

    Shadings: PVsyst now suggests recomputing shading factor tables if they have been computed with an older version

and for 7.4.2 was 

    Shadings: shading factor tables now remain valid if no changes have been made to the shading scene

This does seem to be the case when I rerun the variant, but when I implement a batch run, the shading scene is immediately recalculated.  Is there any way to stop this from happening?  If not, this is a feature I'd like to see.

Thanks,

Laura H.

 

Edited May 23 by laurahin
English error

[laurahin]

Actually, the "diffuse integrals" are also being recomputed every time, regardless of whether I'm running a batch or not, apparently just because something changed somewhere in the configuration.  I don't want that to happen either, because we are using all trackers in the diffuse shading calculation.  Is there any reason we can't just be happy with the existing shading if the shading scene hasn't changed?