> 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-functions/advanced-functions/advanced-or-sidseuil.md).

# Advanced | SIDSEUIL

## OVERSHOOT TIME – \[SIDSEUIL]

Computes the period of time during which a threshold value is reached in a signal.

## **CATEGORY**

Advanced

![](https://content.gitbook.com/content/fwfLeQP2Iaoefor0ZUNi/blobs/d9sFX5WNL31OyH4fHoCJ/hyp45.PNG)

## **DESCRIPTION**

The function computes the period of time and different results related to the overshoot time during which a threshold value is reached in a signal, either on a rising or a falling edge(Slope).

It computes the beginning and ending time and duration of the threshold condition.

To perform the analysis, a new signal is generated with the three signals specified as input parameters and following the type of threshold specified.

Based on the slope value, resulting signal calculated as follow:

<table data-header-hidden><thead><tr><th width="216.727294921875"></th><th></th></tr></thead><tbody><tr><td><strong>Rise(m)</strong></td><td>Resulting signal is the maximum of the three signals.</td></tr><tr><td><strong>Fall(d)</strong></td><td>Resulting signal is the minimum of the three signals.</td></tr></tbody></table>

When samples do not belong to the signal part specified, values are replaced by 0.0.

User must specify three input signals. However, if only one signal is to be used, then the same name should be given to all three signals. When only one signal is processed, the maximum and minimum samples will result in one identical signal. Similarly, if two signals are to be processed, the third signal to be used can be identical to one of the first two.

## **RESULT VARIABLES AND PARAMETERS**

<table data-header-hidden><thead><tr><th width="144.00006103515625"></th><th></th></tr></thead><tbody><tr><td><strong>tsed</strong></td><td>From the starting time of the analysis, course of the generated signal to find the time at which the threshold value is reached based on the type of threshold specified. The time is returned in milliseconds [ms] and is relative to time 0.</td></tr><tr><td><strong>tsef</strong></td><td>From the ending time of the analysis, course of the generated signal towards the beginning to find the time at which the threshold value is reached based on the type of threshold specified. The time is returned in milliseconds [ms] and is relative to time 0.</td></tr><tr><td><strong>duse</strong></td><td>Difference between tsef and tsed in milliseconds [ms]. This result represents the period of time during which the threshold value is reached.</td></tr><tr><td><strong>Signal_1</strong></td><td>First signal to analyze.</td></tr><tr><td><strong>Signal_2</strong></td><td>Second signal to analyze.</td></tr><tr><td><strong>Signal_3</strong></td><td>Third signal to analyze.</td></tr><tr><td><strong>Signal_Part</strong></td><td><p>Part of the signal on which the analysis is done (neg, pos, sig, abs). Here are the definitions of the four distinct parts of a signal:<br><strong>Neg:</strong> Only the negative values of the input signal are used for the calculations. The other values are considered to be null.<br><img src="https://1028368895-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwfLeQP2Iaoefor0ZUNi%2Fuploads%2F8fansxahLLm3kxEgVLSk%2Fimage.png?alt=media&amp;token=28d9bd72-8f9c-4c37-9e5f-7b72df8983fc" alt=""></p><p><strong>Pos:</strong> Only the positive values of the input signal are used for the calculations. The other values are considered to be null.<br><img src="https://1028368895-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwfLeQP2Iaoefor0ZUNi%2Fuploads%2F6AIIcVDJ1Xi6LSJYo6ld%2Fimage.png?alt=media&amp;token=d65ce3ed-8ce6-4313-8d65-513a36f67c7b" alt=""></p><p><strong>Sig</strong>: The original input signal is used for the calculations.</p><p><img src="https://1028368895-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwfLeQP2Iaoefor0ZUNi%2Fuploads%2FpCREWvs26miAtXnwhrzs%2Fimage.png?alt=media&amp;token=17734aaa-dd02-411f-85d2-bc1df29b7d93" alt="" data-size="original"></p><p><strong>Abs:</strong> The calculations are done on the absolute value of the input signal.<br><img src="https://1028368895-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwfLeQP2Iaoefor0ZUNi%2Fuploads%2FPSwTzLofJ1EHPZvOIwg9%2Fimage.png?alt=media&amp;token=1771a6ee-a7b2-4f76-adff-274da3ddb467" alt=""></p></td></tr><tr><td><strong>Threshold</strong></td><td>Value of threshold to be reached on the specified part of the signal.</td></tr><tr><td><strong>Slope</strong></td><td>Type of threshold to reach: the threshold value can be reached on a rise (m) or a fall (d).<br><strong>Rise(m):</strong> On the resulting signal, the threshold is considered to be reached when the first sample of the analyzed signal exceeds the specified threshold (tsed). From the ending time of the analysis, the threshold is considered to end when the first sample of the analyzed signal exceeds the specified threshold (tsef).<br><strong>Fall(d):</strong> On the resulting signal, the threshold is considered to be reached when the first sample is smaller than the specified threshold (tsed). From the ending time of the analysis, the threshold is considered to end when the first sample of the analyzed signal is smaller than the specified threshold (tsef).</td></tr><tr><td><strong>Begin_time</strong></td><td>Time at which the analysis of a signal must start. This time is expressed in milliseconds [ms]. This value must be greater than 0 and lower than the duration of the test. The default value is 0.</td></tr><tr><td><strong>End_time</strong></td><td>Time at which the analysis of a signal must end. This time is expressed in milliseconds [ms]. The value of this time must be larger than the specified begin_time and smaller than the duration of the test. Use the “HUGE” value to specify the end of the test. The default value is HUGE.</td></tr><tr><td><strong>Factor</strong></td><td>Multiplying factor for the results generated by the function. The default value of the multiplying factor is 1.0 and has no effect on the results. The multiplying factor applies only to the tsed and tsef results.It does not apply to the duse result.</td></tr></tbody></table>

## **SYNTAX**

**\[tsed, tsef, duse]** = sidseuil(sig1, sig2, sig3, "sig", threshold, "m", 0, HUGE, factor)

## **CHARACTERISTICS**

Data type support

Double Floating point

## **EXAMPLE**

The following figures show Sidseuil function examples on Rise and Fall:

| **Sidseuil function on a rise:** | ![](https://opal-rt.atlassian.net/wiki/download/thumbnails/1517191741/hyp54.PNG?version=1\&modificationDate=1757702626887\&cacheVersion=1\&api=v2\&width=561\&height=250) |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Sidseuil function on a fall:** | ![](https://opal-rt.atlassian.net/wiki/download/thumbnails/1517191741/hyp55.PNG?version=1\&modificationDate=1757702626653\&cacheVersion=1\&api=v2\&width=560\&height=250) |

The next figures show the different limit cases of the Sidseuil function:

![](https://content.gitbook.com/content/fwfLeQP2Iaoefor0ZUNi/blobs/FiG31yIiLejAtkps6mgH/hyp56.PNG)


---

# 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-functions/advanced-functions/advanced-or-sidseuil.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.
