Tucson format - Revision history

Lars-Ake: /* Unexpected examples */

2017-01-11T10:25:23Z

Unexpected examples

← Older revision		Revision as of 12:25, 11 January 2017
Line 154:		Line 154:
	<br>Note: The germ21.rwl file contains another severe error (a missing line of data) that makes it unreadable to CDendro.''		<br>Note: The germ21.rwl file contains another severe error (a missing line of data) that makes it unreadable to CDendro.''


			<pre>
			cc321201 0 0 3934 2736 2620 4184 4334 4438 4790 4968 5330 wb
			cc321201 10 5008 1796 4786 3940 2762 1870 1804 1912 1588 1874 wb
			cc321201 20 2634 1840 1994 2120 3334 1252 1206 1362 4186 1938 wb
			cc321201 30 2090 530 1594 2492 1686 2064 518 2854 1426 1652 wb
			cc321201 40 774 1080 1130 1248 -9999 wb
			cc321202 0 0 5022 4404 5402 4176 5676 2666 6004 5212 4262 wb
			cc321202 10 2206 2928 1894 2458 4806 2846 2880 2354 2318 2550 wb
			cc321202 20 2028 2178 2054 2230 2492 1756 1892 2730 1948 1922 wb
			cc321202 30 1334 2016 1386 2154 1708 4396 1336 1742 502 2868 wb
			cc321202 40 -9999 wb </pre>
			''From measurements performed on a Velmex machine and saved as time series in a decadal format
			<br>(The " wb" word at end of each line made CDendro versions before 8.1.2 reject the data.)

Lars-Ake: /* Basics of the Tucson format for ring width data */

2016-11-03T13:29:39Z

Basics of the Tucson format for ring width data

← Older revision		Revision as of 15:29, 3 November 2016
Line 24:		Line 24:
	While a "0" value seems to be handled as an "absent" value which is just omitted from correlations. CDendro from version 8.2 will have a setting to make		While a "0" value seems to be handled as an "absent" value which is just omitted from correlations. CDendro from version 8.2 will have a setting to make
	missing values marked as "0" also in .rwl files having 0.01 mm measurement units.		missing values marked as "0" also in .rwl files having 0.01 mm measurement units.
	You can attain the same effect of unbroken series by changing the Decadal measurement unit to 0.001 mm and again write out your series to a .rwl file		You can attain the same effect of unbroken series by changing the Decadal measurement unit to 0.001 mm in CDendro and again write out your series to a .rwl file
	before submitting it to Cofecha.		before submitting it to Cofecha.

Lars-Ake: /* Basics of the Tucson format for ring width data */

2016-11-03T13:21:51Z

Basics of the Tucson format for ring width data

← Older revision		Revision as of 15:21, 3 November 2016
Line 16:		Line 16:
	The missing data mark is actually not defined, though usually the mark "-999" is used within 0.01 mm files, and "0" in 0.001 mm files. See also Note 4 below!		The missing data mark is actually not defined, though usually the mark "-999" is used within 0.01 mm files, and "0" in 0.001 mm files. See also Note 4 below!

	<br/>Note 1: The consequence of using the value 999 as a stop marker is that a measurement of 9.99 mm, in 0.01 mm units, has to be changed		<br/><b>Note 1:</b> The consequence of using the value 999 as a stop marker is that a measurement of 9.99 mm, in 0.01 mm units, has to be changed
	into 9.98 mm (written value=998) or 10.00 mm (1000)! To avoid fooling any other software, it is probably best never to write the value "999" as measurement data also for files with 0.001 mm units!		into 9.98 mm (written value=998) or 10.00 mm (1000)! To avoid fooling any other software, it is probably best never to write the value "999" as measurement data also for files with 0.001 mm units!
	<br/>Note 2: If 5 digits are needed for the year number, i.e. a core older than -999, the identity cannot be more than 7 alphanumeric characters.		<br/><b>Note 2:</b> If 5 digits are needed for the year number, i.e. a core older than -999, the identity cannot be more than 7 alphanumeric characters.
	<br/>Note 3: An ITRDB specification of the Tucson format is available <ref>ITRDB's specification of the tucson format: http://www.ncdc.noaa.gov/paleo/treeinfo.html</ref>, though that specification cannot be		<br/><b>Note 3:</b> An ITRDB specification of the Tucson format is available <ref>ITRDB's specification of the tucson format: http://www.ncdc.noaa.gov/paleo/treeinfo.html</ref>, though that specification cannot be
	fully trusted. E.g. it currently (2009-07-09) specifies the missing data mark to be 999, which value in reality is used as the stop marker.		fully trusted. E.g. it currently (2009-07-09) specifies the missing data mark to be 999, which value in reality is used as the stop marker.
	<br/>Note 4: It seems that Cofecha is handling these two marks differently: When Cofecha runs over a -999 value, then the series is broken into two series by this mark.		<br/><b>Note 4:</b> It seems that Cofecha is handling these two marks differently: When Cofecha runs over a -999 value, then the series is broken into two series by this mark.
	While a "0" value seems to be handled as an "absent" value which is just omitted from correlations. CDendro from version 8.2 will have a setting to make		While a "0" value seems to be handled as an "absent" value which is just omitted from correlations. CDendro from version 8.2 will have a setting to make
	missing values marked as "0" also in .rwl files having 0.01 mm measurement units.		missing values marked as "0" also in .rwl files having 0.01 mm measurement units.

Lars-Ake: /* Basics of the Tucson format for ring width data */

2016-11-03T12:08:07Z

Basics of the Tucson format for ring width data

← Older revision		Revision as of 14:08, 3 November 2016
Line 14:		Line 14:
	I.e. the stop marker is used to show not only the end of the series but also the units of measurement used (0.01 mm or 0.001 mm)!		I.e. the stop marker is used to show not only the end of the series but also the units of measurement used (0.01 mm or 0.001 mm)!

	The missing data mark is actually not defined, though usually the mark "-999" is used within 0.01 mm files, and "0" in 0.001 mm files.		The missing data mark is actually not defined, though usually the mark "-999" is used within 0.01 mm files, and "0" in 0.001 mm files. See also Note 4 below!

	<br/>Note 1: The consequence of using the value 999 as a stop marker is that a measurement of 9.99 mm, in 0.01 mm units, has to be changed		<br/>Note 1: The consequence of using the value 999 as a stop marker is that a measurement of 9.99 mm, in 0.01 mm units, has to be changed
Line 21:		Line 21:
	<br/>Note 3: An ITRDB specification of the Tucson format is available <ref>ITRDB's specification of the tucson format: http://www.ncdc.noaa.gov/paleo/treeinfo.html</ref>, though that specification cannot be		<br/>Note 3: An ITRDB specification of the Tucson format is available <ref>ITRDB's specification of the tucson format: http://www.ncdc.noaa.gov/paleo/treeinfo.html</ref>, though that specification cannot be
	fully trusted. E.g. it currently (2009-07-09) specifies the missing data mark to be 999, which value in reality is used as the stop marker.		fully trusted. E.g. it currently (2009-07-09) specifies the missing data mark to be 999, which value in reality is used as the stop marker.
			<br/>Note 4: It seems that Cofecha is handling these two marks differently: When Cofecha runs over a -999 value, then the series is broken into two series by this mark.
			While a "0" value seems to be handled as an "absent" value which is just omitted from correlations. CDendro from version 8.2 will have a setting to make
			missing values marked as "0" also in .rwl files having 0.01 mm measurement units.
			You can attain the same effect of unbroken series by changing the Decadal measurement unit to 0.001 mm and again write out your series to a .rwl file
			before submitting it to Cofecha.

	<PRE>		<PRE>
	PMkr12b 1781 120 87 69 122 108 85 125 114 77		PMkr12b 1781 120 87 69 122 108 85 125 114 77

Lars-Ake at 16:38, 8 April 2015

2015-04-08T16:38:57Z

← Older revision		Revision as of 18:38, 8 April 2015
Line 132:		Line 132:
	...		...
	</pre>		</pre>
	''Example from the [http://~~sokl~~.~~joensuu~~.fi/~~saima~~/homepage3/lemola/ab/kinsys/lemoltu_.txt Finnish Tree ring data bank of Saima]		''Example from the [http://lustiag.pp.fi/Saima/homepage3/lemola/ab/kinsys/lemoltu_.txt Finnish Tree ring data bank of Saima]
	''With this layout each "unused position" is marked with a dot (.).		''With this layout each "unused position" is marked with a dot (.).

Lars-Ake at 20:01, 21 October 2013

2013-10-21T20:01:31Z

← Older revision		Revision as of 22:01, 21 October 2013
Line 77:		Line 77:
	MWK401 -3550 26 21 19 20 28 21 13 11 -0 11 </pre>		MWK401 -3550 26 21 19 20 28 21 13 11 -0 11 </pre>
	''Example from ca535.rwl<ref>{{itrdb\|ca535\|northamerica/usa}}</ref> where zeroes are filled into positions which are not in use and this with a -0 instead of 0 or -999 for missing rings. Each row also ends with a number of extra white spaces''		''Example from ca535.rwl<ref>{{itrdb\|ca535\|northamerica/usa}}</ref> where zeroes are filled into positions which are not in use and this with a -0 instead of 0 or -999 for missing rings. Each row also ends with a number of extra white spaces''

			<pre>
			BG8 1920 324 693 690 700 1130 847 980 1143 680 566
			BG8 1930 548 671 907 1197 902 1169 969 862 1051 1125
			BG8 1940 549 361 496 767 782 168 38 -7 -7 -7
			BG8 1950 102 119 31 94 110 79 118 240 245 251</pre>
			''Example where "-7" has been used to indicate a missing ring.
			<br/>A comment from a CDendro user: <i>"To give an example of when negative values are used with a particular meaning, it is possible to fill in missing data in ARSTAN. The relevant setting fills in missing data if the data points are denoted with a negative number (excluding -9999). Data points with zero values do not get filled in."</i>

Taxelson: /* Unexpected examples */ one more detail on ca535

2012-02-07T08:48:44Z

Unexpected examples: one more detail on ca535

← Older revision		Revision as of 10:48, 7 February 2012
Line 76:		Line 76:
	...		...
	MWK401 -3550 26 21 19 20 28 21 13 11 -0 11 </pre>		MWK401 -3550 26 21 19 20 28 21 13 11 -0 11 </pre>
	''Example from ca535.rwl<ref>{{itrdb\|ca535\|northamerica/usa}}</ref> where zeroes are filled into positions which are not in use and this with a -0 instead of 0 or -999 for missing rings.''		''Example from ca535.rwl<ref>{{itrdb\|ca535\|northamerica/usa}}</ref> where zeroes are filled into positions which are not in use and this with a -0 instead of 0 or -999 for missing rings. Each row also ends with a number of extra white spaces''

Lars-Ake: /* Unexpected examples */

2011-02-05T21:41:50Z

Unexpected examples

← Older revision		Revision as of 23:41, 5 February 2011
Line 126:		Line 126:
	''Example from the [http://sokl.joensuu.fi/saima/homepage3/lemola/ab/kinsys/lemoltu_.txt Finnish Tree ring data bank of Saima]		''Example from the [http://sokl.joensuu.fi/saima/homepage3/lemola/ab/kinsys/lemoltu_.txt Finnish Tree ring data bank of Saima]
	''With this layout each "unused position" is marked with a dot (.).		''With this layout each "unused position" is marked with a dot (.).


			<pre>
			109540 1690 48 45 45 39 39 33 33 36 33 33
			109540 1700 36 30 33 27 36 39 36 39 36 39
			109540 1710 39 33 33 30 33 30 22.5 22.5 25.5 25.5
			109540 1720 25.5 31.5 34.5 30 37.5 45 39 37.5 40.5 36
			109540 1730 30 31.5 31.5 34.5 30 30 34.5 34.5 33 36
			109540 1740 31.5 30 25.5 27 30 30 24 30 999
			109550 1521 138 129 114 99 99 189 120 114 111
			109550 1530 111 105 99 102 105 96 90 102 81 93</pre>
			''A snappet from germ21.rwl.<ref>{{itrdb\|germ21\|europe}}</ref> This is the only case we have found with decimal values (like "22.5").
			<br>Note: The germ21.rwl file contains another severe error (a missing line of data) that makes it unreadable to CDendro.''

Taxelson: /* Basics of the Tucson format for ring width data */

2011-02-05T15:38:47Z

Basics of the Tucson format for ring width data

← Older revision		Revision as of 17:38, 5 February 2011
Line 4:		Line 4:

	A Tucson file usually consists of three lines of meta data followed by an undefined number of data lines.		A Tucson file usually consists of three lines of meta data followed by an undefined number of data lines.
	Ring width data is written as integers either in units of 0.01 mm or in units of 0.001 mm		Ring width data is written as integers either in units of 0.01 mm or in units of 0.001 mm.
	A data line consist of the ''core identity'' (max 8 alphanumeric characters, i.e. letters or digits), the ''year'' of the oldest measurement		A data line consist of the ''core identity'' (max 8 alphanumeric characters, i.e. letters or digits), the ''year'' of the oldest measurement
	of the line (4 digits) followed by ring width data, up to ten rings per line.		of the line (4 digits) followed by ring width data, up to ten rings per line.
Line 44:		Line 44:
	NM002 1640 116 72 91 49 85 146 125 126 136 131</pre>		NM002 1640 116 72 91 49 85 146 125 126 136 131</pre>
	''The usual ending and start of samples (0.01 mm units resolution)''		''The usual ending and start of samples (0.01 mm units resolution)''


	==Unexpected examples==		==Unexpected examples==

Taxelson: /* See also */ snyggar till länk

2010-02-04T22:46:33Z

← Older revision		Revision as of 00:46, 5 February 2010
Line 314:		Line 314:

	==See also==		==See also==
	See also [~~http~~:~~//www.cybis.se/wiki/index.php?title=~~Category:~~Dendro_data_format~~ Dendro data format]		See also [[:Category:Dendro data format\|Dendro data format]]

	==Notes==		==Notes==