PVsystUser Posted May 28 Posted May 28 If February 29th is missing from a leap year weather dataset, does it affect only that specific day, or does it impact the rest of the year as well? For example, when importing NSRDB weather data for 2020 (a leap year) into PVsyst, but excluding February 29th from the dataset: Does the PVsyst output for March 1st still correspond to the actual March 1st? Or does PVsyst treat the March 1st data from the file as February 29th, thereby shifting all subsequent days? Additionally, when running PVsyst for a specific year, does the software calculate the sun position based on that exact year (e.g., accounting for leap years), or is the sun position fixed for each calendar day regardless of the year?
Linda Thoren Posted June 5 Posted June 5 Hello, PVsyst is calculating the sun position based on the exact year accounting for leap years, when specific years are simulated. Thus, if you import a specific year that is a leap year though the 29th is missing in the data set, it will be considered as missing data and values will be 0 (similar to as if any other date of the year was missing). So values for February 29th will be zero (e.g., no irradiance), but the date will still be included in the simulation. March 1st will correctly follow as the next day.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now