October 9, 20197 yr comment_3034 Dear Tim, yes, that is true. This is because we only simulate one year, and the calendar component that you showed in your screenshot needs a year to be set. 2014 is just an arbitrary value, a placeholder for any year, if you want. Sorry for the confusion, kind regards, Martin Report
October 9, 20197 yr Author comment_3035 Dear Martin, ? i didn't understand where is the confusion? "This is because we only simulate one year" -why? , which year? thanks Report
October 9, 20197 yr comment_3036 Hi Tim, the year that we simulate isn't a specific one. It is a general year, just the 8760 hours of one typical year at a given location. The climate data is taken from real years with a range of 10 to 20 or even 30 years and is compiled into a single typical meteorological year (TMY), that contains e.g. the January of 2006, the February of 2013, March 2014, and so on. See more on that topic here: https://help.valentin-software.com/pvsol/2019/calculation/irradiation/climate-data/#what-are-climate-data-sets-what-does-typical-mean-year-mean So, this single TMY is "yearless", so to speak. It stands for a typical year in the time range that is denoted in the climate data. Hope that clarifies the matter, kind regards, Martin Report
October 9, 20197 yr Author comment_3037 ohhh got it ! thank you:) So the 2014 is making a confusion ? Report
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.