You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
When we added the
2022_Gretzinger_AngloSaxons
package, we made a few decisions that need be checked by the first author: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 theDate_Type
to "contextual", as the validator doesn't allow the type to beC14
without uncalibrated dates given.The text was updated successfully, but these errors were encountered: