The Export Variable to CSV" measure uses the weather file run period for the exported time series. Here is the part of the measure that does that:
# get the weather file run period (as opposed to design day run period)
ann_env_pd = nil
sqlFile.availableEnvPeriods.each do |env_pd|
env_type = sqlFile.environmentType(env_pd)
if env_type.is_initialized
if env_type.get == OpenStudio::EnvironmentType.new("WeatherRunPeriod")
ann_env_pd = env_pd
break
end
end
end
The Tel Aviv weather file though contain a lot of 1999 entries appears to be of 2006. I assume that from the fact that it start on sunday January first as opposed to Friday January first as was in 1999. Here is the part from the EPW file:
DATA PERIODS,1,1,Data,Sunday,1/ 1,12/31
1999,1,1,1,60,2520______________*_____________*_*___*_*_*,7.1,6.5,96,101880,9999,9999,298,0,0,0,
Anyway as I commented above, to my best judgment you can use that data safely as far as you make sure that the day of the week is the one you selected so the right schedules will be chosen for the simulation.
what is set in your Weather file and design days tab. Is it calendar year? Which weather file are you using?
On the weather tab the year is 2016, the epw weather file is taken from Energyplus website ( for Tel-Aviv) and is for year 1999.
I believe that it is a minor bug that does not have much impact on the results. Just make sure that the day of the week is to one you were looking for. Alternatively you could select the day of the week that start the year.