Category talk:Chronologies Working Group - Revision history

Khider: /* 14C recomendations -- SimonGoring (talk) 11:50, 29 September 2016 (PDT) */ Fix PAGES link

2017-08-23T19:24:51Z

‎14C recomendations -- SimonGoring (talk) 11:50, 29 September 2016 (PDT): Fix PAGES link

Jeg at 03:29, 14 March 2017

2017-03-14T03:29:02Z

SimonGoring: /* 14C recomendations -- ~~~~ */ new section

2016-09-29T18:50:31Z

‎14C recomendations -- ~~~~: new section

New page

== 14C recomendations -- [[User:SimonGoring|SimonGoring]] ([[User talk:SimonGoring|talk]]) 11:50, 29 September 2016 (PDT) ==

There are more recomendations in Grimm et al., coming out of the 2014 Belfast workshop:

http://www.pages-igbp.org/download/docs/calendar/2014/Age%20Models,%20Chronologies,%20and%20Databases%20Complete%20Report.pdf

This addresses the issues with Age Model version reporting. For example:

> The program versions, metadata, and ideally scripts should be stored to enable reproduction of chronologies

> It is recommended that producers of age modeling software provide all data necessary for reproducing chronologies in easily storable scripts or “age model definition” files.

> Instantaneous sedimentation events (slumps, thick tephras), hiatuses, and sharp changes in sedimentation rate create difficulties for classical single-solution age models, and investigators have often created ad hoc chronologies for these situations. Chronologies from these age models are particularly challenging to reproduce. It is recommended that developers of age modeling software formally incorporate these situations into their
modeling framework. Some programs already do.

← Older revision		Revision as of 03:29, 14 March 2017
Line 13:		Line 13:
	> Instantaneous sedimentation events (slumps, thick tephras), hiatuses, and sharp changes in sedimentation rate create difficulties for classical single-solution age models, and investigators have often created ad hoc chronologies for these situations. Chronologies from these age models are particularly challenging to reproduce. It is recommended that developers of age modeling software formally incorporate these situations into their		> Instantaneous sedimentation events (slumps, thick tephras), hiatuses, and sharp changes in sedimentation rate create difficulties for classical single-solution age models, and investigators have often created ad hoc chronologies for these situations. Chronologies from these age models are particularly challenging to reproduce. It is recommended that developers of age modeling software formally incorporate these situations into their
	modeling framework. Some programs already do.		modeling framework. Some programs already do.
		+
		+	===Re: 14C recomendations -- [[User:Jeg\|JEG]] ([[User talk:Jeg\|talk]]) 20:29, 13 March 2017 (PDT)===
		+
		+	: These are all excellent suggestions. Can we invite the authors/users of such softwares to give some details? E.g. what are the parameters necessary to reproduce a Bacon age model?

@@ Line 3: / Line 3: @@
 There are more recomendations in Grimm et al., coming out of the 2014 Belfast workshop:
-http://www.pages-igbp.org/download/docs/calendar/2014/Age%20Models,%20Chronologies,%20and%20Databases%20Complete%20Report.pdf
+http://www.pastglobalchanges.org/download/docs/calendar/2014/Age%20Models,%20Chronologies,%20and%20Databases%20Complete%20Report.pdf
 This addresses the issues with Age Model version reporting.  For example: