shape
carat
color
clarity

AGS 2 or AGS 0 - The ''Candidate'' vs Parametric grades

Status
Not open for further replies. Please create a new topic or request for this thread to be opened.
Picture from STL DC file

STLP41CR35.jpg
 
Picture from DMC STL file

re:"SERGEY.. DON''T GO OFF HALF COCKED. LOOK AT WHAT I SENT YOU. AS I SAID PRIVATELY TO YOU, the problem you choose to address publically arises because DIAMONDCALC can, and did, generates STLS that are BOGUS, just as Sarin had problems with, and were readily apparent in OGI STL previously in another thread.
I SENT YOU DIAMONDCALC generated binary STLS, that had some MINOR issues, like three colinear (or coincident) points, and GARBAGE IN, GARBAGE OUT. It is impossible for ANY software to trap all the potential CRAP that it is given for input, and you are NOT WITHOUT BLAME HERE. You chose NOT TO LOOK AT THEM Before trying to create a PUBLIC FLAP.
"

Marty , Do you see any difference?
1) I created Dmc file. Save
2) COnvert to binary STL file. Save
3) Send both type file to you and AGS
4) Open both file in DC, creat picture , publish on PS

You can check each my step

What is BOGUS? Do you know whats STL support only only triangular facets?!

It was very bad idea use STL for AGS-PGS, and even more bad idea to try find reason bad work PGS outside AGS.
Try to undestand reason PGS problem firstly

DMCP41Cr35.jpg
 
Date: 2/23/2007 4:25:32 PM
Author: Serg
Picture from STL DC file
Sergey.. The picture doesn''t tell the story regarding anomolous PGS results you quoted... PERIOD..
 
Date: 2/23/2007 4:37:24 PM
Author: adamasgem

Date: 2/23/2007 4:25:32 PM
Author: Serg
Picture from STL DC file
Sergey.. The picture doesn''t tell the story regarding anomolous PGS results you quoted... PERIOD..

Marty,
these pictures is fine answer to your below attack.( did you see both pictures? see first on previouce page)

Marty:I SENT YOU DIAMONDCALC generated binary STLS, that had some MINOR issues, like three colinear (or coincident) points, and GARBAGE IN, GARBAGE OUT. It is impossible for ANY software to trap all the potential CRAP that it is given for input, and you are NOT WITHOUT BLAME HERE. You chose NOT TO LOOK AT THEM Before trying to create a PUBLIC FLAP
 
Marty , Do you see any difference in these pictures( one from dmc , other from stl)?
 
Date: 2/23/2007 4:33:20 PM
Author: Serg

Picture from DMC STL file

re:''SERGEY.. DON''T GO OFF HALF COCKED. LOOK AT WHAT I SENT YOU. AS I SAID PRIVATELY TO YOU, the problem you choose to address publically arises because DIAMONDCALC can, and did, generates STLS that are BOGUS, just as Sarin had problems with, and were readily apparent in OGI STL previously in another thread.

I SENT YOU DIAMONDCALC generated binary STLS, that had some MINOR issues, like three colinear (or coincident) points, and GARBAGE IN, GARBAGE OUT. It is impossible for ANY software to trap all the potential CRAP that it is given for input, and you are NOT WITHOUT BLAME HERE. You chose NOT TO LOOK AT THEM Before trying to create a PUBLIC FLAP.
''

Marty , Do you see any difference?
1) I created Dmc file. Save
2) COnvert to binary STL file. Save
3) Send both type file to you and AGS
4) Open both file in DC, creat picture , publish on PS

You can check each my step

What is BOGUS? Do you know whats STL support only only triangular facets?!

It was very bad idea use STL for AGS-PGS, and even more bad idea to try find reason bad work PGS outside AGS.
Try to undestand reason PGS problem firstly
Perhaps you should have whomever sent you the erroneous PGS resuts (probably arising because of misinterpreted extraneous STL''s or combined facets) to send you the detailed breakdown of where the deductions came from..

1) I generated with build 375 of DC, ascii STLS which I sent to Rockdoc to run through the PGS software

2) PGS couldn''t read ascii STL''s so Rockdoc imported the ascii STL''s to DC and exported binary STL''s from DC, and got bogus results regarding "culet" and "girdle" deductions, but all four files gave AGS 0''s for the ray tracing portion of the software.

3) When I examined both ascii STL''s and binary STL''s from DC, they were mathematically different

4) When I read these binary files with my software, I saw colinear (or coincident point) STL''s, i.e. STL''s that either had zero area or STL''s which were mathematically on a straight line (i treat them the same in my trap)

5) I, and AGS have seen similar types of problems in the past with Sarin files, where you have mathematically small facets whose normals point in unexpected directions, and the GIGO syndrome take over.

6) You saw the really bad OGI stl''s

7) I guess you didn''t ask whomever gave you the total PGS grade to give you the pieces of the puzzle. They are readily available in the PGS output.

8) LITTERALLY NO SOFTWARE can take into account the myriad of erroneous, or unanticipated conditions, that can be thrown at it.

What is the agenda?
 
Date: 2/23/2007 4:51:45 PM
Author: Serg
Marty , Do you see any difference in these pictures( one from dmc , other from stl)?
Sergey, there doesn''t appear to be a difference in the pictures, BUT THAT IS NOT THE POINT.
 

re:2) PGS couldn''t read ascii STL''s so Rockdoc imported the ascii STL''s to DC and exported binary STL''s from DC, and got bogus results regarding "culet" and "girdle" deductions, but all four files gave AGS 0''s for the ray tracing portion of the software.


What is the agenda?

It is agenta. is it official answer from your or AGS, what:

"6 mm 80 LG P41 Cr35 T57
1) Girdle( In bezel) 3% Star 50%
2) Girdle( In bezel) 3.5% Star 50%
3) Girdle( In bezel) 3% Star 55%
4) Girdle( In bezel) 3.5% Star 55%

"

have AGS0?

IN such case we can back to first question: two Type AGS charts.
or How did same diamond receive AGS=3 in AGS CHART?

 
re:Perhaps you should have whomever sent you the erroneous PGS resuts (probably arising because of misinterpreted extraneous STL''s or combined facets) to send you the detailed breakdown of where the deductions came from..


Marty, I do not see reason do it.


History:
1) I asked on PS published full PGS-AGS report for my 4 examples
2) I received answer with very strange results from one source. ( AGS0-AGS3 like in AGS charts) It was very strange for me and I asked you( in privet correspondence send your results) I did not mention about these result on PS. You did it firstly
3) Then I received several letters from you and AGS staff with information about some problem with DC stl files( I proof what DC stl file is correct)
4) I did not receive from you and AGS PGS reports ( for my CORRECT STL file or any other files) yet
5) You have just published what ROCDOC received AGS0 for all 4 files. Could I see full PGS report and file with models?

I received ATTACK from you , AGS and nothing with result from PGS software

 
Date: 2/23/2007 5:22:40 PM
Author: Serg

re:Perhaps you should have whomever sent you the erroneous PGS resuts (probably arising because of misinterpreted extraneous STL''s or combined facets) to send you the detailed breakdown of where the deductions came from..


Marty, I do not see reason do it. Why not?


History:

1) I asked on PS published full PGS-AGS report for my 4 examples And I attempted to do so.
2) I received answer with very strange results from one source. ( AGS0-AGS3 like in AGS charts) It was very strange for me and I asked you( in privet correspondence send your results) I did not mention about these result on PS. You did it firstly Yes, and did you bother to ask why? Was it "culet" or "girdle"? Because it certainly wasn''t performance ray trace issues, which you certainly have available through your other source.

3) Then I received several letters from you and AGS staff with information about some problem with DC stl files( I proof what DC stl file is correct) Because in the translation using DC from ascii STL files that I generated to the binary STL''s, that DC generated from the ascii files done by RockDoc, there were anomolous results, similar to some problems I have seen ijn the past with Sarin files, related to tiny anomolous STL facets whose normals were not correct. Since I do not have the AGS software, I asked AGS to look into the problem, and told RockDoc the total grades were problematic.

4) I did not receive from you and AGS PGS reports ( for my CORRECT STL file or any other files) yet Why should I release t you, or anone else, results I knew to be problematic, becuse of annomolout STL files interacting with the PGS software in ways unanticipated.

5) You have just published what ROCDOC received AGS0 for all 4 files. Could I see full PGS report and file with models? Sure, and I can show that DC ascii STL''s and binary STL''s appear to be slightly different, for whatever reason I don''t know. And so then Rockdoc did a binary export of the DC ascii files to generate these results.

I received ATTACK from you , AGS and nothing with result from PGS software. But Sergey, you DEMANDED results, and I told you that there appeared to be a problem, consistent with erroneous data in STL files, yet you refused to even look at the STL files I sent you, both binary and ascii, AND then went here on PS to say there was a problem. And yes there is a problem, GIGO.. Sorry, but all I was trying to do is come to the root of the problem privately. I have utmost respect for your software, but both I and AGS, independendtly, have seen apparent inconsistencies, numerical or otherwise, and all I tried to do is find the cause of the problem.

I showed you mine, now you show me yours!!!!!!!!!!!

marty1stl.jpg
 
Serg....

I don''t think Marty is attacking you.

From my working with him, on a similar problem to get the Sarin graphical painted girdle images "fixed", we saw similar issues.

Marty just wants to get it corrected.

Both Sarin and AGS bent over backwards to cooperate and help in order to improve the accuracy of the scans previously and Marty has the same interest at heart.

I do too, as I want to provide the highest level of reliability in what I provide whether it is result from Sarin,DiaCalc, AGS, B Scope, or Gemprint, or any other computer program / equipment used.

Hope you''re well.

Regards,

Rockdoc
 
Date: 2/23/2007 10:17:36 PM
Author: RockDoc
Serg....

I don''t think Marty is attacking you.

From my working with him, on a similar problem to get the Sarin graphical painted girdle images ''fixed'', we saw similar issues.

Marty just wants to get it corrected.

Both Sarin and AGS bent over backwards to cooperate and help in order to improve the accuracy of the scans previously and Marty has the same interest at heart.

I do too, as I want to provide the highest level of reliability in what I provide whether it is result from Sarin,DiaCalc, AGS, B Scope, or Gemprint, or any other computer program / equipment used.

Hope you''re well.

Regards,

Rockdoc
Bill,
1) I had sent Binary STL to Marty and AGS. And did not receive any reports from Binary stl( We developed such export SPECIALY for AGS -PGS) and I do not see any reason to try use ASCII STL for PGS. I am not understanding what all you( MARTY-BILL-AGS staff ) are doing now. WHat is your goal?
2) DC 2.8.0 build 375 has binary stl export
3)Before yesterday I did not receive any information about problem with DC STL export( EVEN yesterday nobody inform about any problem with binary stl export from DC)
4) DC fine works with both type STL ( Binary, ASCII,.. after several import export) .
5) The problem PGS-AGS software with STL is inside PGS software. ( STL format is bad for any optical calculation, firstly you(AGS-PGS) need convert small STL facet( parts one real facet) to ONE real facet. Only then you can start optical calculation .DC do it from day of first import stl format. Amazing what AGS-PGS does not do it until now)
6) We did not receive yet any explanation why P41Cr35T57( Girdle 3-3.5%, start 50-55%) have AGS 0 in PGS software , but AGS0 and AGS3 in AGS charts. First explanation form Marty was:
"2) The two sets of charts are for TWO DIFFERENT girdle thicknesses and star facet lengths, and some regions of the underlying factors have rather steep gradients for performance factors. One only has to look at MSU and GIA"s published works to validate this statement.
"
Now we see it was wrong explanation and we did not receive any reasonable explanation/
Again could anybody print PGS full report for binary STL my 4 example( you can do binary STL easy in DC 2.8.0 or I can send such STL)
 
re:Marty, I do not see reason do it. Why not?

Marty,

On PS I publish two type data:
1) From me
2)Not from me if I can check result( for example from other source )
 
re: Marty: But Sergey, you DEMANDED results, and I told you that there appeared to be a problem, consistent with erroneous data in STL files, yet you refused to even look at the STL files I sent you, both binary and ascii, AND then went here on PS to say there was a problem.

Marty, completely wrong interpretation what had been done by me on PS:

1) Firstly, I checked files in DC and did not find any problems.
2)Secondly, I have started Discuss this issue on PS ( just proof DC STL export by pub;ish pictures ) , only after your attack( " the problem you choose to address publically arises because DIAMONDCALC can, and did, generates STLS that are BOGUS")

Before this your attack I did not use any result( any information) from PGS software on PS!. I used AGS charts and my experience with DC and cut study ONLY/



Please check. Anybody can check it:


"Marty,
I do not need any software for statement what such similar diamonds should receive same rating, grade.../ Difference 1% in rating is quit normal, but difference in 3 grades for 10 steps grade system is quit abnormal.
I do not know about reason this mistake in AGS grade( two possibility: Or AGS change grade system ( and these grades from different software) or AGS-PGS has big problems with continuity in point)
"
Nothing about STL problem. Just about main issue what P41CR35T57 has different grade in different AGS charts( AGS0 and AGS3)
(Or AGS change grade system ( and these grades from different software) or AGS-PGS has big problems with continuity in point)

 
AGS-PGS result from Binary STL ( export from Diamcalc)

AGS_PGS_P41Cr35T57.gif
 
re:

Sergey:2) I received answer with very strange results from one source. ( AGS0-AGS3 like in AGS charts) It was very strange for me and I asked you( in privet correspondence send your results) I did not mention about these result on PS. You did it firstly

Marty:Yes, and did you bother to ask why? Was it "culet" or "girdle"?

No. It was other problem. I received result from other files.
May be You and Rocdoc were first who find PGS problem with culet and girdle deductions for ASCII STL.

I understood this problem ONLY after you published on PS PGS results with HUGE deductions. I had not any idea why you and AGS sent me a lot of STL files. And I never before mentioned about this problem( in PS or emails) Just because I had not any possibility see and know about such problem( You sent me just stl files with strange for explanations without PGS results)



Marty,
Is it clear for you now? Please check all post in right order.
Could we back to main issue about AGS charts?
 
Date: 2/24/2007 10:35:32 AM
Author: Serg

re:

Sergey:2) I received answer with very strange results from one source. ( AGS0-AGS3 like in AGS charts) It was very strange for me and I asked you( in privet correspondence send your results) I did not mention about these result on PS. You did it firstly

No Sergey, you timeline is slightly off. Quoting you on PS AFTER I sent you STLs saying there was a problem "Marty,
I do not need any software for statement what such similar diamonds should receive same rating, grade.../ Difference 1% in rating is quit normal, but difference in 3 grades for 10 steps grade system is quit abnormal.
I do not know about reason this mistake in AGS grade( two possibility: Or AGS change grade system ( and these grades from different software) or AGS-PGS has big problems with continuity in point)"



Marty:Yes, and did you bother to ask why? Was it ''culet'' or ''girdle''?

No. It was other problem. I received result from other files.



May be You and Rocdoc were first who find PGS problem with culet and girdle deductions for ASCII STL.Sergey For the 10th time, PGS cannot read ascii STL''s. The problem was that Rockdoc used DiamondCalc to go from the original ascii STL to a binary STL and got the problem results. The problem is in bad STL''s conversions in going from ascii to binary. (Sort of annalogous to trying to anticipate and code for all conditions that could give you a divide by zero error)



I understood this problem ONLY after you published on PS PGS results with HUGE deductions.

OK now we are on the same page..

I had not any idea why you and AGS sent me a lot of STL files. And I never before mentioned about this problem( in PS or emails) Just because I had not any possibility see and know about such problem( You sent me just stl files with strange for explanations without PGS results)I have to forgive you Sergey, your English is MUCH better than my Russian. We do have a communication problem.


Marty,
Is it clear for you now? Please check all post in right order. I did, see above

Could we back to main issue about AGS charts?

There is no "issue" about the original AGS charts, they were released as cutting guidlines only, it is not a dumbed down parametrically based system that anyone can impliment without raytracing.. End of story.

 
re:No Sergey, you timeline is slightly off. Quoting you on PS AFTER I sent you STLs saying there was a problem "Marty,
I do not need any software for statement what such similar diamonds should receive same rating, grade.../ Difference 1% in rating is quit normal, but difference in 3 grades for 10 steps grade system is quit abnormal.


Marty,
It has not any connection with your letters at all:
1) You did not send in your letters results PGS grade at all. ( My statement about difference in 3 grades can not come from information from your letters)
2) It was answer to you post about difference in DC metric( 0.97/0.98) for my 4 examples. I said 1% is not problem but 3 grades( AGS0-AGS3) for diamonds which have minor difference in girdle and Star is REAL problem/
I did not change Issue topic, but because you found new problem in PGS software you though I am speaking about new problem


 
re:End of story.

No Marty,
It is not end
A lot of people are wating explanation from AGS now
 
Date: 2/24/2007 2:02:51 PM
Author: Serg
re:End of story.

It is not end
A lot of people are wating explanation from AGS now



Please check. Anybody can check it:


I do not need any software for the statement that very similar diamonds should receive the same rating. Grading difference of 1% in rating is quite normal, but difference of 3 grades for a 10-step grading system is quit abnormal.


I do not know about the reason for this mistake in AGS grade. Two possibilities are that AGS changed the grading system (and these grades are from different software) or AGS-PGS has big problems with continuity at a point)


Leaving the STL problem aside, consider just the main issue that P41CR35T57 has different grades in different AGS charts ( AGS0 and AGS3)


Is it clear for you now? Please check all posts in the right sequence.
Could we go back to the main issue about the AGS charts?

Sergey Sivovolenko



Sergey’s main question, why P41CR35T57 has different grades in different AGS charts, is the same question I addressed in my posts that are now buried three pages back.


I was told that the cut grading guideline charts were the AGS’s initial determinations for optically symmetric cutting with the constraints and proportions listed on each graph.


Peter is very forthcoming in supplying the updated grade for any specific combination of parameters such as the 56/41/35/50/80/ symmetric case that I asked him for. The argument for updating the charts is for completeness and so that the AGS position may be correctly represented. It is to remove confusion like the P41CR35T56 Ideal 0 combination that is currently labeled a 2.


Seems to me that both Sergey and I have made an earnest case for the importance of AGS issuing an update to the cut grading guidelines.

Michael Cowing
 
Date: 2/24/2007 3:10:31 AM
Author: Serg
AGS-PGS result from Binary STL ( export from Diamcalc)
Sergey..

As I understand the "problem" with STL''s

1) Create a model in DC and directly export to binary STL format, you get one set of STL''s

2) Create the same model in DC, export to ascii STL format, re-import to DC and export to binary STL and you get a different set of STL''s.

Probably caused by internal software rounding (single/double precision/whatever) and attempt to fill in the "blanks" where there "appears" to be mathematical inconsistencies, but in effect are LSB differences.

How close can two vertices be to one another, before they are considered one point, and not two points.

What I theorize what happens is, that you wind up creating infinitesimally small facets whose normals appear to come from the girdle plane or be associated with some other facet, like the culet, because one always tries to close the "form".

Let us say you read in double precision numbers as single precision, as you can do with ascii files (as opposed to binary). Then the subsequant math is working with truncated variables. (not as bad as GIA rounding though
41.gif
)

Because of the small "virtual" facet size relative to the whole stone, you don''t materially effect any raytracing (or image, think of it as one bad pixel on a screen) but you do wind up potentially effecting software that hasn''t anticipated all possible "errors", so to speak.

When I put "errors" in quotes, I mean they are caused by LSB (Least Significant Bit, for the uninitiated) math, and are very difficult to "prevent" either in generation (of STL''s) or interpretation (by PGS or any other software, like mine
17.gif
).
 
Date: 2/24/2007 2:10:46 PM
Author: michaelgem

Seems to me that both Sergey and I have made an earnest case for the importance of AGS issuing an update to the cut grading guidelines.

Michael Cowing
No you haven''t made any case, at all. All you have done is whine that you are not getting your way.

The original charts were GUIDELINES ONLY, intended to indicate that if you cut inside those guidelines you were MORE LIKELY to receive the desired grade, than if you cut on the edge of a potential cliff.
 
Date: 2/24/2007 2:20:33 PM
Author: adamasgem

Date: 2/24/2007 3:10:31 AM
Author: Serg
AGS-PGS result from Binary STL ( export from Diamcalc)
Sergey..

As I understand the ''problem'' with STL''s

1) Create a model in DC and directly export to binary STL format, you get one set of STL''s

2) Create the same model in DC, export to ascii STL format, re-import to DC and export to binary STL and you get a different set of STL''s.

Probably caused by internal software rounding (single/double precision/whatever) and attempt to fill in the ''blanks'' where there ''appears'' to be mathematical inconsistencies, but in effect are LSB differences.

How close can two vertices be to one another, before they are considered one point, and not two points.

What I theorize what happens is, that you wind up creating infinitesimally small facets whose normals appear to come from the girdle plane or be associated with some other facet, like the culet, because one always tries to close the ''form''.

Let us say you read in double precision numbers as single precision, as you can do with ascii files (as opposed to binary). Then the subsequant math is working with truncated variables. (not as bad as GIA rounding though
41.gif
)

Because of the small ''virtual'' facet size relative to the whole stone, you don''t materially effect any raytracing (or image, think of it as one bad pixel on a screen) but you do wind up potentially effecting software that hasn''t anticipated all possible ''errors'', so to speak.

When I put ''errors'' in quotes, I mean they are caused by LSB (Least Significant Bit, for the uninitiated) math, and are very difficult to ''prevent'' either in generation (of STL''s) or interpretation (by PGS or any other software, like mine
17.gif
).

Marty,

If you want discuss ASCII stl please open new thread. This thread is about AGS charts.
In your first post in ASCII STL thread please explain: why is not enough for you(or AGS) work with binary STL?( It had been done specially for PGS-AGS. )
I will spend time Octonus developer only for important for market tasks.
For most DC clients export to STL is not necessary at all.
AGS researchers can use binary STL.
BTW I have not task support my competitors or fix AGS problems
End this story.
regards to AGS.
 
Date: 2/24/2007 2:30:00 PM
Author: adamasgem


Date: 2/24/2007 2:10:46 PM
Author: michaelgem



Seems to me that both Sergey and I have made an earnest case for the importance of AGS issuing an update to the cut grading guidelines.

Michael Cowing
No you haven't made any case, at all. All you have done is whine that you are not getting your way.

The original charts were GUIDELINES ONLY, intended to indicate that if you cut inside those guidelines you were MORE LIKELY to receive the desired grade, than if you cut on the edge of a potential cliff.



MARTY,


It is not GUIDELINES ONLY.


IT IS WRONG AGS GUIDELINES FOR CUTTERS.


It's main MICHAEL's ISSUE and IT IS CORRECT RIGHT QUESTION. AND WE HAVE RIGHTS to receive CORRECT AND RIGHT ANSWER
IF YOU CAN NOT DO IT please stop your SQUABBLE here.
 
Date: 2/24/2007 2:36:56 PM
Author: Serg


Marty,

If you want discuss ASCII stl please open new thread. This thread is about AGS charts. Only brought up because in an attempt to answer your question, we found a problem

In your first post in ASCII STL thread please explain: why is not enough for you(or AGS) work with binary STL?( It had been done specially for PGS-AGS. ) Sergey.. Please reread the thread. PGS uses ONLY binary files. I generated the original STL''s as ascii, sent them to Bill, and when we found that PGS doesn''t read the ascii files, they were converted to binary files in DiamondCalc, and wound up giving erroneous results.

I will spend time Octonus developer only for important for market tasks. No problem..

For most DC clients export to STL is not necessary at all. I agree
AGS researchers can use binary STL. And they do..
BTW I have not task support my competitors or fix AGS problems..AGS will fix the problems with trapping unexpected erroneous input, I suppose that you will look at the commentary objectively, and address the issue in DC with maybe a warning that file conversions may not always give what you expect, because of numerical differences.

End this story.
regards to AGS.

Keep up the good work, I have been very pleased with what I see in DiamondCalc
 
Date: 2/24/2007 2:44:13 PM
Author: Serg


MARTY,

It is not GUIDELINES ONLY.



IT IS WRONG AGS GUIDELINES FOR CUTTERS.

It''s main MICHAEL''s ISSUE and IT IS CORRECT RIGHT QUESTION. AND WE HAVE RIGHTS to receive CORRECT AND RIGHT ANSWER
IF YOU CAN NOT DO IT please stop your SQUABBLE here.
Sergey, I don''t see where you or Michael have any "RIGHTS" at all.

Particularly when you take COPYRIGHTED AGS GUIDELINE charts and try to impliment them in your DiamondCalc software as a parametrically based grading system, which they are NOT. (AGS_2005 Appraiser)
17.gif


Good try, but no cigar. I can see facts and and read between the lines..
 
Date: 2/24/2007 3:39:26 PM
Author: adamasgem



Date: 2/24/2007 2:44:13 PM
Author: Serg





MARTY,



It is not GUIDELINES ONLY.






IT IS WRONG AGS GUIDELINES FOR CUTTERS.




It's main MICHAEL's ISSUE and IT IS CORRECT RIGHT QUESTION. AND WE HAVE RIGHTS to receive CORRECT AND RIGHT ANSWER
IF YOU CAN NOT DO IT please stop your SQUABBLE here.
Sergey, I don't see where you or Michael have any 'RIGHTS' at all.

Particularly when you take COPYRIGHTED AGS GUIDELINE charts and try to impliment them in your DiamondCalc software as a parametrically based grading system, which they are NOT. (AGS_2005 Appraiser)
17.gif


Good try, but no cigar. I can see facts and and read between the lines..
WE =MARKET ( here), Cutters for example.
Michael and I just asked it on PS.
Ask AGS, Have Market rights or not? :)
BTW Somebody in GIA though what market has not rights to demand FREE RIGHT GUIDELINES for cutters.
Not only cutters depend from LABs, Labs depend from cutters too

. re:Particularly when you take COPYRIGHTED AGS GUIDELINE charts and try to impliment them in your DiamondCalc software as a parametrically based grading system, which they are NOT. (AGS_2005 Appraiser)

BTW.I had permission for it. Ask AGS again . Or Are you new AGS lawyer .:)
 
Date: 2/24/2007 3:52:15 PM
Author: Serg

WE =MARKET ( here), Cutters for example.
Michael and I just asked it on PS.
Ask AGS, Have Market rights or not? :)

BTW Somebody in GIA though what market has not rights to demand FREE RIGHT GUIDELINES for cutters.
In GIA''s case, I think their output should be public domain, because of the tax status issues.

Not only cutters depend from LABs, Labs depend from cutters too.. Yup, and the "wider" their ystem th tendency for more business

. re:Particularly when you take COPYRIGHTED AGS GUIDELINE charts and try to impliment them in your DiamondCalc software as a parametrically based grading system, which they are NOT. (AGS_2005 Appraiser)

BTW.I had permission for it. Ask AGS again . Or Are you new AGS lawyer .:) Then I appologize. But I doubt if you were given permission to issue "grades" or to publish software that gives AGS_2005 "parameters quality" for conditions which were never published. Seems a software fix is in order?

6by6.jpg
 
re:BTW.I had permission for it. Ask AGS again . Or Are you new AGS lawyer .:) Then I appologize. But I doubt if you were given permission to issue "grades" or to publish software that gives AGS_2005 "parameters quality" for conditions which were never published. Seems a software fix is in order?

Marty,
I will happy discuss it with AGS in court. It will give me good publicity.
Are you new AGS lawyer?
If you are not AGS lawyer please do not to try do him work here and lose my time.
You have lost something very important during this post
BTW I will happy delete any mention about AGS( and of course any DATA from AGS and ASET) from DC3.0 . It is not problem for OctoNus at all. And what is more I do not like more help to AGS.
One advice Marty: before you will continue here your lawyer work, discuss with Peter firstly.
Did you hear: I will HAPPY delete all from AGS in DC3.0 :)
 
Date: 2/24/2007 4:32:15 PM
Author: adamasgem

Date: 2/24/2007 3:52:15 PM
Author: Serg

WE =MARKET ( here), Cutters for example.
Michael and I just asked it on PS.
Ask AGS, Have Market rights or not? :)

BTW Somebody in GIA though what market has not rights to demand FREE RIGHT GUIDELINES for cutters.
In GIA''s case, I think their output should be public domain, because of the tax status issues.

Not only cutters depend from LABs, Labs depend from cutters too.. Yup, and the ''wider'' their ystem th tendency for more business

. re:Particularly when you take COPYRIGHTED AGS GUIDELINE charts and try to impliment them in your DiamondCalc software as a parametrically based grading system, which they are NOT. (AGS_2005 Appraiser)

BTW.I had permission for it. Ask AGS again . Or Are you new AGS lawyer .:) Then I appologize. But I doubt if you were given permission to issue ''grades'' or to publish software that gives AGS_2005 ''parameters quality'' for conditions which were never published. Seems a software fix is in order?
re:publish software that gives AGS_2005 ''parameters quality'' for conditions which were never published. Seems a software fix is in order?

from http://www.octonus.com/oct/products/3dcalc/standard/diamcalc_2-4.phtml

"The new AGS appraiser for Brilliant and Prince cuts is added. It is named AGS_2005. This appraiser provides estimation of the overall cut quality, using several cut parameters simultaneously. The parameters that are taken into account during stone appraisal are displayed in gray, red or green color. The red color means that it is necessary to decrease the parameter value to get to a better group, the green color suggests to increase the parameter value. There is also a special button "Better group" that changes all parameters of the stone to move it to a nearest better group. "

What is color for diameter? :)
 
Status
Not open for further replies. Please create a new topic or request for this thread to be opened.
GET 3 FREE HCA RESULTS JOIN THE FORUM. ASK FOR HELP
Top