From 2f7596aab54252686fabd3743c9f5680a4e9fbb5 Mon Sep 17 00:00:00 2001 From: Trey Spiller Date: Thu, 31 Jul 2025 17:47:28 -0500 Subject: [PATCH] Clarify multiple signals must all be true --- docs/guides/signals.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/guides/signals.md b/docs/guides/signals.md index 36dc25496f..4c678d729b 100644 --- a/docs/guides/signals.md +++ b/docs/guides/signals.md @@ -24,6 +24,10 @@ It then divides those into _batches_ (configured with the model's [batch_size](. Signal checking functions examines a batch of time intervals. The function is always called with a batch of time intervals (DateTimeRanges). It can also optionally be called with key word arguments. It may return `True` if all intervals are ready for evaluation, `False` if no intervals are ready, or the time intervals themselves if only some are ready. A checking function is defined with the `@signal` decorator. +!!! note "One model, multiple signals" + + Multiple signals may be specified for a model. SQLMesh categorizes a candidate interval as ready for evaluation if **all** the signal checking functions determine it is ready. + ## Defining a signal To define a signal, create a `signals` directory in your project folder. Define your signal in a file named `__init__.py` in that directory (you can have additional python file names as well).