Here you can find information about what is new in HPOxygen Server version 5.4.6.
The functionality described in this section is available to users.
It is now possible to get a much higher mass for RBC when running SmartRecut with the GIA Facetware+MyRound appraiser, as the Diameter (Symmetry) for VG and GD grades now may vary in full GIA boundaries (previously it was limited by 0.7 as for the EX grade).
New boundaries are:
Sometimes, the custom facet marking of a model (if it has this marking) may differ from the facet marking applied to the model in Polish Report (Auto Marking). Now the Polish Report dialog provides you information about this difference and allows to select which marking to use in the report.
No custom marking | Markings identical | Markings differ | |
---|---|---|---|
In HP Oxygen, now for the shadow models, cavities previously built with XRay may be applied. This can be done several times throughout the polishing process.
The general workflow is the following:
(in the steps below "Intersector" is an XRay model from DM containing cavities)
Model | Applied Cavity - Model |
---|---|
From the Algorithm list, the outdated algorithms have been removed: only algorithms of 2013 and later plus "06. Semicut (final)" are now in the list.
Also, on opening, the list of algorithms now only shows the algorithms marked as Favorites.
Was | After deletion of outdated | Favorites |
---|---|---|
Currently selected algorithm is highlighted with bold . To add the algorithm to favorites, click . Clear the star to remove from favorites. | To see the full list, click show all. |
In Relative appraiser, now:
Wrong values are highlighted with red. On editing finish, the wrong value is automatically substituted with the nearest correct (0,01 or -0,01).
The speed and accuracy of the Crown and Pavilion Reflect algorithms are increased.
The following fixes for the known problems and improvements have been implemented:
The problem with the excessive facets near the culet in the RBC scan has been solved.
It has been found that during the shadow scanning for Brilliant cutting, the excessive facets were created near the culet. In the case of scanning the same stone for AnyCut cutting, these facets were not presented. This meant there had been an error in RBC scanning. The example is presented in the picture: In the pictures: magenta - RBC, green - AnyCut. |
The table correction rules have been changed, which solves some problems including not highlighting facets on Crown Reflect
When working with Solutions Report and accidentally entering "0" or empty value for the Columns per page option, the report stopped working (black screen). It did not work after the system re-start either. To solve this problem now you can re-run the program or re-open the project which will restore the normal functioning of the Solutions Report.
The information in this section is for sharing with Lexus only.
The following fixes for the known problems and improvements have been implemented:
The problem with the excessive facets near the culet in the RBC scan has been solved.
From: <janak@lexus-com.com> Dear Sergey, Can you please check this model construction? We also noticed that when the model is built as Anycut, the construction is more close to counters. Model in Magenta color is Shadow model. That is Green color is built as Anycut. |
The algorithm finding the symmetry axis for the round cuttings of non-standard forms has been improved. The errors in the previous algorithm version sometimes led to identical solutions in SmartRecut AnyCut.
When working with Solutions Report and accidentally entering "0" or empty value for the Columns per page option, the report stopped working. It did not work after the system re-start either. To solve this problem now you can re-run the program or re-open the project which will restore the normal functioning of the Solutions Report.
От: "Utpal Mistry" <utpal@lexusindia.in> By Mistake , I had entered (Zero) in No of columns in solution report and then the Solution reports behaves erratically (Even if I restart the program). Can we also validate this , so that no one can enter (Zero) or default can be at least one. Fixed: |