Would someone be willing to run DiamCalc for me?

[MarkP1]

Hi,
Can someone please run this diamond through DiamCalc for me?
Thank-you very much.

1.06, Round
6.64 - 6.66 x 4.03mm
Depth: 60.6%
Table: 55%
Crown Angle: 34.5
Crown Height: 15.5%
Pavilion Angle: 40.8
Pavilion Depth: 43%
Star Length: 50%
Lower Half: 80%
Girdle: Thin to Medium, Faceted
Culet: None
Polish & Symmetry: Excellent
Fluorescence: None

Thank-you very much.
Mark

 

[Garry H (Cut Nut)]

it will look like any other perfect diamcal image. and will not help you.
The stone will be very nice - even if the GIA rounded data is out a little.

 

[MarkP1]

Garry,
I actually purchased this diamond for an engagement ring after a month of advice and great learning on this site.

My biggest thanks goes to yourself & John for help and advice and Dave & Jen at Mr. Atlas''s company who sent me, overnight from the US to Canada, an Ideal-Scope so that I could take it in with me before my purchase.

I am asking for the DiamCalc data and image more for myself and my fiance to hang on to.
Thanks.

 

[JohnQuixote]

Date: 9/7/2006 2:13:05 AM
Author: MarkP1
Garry,
I actually purchased this diamond for an engagement ring after a month of advice and great learning on this site.

My biggest thanks goes to yourself & John for help and advice and Dave & Jen at Mr. Atlas's company who sent me, overnight from the US to Canada, an Ideal-Scope so that I could take it in with me before my purchase.

I am asking for the DiamCalc data and image more for myself and my fiance to hang on to.
Thanks.

Mark, congratulations! I'm glad you found the site helpful - it was a pleasure discussing things with you.

It's a simple thing to punch the dozen numbers from above into DiamCalc. Anyone can do this and you can certainly enjoy seeing and sharing the generalized data with your fiance (congrats again!).

What Garry is saying is that our DC images won't match your diamond precisely: We have only basic skeletal information for manual input. Only a dozen data points are available and those are both averaged and rounded. DiamCalc will use them like a very simple dot-to-dot (which is missing thousands of dots) and assume a perfect wireframe connecting them - which no diamond has.

For an individual diamond a Sarin/Helium or Ogi 3D scan is used. These optical scanners acquire thousands of data points for a specific diamond and calculate lines between them for a more realistic representation - which includes all variation ranges, symmetry details, extra facets, naturals etc (and even this is not infallible).

 

[JohnQuixote]

So - with that said, here is what the basic data set from your GIA report produces in DiamCalc.

Note: Rounding, ranges of variance, symmetry details and other factors are not accounted-for.

 

[JohnQuixote]

Here is what your basic data set produces in terms of simulated Ideal-Scope and ASET views.

Again - not wholly accurate to your specific diamond, as it assumes perfect optical symmetry, no variances, etc.

 

[JohnQuixote]

As a 'for example,' I took your basic data set and without changing main proportions I gave it some notable symmetry deviations. You can see the change in the patterns.

Diamonds cut to the heart of EX/Ideal often have a nice level of optical symmetry as a by-product of the craftsmanship it took to get there, but there is no way to know without assessing the actual stone.

I hope this is educational in showing why we can go ahead and plug basic numbers into DiamCalc - but we can't expect it to be the real McCoy.

Congrats again, Mark.

 

[MarkP1]

John,
Thank-you very much.
I appreciate it and I totally understand what you are saying.

Cheers,
Mark