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

Points to check and fix (?) in 2022_Gretzinger_AngloSaxons #163

Open
stschiff opened this issue Mar 25, 2024 · 1 comment
Open

Points to check and fix (?) in 2022_Gretzinger_AngloSaxons #163

stschiff opened this issue Mar 25, 2024 · 1 comment

Comments

@stschiff
Copy link
Member

When we added the 2022_Gretzinger_AngloSaxons package, we made a few decisions that need be checked by the first author:

  • Our supplement gives contamination estimates without error bars. Poseidon requires them, if the estimates themselves are set. I now set them all to a dummy value of 0.001, but it would of course be good if you could actually fill the correct ones if you still have them.
  • The dates in GRO004, GRO006, GRO015, GRO016, GRO020 were given only as upper bound in our Supplement. I have now set their lower bound to 900 in all of these. Please check whether that is appropriate
  • All HIDXXX samples were only given with a date fixed at 400 CE. I have now set this 300-500. Please check whether that is appropriate.

Finally, I noticed that the Supplementary Tables of the paper give the same C14 date ID for samples I0790 (LintonSk352) and I0791 (Linton351), namely SUERC-20250. They are from the same grave, so the common ID indicates that only one measurement was made, which is fine, but we need the uncalibrated date. I have, for now, switched the Date_Type to "contextual", as the validator doesn't allow the type to be C14 without uncalibrated dates given.

@nevrome
Copy link
Member

nevrome commented Mar 29, 2024

@JoschaGretzinger

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