CDendro naming standard

From Cybis Wiki
(Difference between revisions)
Jump to: navigation, search
(längden)
Line 1: Line 1:
To let '''CDendro''' know which radius comes from which tree, you should carefully select the identities of your samples.
+
To let '''[[CDendro]]''' know which radius comes from which tree, you should carefully select the identities of your samples.
* Five samples from two different trees could be named NM01A, NM01B, NM02A, NM02B1, NM02B2.
+
* Five samples from two different trees could be named '''NM01A''', '''NM01B''', '''NM02A''', '''NM02B1''', '''NM02B2'''.
 
* The identity for a tree should end with a digit. An optional following letter indicates a radius.
 
* The identity for a tree should end with a digit. An optional following letter indicates a radius.
* One radius may be divided into two samples if they are named e.g. NM02B1 and NM02B2.
+
* One radius may be divided into two samples if they are named e.g. '''NM02B1''' and '''NM02B2'''.
* The identity is not case sensitive. I.e. NM01A will mean the same as Nm01a.
+
* The identity is not case sensitive. I.e. '''NM01A''' will mean the same as '''Nm01a'''.
 +
 
 +
Even if CDendro itself is able to handle very long identity names, it is strongly recommended that the restrictions of the [[Tucson format]] is followed (i.e. not more than 7 or 8 characters). Otherwise the identities will be truncated when the data is exported.  
  
 
[[Category:CDendro]]
 
[[Category:CDendro]]

Revision as of 09:30, 22 May 2009

To let CDendro know which radius comes from which tree, you should carefully select the identities of your samples.

  • Five samples from two different trees could be named NM01A, NM01B, NM02A, NM02B1, NM02B2.
  • The identity for a tree should end with a digit. An optional following letter indicates a radius.
  • One radius may be divided into two samples if they are named e.g. NM02B1 and NM02B2.
  • The identity is not case sensitive. I.e. NM01A will mean the same as Nm01a.

Even if CDendro itself is able to handle very long identity names, it is strongly recommended that the restrictions of the Tucson format is followed (i.e. not more than 7 or 8 characters). Otherwise the identities will be truncated when the data is exported.

Personal tools