-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Lubridate error due to leapday + suggestion of using multiple en dates #72
Comments
Hi Max! Thanks for the suggestions! Regarding leapyear this is a known bug (see #26 ). The problem is fixed in lubridate 1.4 (the test cases of sweidnumbr passes) but lubridate 1.4 has not (yet) been published on CRAN. So as soon lubridate is published on CRAN this will problem will go away. If you download the latest version of lubridate this will work for you. Regarding multiple time periods I think it is a good idea to implement it in a vectorized form. Is it possible to for the repo and add it using a merge request? The all testsuites will be run and we can see if it will make any test cases fail? /Måns |
Great job! |
Hi there @gforge! |
Leap day issue
It seems that leap days are causing issues. Although this should be fixed in the lubridate package this is not entirely the case, the following throws an error:
Multiple dates
I suggest that you add the option of having multiple end dates, this is useful when calculating the time to event data.
Suggested solution
The following change the pin_age use the lubridate:::as.period() together with an option of having end dates specified:
The text was updated successfully, but these errors were encountered: