> For the complete documentation index, see [llms.txt](https://docs.m-xr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.m-xr.com/marso-measure/getting-started/processing.md).

# Processing

Follow this page when you are ready to process.

{% hint style="success" %}
Once you have produced an Alembic, ST Map(s), and optional Mask Mesh, you are ready to process the Job to produce your textures.
{% endhint %}

1. Hover over Actions on the right side and click Process.

<div align="left"><figure><img src="https://content.gitbook.com/content/dSWZvUSEhiy6J2XcG20t/blobs/IhcncrHYryLPWfSsrr3A/ProcessJob.png" alt="" width="563"><figcaption></figcaption></figure></div>

2. Select your exposure preset by clicking the drop down, if you are yet to create your exposure preset, see [here](/marso-measure/resources/creating-an-exposure-calibration.md).
3. Select the light system used by clicking the drop down, if you are yet to create a light system, see [here](/marso-measure/resources/creating-a-light-system.md).
4. Choose the photogrammetry software you used, for more information on photogrammetry, see [here](/marso-measure/getting-started/photogrammetry.md).
5. In the mesh file, mask mesh (Optional) and ST map area, provide the necessary paths.
6. Select your desired output resolution, if multiple are selected, the materials will be processed at the highest resolution and smaller textures will be down-sampled from it).
7. Select your Model
8. Once done you can apply the changes to keep them for later without adding to the queue, or save and queue last to put at the back of the queue. Additional queue options are available in the drop-down menu.

<div align="left"><figure><img src="https://content.gitbook.com/content/dSWZvUSEhiy6J2XcG20t/blobs/o1bKWvVsAaIfmlx8VlhX/ProcessConfig.png" alt="" width="563"><figcaption></figcaption></figure></div>

***

#### Export from Marso Measure

When processing is complete you will find an new item in the asset library. This shows all assets that are available for export.

1. Click on Asset Library.
2. Find your desired job and click Export.
3. Select your export file format, multiple formats can be selected.&#x20;
4. Choose your desired output path for results.

***

#### Interrupting a job

<figure><img src="https://content.gitbook.com/content/dSWZvUSEhiy6J2XcG20t/blobs/VnSrkuyh0k3wpvDuy1CO/Screenshot%202025-07-09%20at%2015.46.07.png" alt=""><figcaption></figcaption></figure>

A running job can be interrupted with either the stop or skip button. Both will lose any progress up to this point.

&#x20;The stop button will return it to the front of the queue, and stop processing queue items, while the skip button will immediately start processing the next item in the queue.

***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.m-xr.com/marso-measure/getting-started/processing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
