-
Notifications
You must be signed in to change notification settings - Fork 0
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
Year zero problem #4
Comments
This is still a problem, e.g.: a <- yr(10, "BC")
b <- yr(10, "CE")
b - yr_transform(a, "CE")
#> # CE years <yr[1]>:
#> [1] 20
#> # Era: Common Era (CE): Gregorian years (365.2425 days), counted forwards from 0 Redefining era epochs using an epoch that has a year 0 (e.g. b2k) might help? |
Redefining epochs in a system without a year 0 is a good solution, but b2k introduces the complication of it now being counted backwards instead of forwards. So instead we'll stick with Gregorian years, but using astronomical numbering, i.e. there is a year zero. This means the epoch of CE is now 0 (i.e. the start of 1 CE was one year after the start of 0 CE) and the epoch of BCE is now 1 (i.e. the start of 1 BCE was one year before the start of 1 CE). Definitions of epochs derived from a (fractional) CE year, e.g. Hijri years, also had to be adjusted. This seems to make things consistent across the board. I've also added a test to try and catch these annoying off-by-one issues in era definition in future. |
When converting between CE-based and BP-based eras, yr_transform() does not account for the absence of a year zero.
OxCal is good at this kind of thing.
The text was updated successfully, but these errors were encountered: