Jump to content

Recommended Posts

Posted (edited)

When using SolarGIS prospect data and the PVsyst synethetic generation algorithm I frequently get:

"December has a great discrepancy of time shift with respect to the average."

This might make sense if I was using hourly data from SolarGIS but this is hourly data that PVsyst itself has generated!

Looking at the best clear days graph for the site clearly shows something wrong for December but I don't know how to fix this.

Anyone else noticed similar problems/behaviour?

H.

Edit 1:

Added pictures.

1078856014_BestClearDay-Dec-SGIS-MN7.png.2a6ec2999a0c5322e70708ff72c8e3b0.png

7954637_TimeshiftGraph-SGIS-MN7.png.18f79b4ff9f6b4a59b7cabd494f5561f.png

Edited by Helios210
Posted

Investigating further it seems generating from MN7 data imported within PVsyst does not present this problem, the graph for best clear days' for December is much better but there is still a significant timeshift and no warning is given this time (??) - see the attached pictures.

I have noticed that PVsyst seems to add MN7 data to imported datasets that don't include Linke Turbidity etc. however it leaves GHI and DIFF alone, so I would not expect this to have such a dramatic effect in a single month, though perhaps I am missing something...

1512338563_BestClearDay-Dec-PureMN7.png.83fe8753e12ac8f0699a4f62c035e6b3.png

419170740_TimeshiftGraph-PureMN7.png.aac8b0ded20d1c2b6c455b5d9973e902.png

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...