> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/scopeview/use-tools-and-templates/use-and-create-templates.md).

# Use & Create Templates

In order to accelerate the configuration of repetitive and identical acquisitions from one session to another, ScopeView allows you to save and retrieve the information on the formulas to evaluate.

**The following information is contained in a template acquisition:**

* List of sources used
* Acquisition numbers
* List of signals to acquire
* List of formulas to evaluate
* Editing information (number of columns, superimposition, zoom, etc.)

## **Open a template**

You can load a previously saved template acquisition by selecting the button or the Open Template... item in the File menu. The software displays the form to select the file to open. The scroll list allows navigating in the file tree-structure.

To load a template acquisition, click on the button or from the File menu click on Open Template...

<figure><img src="https://1028368895-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwfLeQP2Iaoefor0ZUNi%2Fuploads%2FOEvGEpZEe0vVgrF0lnaz%2Fimage.png?alt=media&amp;token=62def1d4-279a-4d97-a26d-6aca74381b4d" alt="" width="432"><figcaption></figcaption></figure>

## **Acquisition parameters**

### Number of acquisitions

The Number of Acquisition field specifies the number of acquisitions to be executed by ScopeView.

If the signals originate from acquisition units, it can be useful to have a number of acquisitions higher than one to see the evolution of the acquisition signals from one acquisition to another or to compute the average of the results obtained.

## Save a template

After editing your data sources and acquisition parameters, you may save the template for future acquisitions. The recommended format is *.svt* (ScopeView Template). The legacy *.xml* format should be avoided as it is a generic extension and may result in confusion with other files used for other purposes.

### Save options

<table><thead><tr><th width="201.272705078125">Option</th><th>Description</th></tr></thead><tbody><tr><td>Save Signals Data</td><td>Using this option will save in the template the last set of values acquired by ScopeView for each signal. Upon reopening the template, the graphs will be automatically populated, without needing a simulation. However, to perform another acquisition, the simulation will be required again.</td></tr><tr><td>Save using relative path</td><td>File data sources will remember a relative path to the template, improving its portability. In order to simplify exporting a model and reimporting on another PC, it is recommended to use this option and to keep the files next to the template location, or under folders and subfolders next to the template.</td></tr></tbody></table>


---

# 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://www.opal-rt.com/docs/scopeview/use-tools-and-templates/use-and-create-templates.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.
