> For the complete documentation index, see [llms.txt](https://docs.motivewave.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motivewave.com/user-guide/sdk-programming-guide/signals.md).

# Signals

All studies and strategies may generate signals. Signals are events that occur at points of interest in a study. Often signals are used as indicators of buy or sell points.

The end user may configure the study to create alerts from the signals generated by the study. To provide a high level of flexibility, the user may choose which signals they want alerts for and how the alerts behave.

The Sample Moving Average Cross (see sample project) is one example of a study that generates signals. This study generates two signals:

* **Fast MA Crossed Above** – This occurs when the Fast MA (shorter period) crosses above the Slow MA
* **Fast MA Crossed Below** – This occurs when the Fast MA crosses below the Slow MA

By default, these signals do not do anything other than show an up or down marker where the crosses occur on the plot. The user can configure alerts for these signals from the ‘Signals’ tab of the Study Dialog.

![Figure 39 - Signals Tab](/files/-M5Sfeq6yFCFJE7i1Gt6)

The following steps are required to generate signals for a study:

* *signal* tag – set the ‘signal’ property in the StudyHeader to true
* declare signals – There are two signals, cross above and cross below.
* call ‘signal’ method – this generates the signals.

![Figure 40 - signal tag (StudyHeader)](/files/-M5Sfeq7GlaCn1xdt9Ub)

![Figure 41 - Generating Signals](/files/-M5Sfeq8OdXp2YDF_s8f)


---

# 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.motivewave.com/user-guide/sdk-programming-guide/signals.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.