> 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/miscellaneous-functions/misc.-or-clearingtime.md).

# Misc. | CLEARINGTIME

## **CLEARING TIME – \[CLEARINGTIME]**

Outputs the clearing time by computing the difference between a network signal and a state signal related to their respective threshold.

## **CATEGORY**

Miscellaneous

![](https://content.gitbook.com/content/fwfLeQP2Iaoefor0ZUNi/blobs/RaUxyadwUuD2GoIgvN3D/image2018%209%2024_12%2035%2028.png)

## **DESCRIPTION**

Outputs the elapsed time between the two following events. The first event is the first positive slope zero crossings of the network signal before the threshold is reached. The threshold is compared to the Windowed RMS computation. The second event is when the state signal exceeds the threshold. Note that this function uses a windowed RMS computation set to a frequency of 60 Hz. The behavior with a system using a different frequency can be different.

## **RESULT VARIABLES AND PARAMETERS**

<table data-header-hidden><thead><tr><th width="118.79998779296875"></th><th width="361.99993896484375"></th></tr></thead><tbody><tr><td><strong>Result</strong></td><td>Clearing time [s]</td></tr><tr><td><strong>Signal</strong></td><td>Network signal input</td></tr><tr><td><strong>Threshold</strong></td><td>Network signal value threshold (RMS Value)</td></tr><tr><td><strong>State</strong> <strong>Signal</strong></td><td>State signal input</td></tr><tr><td><strong>Threshold</strong></td><td>State signal threshold</td></tr></tbody></table>

## **SYNTAX**

**Clearing\_Time**=clearingtime(Input\_Network,Threshold\_Network,Input\_State,Threshold\_State)

## **CHARACTERISTICS**

Data type support

Double Floating point

## **EXAMPLE**

![](https://content.gitbook.com/content/fwfLeQP2Iaoefor0ZUNi/blobs/z8xRdppFUKtjEP7Yxxw3/image2018%209%2024_12%2046%205.png)

![](https://content.gitbook.com/content/fwfLeQP2Iaoefor0ZUNi/blobs/8ToaTEWfZB80rBsYwZhj/image2018%209%2024_12%2046%2011.png)

![](https://content.gitbook.com/content/fwfLeQP2Iaoefor0ZUNi/blobs/wNJ7wLi8uX8f3wyixdyU/image2018%209%2024_12%2046%2021.png)

![](https://content.gitbook.com/content/fwfLeQP2Iaoefor0ZUNi/blobs/wQya3yqF9UEF2WjmWV4Z/image2018%209%2024_12%2046%2026.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/miscellaneous-functions/misc.-or-clearingtime.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.
