http://imagej.273.s1.nabble.com/BoneJ-Analyze-Skeleton-on-Skeletons-with-32766-components-tp5009924p5009957.html
>
>
>
> > I'm pretty sure I've used float or double for labelling (integer numeric
> values) in the past with no particular problems, but will watch out since
> Karsten's warning!
>
> Karsten is correct, integers above 2^24 (a bit more than 16 million) are
> not precisely represented by float. See e.g. this:
>
>
http://www.ibm.com/developerworks/java/library/j-math2/index.html>
> So I added a little warning to the 3D particle analyser's label image
> output, in case users are measuring this many (!!) particles in their
> image stacks (the analysis itself runs on an int[][] array so will be OK
> up to 2^31 - 1 particles, it's just the image display which uses a
> float). Perhaps a similar approach might be reasonable for Analyze
> Skeleton?
>
> Michael
>
>
> [RVC Logo - link to RVC Website]<
http://www.rvc.ac.uk> [Twitter icon -
> link to RVC (Official) Twitter] <
http://twitter.com/RoyalVetCollege>
> [Facebook icon - link to RVC (Official) Facebook] <
>
http://www.facebook.com/theRVC> [YouTube icon - link to RVC YouTube] <
>
http://www.youtube.com/user/RoyalVetsLondon?feature=mhee> [Pinterest
> icon - link to RVC Pinterest] <
http://pinterest.com/royalvetcollege/>
> [Instagram icon - link to RVC Instagram] <
>
http://instagram.com/royalvetcollege>
>
> This message, together with any attachments, is intended for the stated
> addressee(s) only and may contain privileged or confidential information.
> Any views or opinions presented are solely those of the author and do not
> necessarily represent those of the Royal Veterinary College (RVC). If you
> are not the intended recipient, please notify the sender and be advised
> that you have received this message in error and that any use,
> dissemination, forwarding, printing, or copying is strictly prohibited.
> Unless stated expressly in this email, this email does not create, form
> part of, or vary any contractual or unilateral obligation. Email
> communication cannot be guaranteed to be secure or error free as
> information could be intercepted, corrupted, amended, lost, destroyed,
> incomplete or contain viruses. Therefore, we do not accept liability for
> any such matters or their consequences. Communication with us by email will
> be taken as acceptance of the risks inherent in doing so.
>