-------- Original Message --------
Subject:        Re: [morphoj/tps format]
Date:   Tue, 4 Oct 2011 10:58:36 -0400
From:   Bachar Cheaib <[email protected]>
To:     [email protected]



Hi,

Thanks a lot for your help
That's work fine for this moment

Best reagrds


B. Cheaib



On Mon, Oct 3, 2011 at 9:22 PM, morphmet <[email protected] <mailto:[email protected]>> wrote:



   -------- Original Message --------
   Subject:     Re: [morphoj/tps format]
   Date:        Mon, 3 Oct 2011 14:50:42 -0400
   From:        Chris Klingenberg <[email protected]>
   <mailto:[email protected]>
   Reply-To:    [email protected] <mailto:[email protected]>
   Organization:        University of Manchester
   To:  [email protected] <mailto:[email protected]>



   Dear Bachar

   For 3D data in the TPS format, use "LM3=" instead of "LM=".

   Here is the corrresponding spec from the help file from tpsSmall (as far
   as I know, this is the official documentation for 3D data in the TPS
   series):
   "For 3D data use the LM3= keyword rather than the LM= keyword and list
   the x, y, z coordinates of each specimen with one line for each landmark."
   (The next release of MorphoJ will give a more detailed output in the
   error message.)

   If I fix that problem, I get a second error about the number of landmarks.

   Also, I get errors if I try to open the file with tpsSmall -- perhaps
   you want to try with an example with fewer than 100 landmarks first.

   Best wishes,
   Chris



   Copyright © 1999 by F. James Rohlf
   On 10/3/2011 6:15 PM, morphmet wrote:
   >
   >
   >  -------- Original Message --------
   >  Subject:       Re: subscribe
   >  Date:  Mon, 3 Oct 2011 12:06:52 -0400
   >  From:  Bachar Cheaib<[email protected]>  
<mailto:[email protected]>
   >  To:    [email protected]  
<mailto:[email protected]>
   >
   >
   >
   >  Hi,
   >
   >  I am using Morphoj, I tried .txt or .tps , the software figure out these
   >  following messages
   >
   >  Reading from TPS file 'test_morphoj.tps'.
   >
   >  Problems with reading the file.
   >
   >  Inconsistent dimensionality in record 1: 2D data although user-defined
   >  dimensionality is 3D.
   >  The number of dimensions in some entry/entries in record 1 appears to be
   >  inconsistent with the number of dimensions.
   >  Inconsistent dimensionality in record 2: 2D data although user-defined
   >  dimensionality is 3D.
   >  The number of dimensions in some entry/entries in record 2 appears to be
   >  inconsistent with the number of dimensions.
   >  Inconsistent dimensionality in record 3: 2D data although user-defined
   >  dimensionality is 3D.
   >  The number of dimensions in some entry/entries in record 3 appears to be
   >  inconsistent with the number of dimensions.
   >  Inconsistent dimensionality in record 4: 2D data although user-defined
   >  dimensionality is 3D.
   >  The number of dimensions in some entry/entries in record 4 appears to be
   >  inconsistent with the number of dimensions.
   >  Inconsistent dimensionality in record 5: 2D data although user-defined
   >  dimensionality is 3D.
   >  The number of dimensions in some entry/entries in record 5 appears to be
   >  inconsistent with the number of dimensions.
   >  Errors occurred in the reading process.
   >  The new dataset could not be created.
   >
   >  I have chosen 3D, and format TPS
   >
   >  Please, could you be able to help me in finding my input error ?
   >  I attached this file input below
   >
   >  Thanks in advance
   >
   >  All the best regards
   >
   >  B. Cheaib
   >

-- ***************************************************************
   Christian Peter Klingenberg
   Faculty of Life Sciences
   The University of Manchester
   Michael Smith Building
   Oxford Road
   Manchester M13 9PT
   United Kingdom

   Telephone:+44 161 275 3899  <tel:%2B44%20161%20275%203899>
   Fax:+44 161 275 5082  <tel:%2B44%20161%20275%205082>
   E-mail:[email protected]  <mailto:[email protected]>
   Web:http://www.flywings.org.uk
   Skype: chris_klingenberg
   ***************************************************************





Reply via email to