> For the complete documentation index, see [llms.txt](https://docs.tracr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tracr.com/tracr-help-pages/lab-eligibility-main-issues-and-how-to-fix.md).

# Lab Eligibility: Main Issues and How to Fix

## Missing Scan Report

If you are missing a scan report and want to grade your diamond through a Tracr intergration, you will need to upload a polished diamond and a supported scan report that Tracr can process.

Please follow the guidelines below to help upload a scan report.

## Invalid Scan Report

If your scan report is invalid, you have uploaded a scan report that is not .xml, .htm, or .html. Manually renaming a file's extension will not make it valid.

Please follow the guidelines below to help upload a valid scan report.

## Scan Report Guide

### Supported Scan Report

A diamond needs a supported scan report to be eligible for grading. Tracr currently supports Sarine XML scan reports and Helium HTM and HTML scan reports.

> We support Helium Carbon versions that generate a .Ox2z file extension, beginning with Carbon version 1.0.\
> For the latest version, please visit the [official Helium Website](https://lexusindia.in/#software).

Example scan reports:

* [Sarine XML](https://jcpackages.tracr.network/integration/demo_polished_1.xml)
* [Helium HTML](https://jcpackages.tracr.network/integration/example_helium.html)

#### Prepare a polished diamond dataset

Follow these steps to prepare polished diamond data for upload to Tracr.

**Sarine Instructor**

If you are using **Sarine Instructor** to provide a scan for polished diamonds, you need to generate an XML report and an STL export. Use the template provided by Tracr to export the report for each diamond.

In the CSV file, Tracr needs the STL file in the column **scan**, and the XML report in the column **scan\_report**.

[Download Sarine export templates](https://jcpackages.tracr.network/integration/Polished_Diamond_Sarine_Instructor_Export_Template.zip)

**Sarine Instructor: Extracting data for polished diamonds**

Extracting the required traceability data for polished diamonds using Sarine Instructor software is compatible with the following hardware:

* DiaMension
* DiaMension HD
* DiaMark HD
* DiaMark™ HD

Once a polished diamond is scanned and the file loaded onto the Instructor software, you can extract the following data points:

* Diamond Measurements (using a provided template)
* Diamond 3D Model

The following instructions describe how to extract the required data.

{% stepper %}
{% step %}

### Install the Tracr templates for polished diamonds

* Place the Tracr template file, e.g. ‘TracrPolishedTemplate.txt’, within the Sarine Instructor Export folder:\
  Sarine Technologies/Instructor/Export/
  {% endstep %}

{% step %}

### Export diamond measurements

1. Open the stone .srn file in Sarine Instructor.
2. Point to the **Export** icon, and select the corresponding Tracr template, for example, ‘TracrPolishedTemplate.txt’.
3. In the **Save As** dialog box, save the measurements as ‘YourStoneName.xml’.
   {% endstep %}

{% step %}

### Export the mesh

1. Open the stone .srn file.
2. Point to the **Save** icon, and select **Save as**.
3. In the **Save As** dialog box, select ‘\*.stl’ as the file type and save the mesh with the stone's name.
   {% endstep %}
   {% endstepper %}

**Helium software**

If you are using **Helium software** to provide a scan for polished diamonds, you need to generate an HTM/HTML report and an STL export. Use the template provided by Tracr to export the report for each diamond. There are two types of Helium template:

* Specific shape, only for a handful of shapes with additional information.
* Generic, less information but you can use this template for all shapes.

| Shape    | Recommended template              |
| -------- | --------------------------------- |
| Princess | HTML\_REPORT\_FOR\_PRINCESS       |
| Radiant  | HTML\_REPORT\_FOR\_RADIANT        |
| Heart    | HTML\_REPORT\_FOR\_Any\_Cut       |
| Pear     | HTML\_REPORT\_FOR\_Any\_Cut       |
| Oval     | HTML\_REPORT\_FOR\_OVAL\_MARQUISE |
| Marquise | HTML\_REPORT\_FOR\_OVAL\_MARQUISE |
| Cushion  | HTML\_REPORT\_FOR\_CUSHION        |
| Emerald  | HTML\_REPORT\_FOR\_STEP\_CUT      |

In the CSV file, Tracr needs the STL file in the column **scan**, and the HTM/HTML report in the column **scan\_report**.

For more information about exporting using a Helium Polish Scanner, please refer to the [Helium Polish Scanner - Settings for Export (PDF)](https://www.lexusindia.in/download/download-files/HELIUMPOLISH_SETTINGS_FOR_EXPORTS.pdf).

[Download Helium templates](https://jcpackages.tracr.network/integration/helium_templates.zip)

{% hint style="info" %}
**Please note:**

* Before uploading polished diamond data, please make sure that you register the parent diamond on Tracr.
* To verify the polished diamond, a 3D scan and the report of the scan of the diamond are crucial.
* Providing the images and videos is optional, however, this will greatly improve the Diamond Experience.
* Add the grading document to complete the polished digital asset.
  {% endhint %}

To populate a polished diamond CSV file:

{% stepper %}
{% step %}

### Download the polished CSV file template

(**Integration Tool > Integration toolkit > CSV Templates**).
{% endstep %}

{% step %}

### Populate the CSV file

One row per diamond.
{% endstep %}

{% step %}

### Use the Data Dictionary

It is recommended that you download and use the Data Dictionary (**Integration Tool > Integration toolkit > Data dictionary**) to help you to populate the CSV file. Filter the Data Dictionary by "Stone State = Polished". Ensure that you populate fields with the column "Required = true".
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tracr.com/tracr-help-pages/lab-eligibility-main-issues-and-how-to-fix.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.