Hi Paul,
I'm creating real year weather files to use for modelling PV systems at a number of sites in Australia. I'm using hourly satellite irradiance data from the Bureau of Meteorology, along with hourly temp and windspeed from BOM Automatic Weather Stations.
I'm using the SAM SDK to calculate DHI for the weather file, but am having some difficulty trying to use timezones to correct for the fact that the irradiance data is recorded at a number of minutes past the hour.
The Satellite data gives GHI and DNI, tagged with the hour (hh:00) but the actual time the reading was taken varies with latitude. As an example, I have a site where the readings are taken 49 minutes after the hour.
I am using the SAM SDK to calculate DHI by supplying the GHI and DNI data to the
module, called from within python, with
set to 1 and using the Perez sky model. As I have
and
set to zero, the
returned should give me DHI.
The timezone here is UTC + 10.
My understanding is that if in the absence of minute data (or if the minute column is set to zero) SAM would assume the GHI and DNI readings I am sending are taken at 30 minutes past the hour. In order to correct this,I am adjusting the timezone
, but am not sure what value to use. I have tried
(49 minutes is 0.82 of an hour) and
(19 minutes or 0.32 past the half-hour).
Both are giving strange results, in particular a bad fit between DHI and GHI on very cloudy days and a dip and spike in DHI towards the end of the day. In fact, for these days, I get more 'normal' looking results using
or thereabouts, but I don't understand why. I suspect I'm missing something obvious.
I've attached a few files with different values for tz.
Is this approach of shifting the timezone the correct one? And if so, what value should I be using?
Thanks for your help.