Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Leap year issues with CMIP5 data #28

Open
jimwlewis opened this issue Aug 3, 2017 · 1 comment
Open

Leap year issues with CMIP5 data #28

jimwlewis opened this issue Aug 3, 2017 · 1 comment

Comments

@jimwlewis
Copy link

When ending a time period on a leap year, an index error occurs. For example, doing RAPIDpy for 1971-1972 crashes, because 1972 is a leap year. But if you do RAPIDpy for 1971-1973, it works fine.

Also, on some installations (problem on my Linux desktop, but not on the HPC install), generating the m3 file for a multi-year time period has an error related to leap years. A problem in the m3 file data occurs every four years, and the number of days is only 365 times the number of years, instead of some years having 366 days.

@snowman2
Copy link
Member

snowman2 commented Aug 4, 2017

I think it is because it bases the number of time steps by the initial file in the group. So, if you start with a file with 365 days, then it assumes all of them are 365 days. This works when the files are divided into days. However, leap years make this assumption invalid for files grouped by year as some will have 366 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants