> For the complete documentation index, see [llms.txt](https://help.hydravision.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.hydravision.ai/ea-configuration/ea-settings/smartentry/custom-re-entry-configuration.md).

# Custom Re-Entry configuration

When using Custom Signal Confirmation there are additional fine tuning settings that can be made.

{% hint style="warning" %}
Use one of the 3 presets until comfortable with the concepts, before attempting custom configuration.
{% endhint %}

Every re-entry evaluation starts by classifying the grid into a [Risk Zone](/concepts/concepts/zones.md#risk-zones): Green, Yellow, or Red. The zone is set by the grid's size: the distance from the anchor to the furthest rung, measured in steps. Green runs up to "Low Risk = Green zone upper bound" × step (default 5), Yellow up to "Medium Risk = Yellow zone upper bound. Above this - Red" × step (default 10), and Red is beyond that. With only the anchor open, the distance from the anchor to the current price is used. Position count and volume are not part of it.

Each zone has its own timeframe for signal evaluation (M15 for Green, M30 for Yellow and H1 for Red by default). The zone timeframes apply in every mode, not only Custom, and are described on [Re-Entry Signal Confirmation](/ea-configuration/ea-settings/smartentry/re-entry-signal-confirmation.md#settings-used-in-every-mode). In Custom, each zone also has its own score threshold and confirm window. As a grid grows, it escalates through zones automatically; as PCL closes its furthest rungs, it can de-escalate back. The zone only changes when the furthest rung changes, not every time price moves.

When using Custom, we can also apply a weight to each signal. Each signal that has fired within the zone's confirm window adds its weight, and these weights are added together to produce the score. The re-entry opens when the score reaches the zone's threshold. In this way we can apply a signal stacking effect.

<figure><img src="https://2125914855-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZIaLMOKKxe4F4BdXrYzO%2Fuploads%2FNNxM9qsE9OlLjb5HtoCq%2FRisk%20Zones.png?alt=media&amp;token=a721d403-f924-4749-973b-dba485e88837" alt=""><figcaption><p><strong>Demonstration of Risk Zone Setup affecting SmartEntry and PCL Actions. Using a 3 Month Market Regime Window</strong></p></figcaption></figure>

{% stepper %}
{% step %}

### Define Risk Zone bands

Done in an [earlier step](/ea-configuration/ea-settings/grid.md#risk-zone-setup)
{% endstep %}

{% step %}

### Provide entry score for each zone

For example, if using all 3 signals, and each signal is worth 1 point.

Green Zone : 1 point = Any 1 signal must confirm

Yellow Zone : 2 points = Any 2 signals must confirm

Red Zone : 3 points = All 3 signals must confirm

The defaults are 3 points in every zone, so out of the box Custom needs all 3 signals in every zone.
{% endstep %}

{% step %}

### Enable the required signals

Decide which re-entry signals to enable. A weight of 0 disables a signal.
{% endstep %}

{% step %}

### Allocate a score to each signal

Allocate a weight (default is 1). Weights let one signal count for more than another. For example, with Momentum Shift at 2, the others at 1 and a threshold of 2, Momentum Shift alone is enough, or Micro Bounce and Range Breakout together. If the weights of the enabled signals can't add up to a zone's threshold, no re-entry can pass in that zone.
{% endstep %}

{% step %}

### Fine tune enabled signals

Adjust the timeframes of each zone (these also apply to the presets). Higher timeframes are more restrictive.
{% endstep %}

{% step %}

### Configure windows

This is the number of bars (of the zone's timeframe) a signal stays valid after it fires. If this is 10, a signal that fired in the last 10 bars still counts, so the enabled signals only need to agree within 10 bars for the re-entry to be approved. The longer this window the more permissive the entry becomes. 0 = tick, meaning the signals must all be firing at the same moment (the most restrictive).
{% endstep %}
{% endstepper %}

{% hint style="info" %}
With the defaults, the Red Zone has a threshold of 3 and a window of 0, so all three signals must fire on the same tick. That rarely, if ever, happens, so with the Custom defaults expect few or no re-entries in the Red Zone.
{% endhint %}

<details>

<summary>Micro Bounce Weight</summary>

`Integer`

Default: 1

How much Micro Bounce adds to the score when it has fired within the window. 0 = disabled.

For custom use only. The presets set every weight to 1.

</details>

<details>

<summary>Momentum Shift Weight</summary>

`Integer`

Default: 1

How much Momentum Shift adds to the score when it has fired within the window. 0 = disabled.

For custom use only. The presets set every weight to 1.

</details>

<details>

<summary>Range Breakout Weight</summary>

`Integer`

Default: 1

How much Range Breakout adds to the score when it has fired within the window. 0 = disabled.

For custom use only. The presets set every weight to 1.

</details>

<details>

<summary>Green Zone Signal Threshold</summary>

`Integer`

Default: 3

The required signal confirmation score to generate a re-entry signal.

For custom use only.

</details>

<details>

<summary>Yellow Zone Signal Threshold</summary>

`Integer`

Default: 3

The required signal confirmation score to generate a re-entry signal.

For custom use only.

</details>

<details>

<summary>Red Zone Signal Threshold</summary>

`Integer`

Default: 3

The required signal confirmation score to generate a re-entry signal.

For custom use only.

</details>

<details>

<summary>Green Zone Timeframe</summary>

Default: M15

The timeframe to be used by the signals when the grid is in the Green Zone. A lower timeframe is more permissive.

Applies in every mode, not only Custom.

</details>

<details>

<summary>Yellow Zone Timeframe</summary>

Default: M30

The timeframe to be used by the signals when the grid is in the Yellow Zone. A lower timeframe is more permissive.

Applies in every mode, not only Custom.

</details>

<details>

<summary>Red Zone Timeframe</summary>

Default: H1

The timeframe to be used by the signals when the grid is in the Red Zone. A lower timeframe is more permissive.

Applies in every mode, not only Custom.

</details>

<details>

<summary>Green Confirm Window (bars, 0=tick)</summary>

`Integer`

Default: 10

When applying signal stacking we have an option to increase the time period of the co-occurrence of the signals (the Window). Therefore more bars in the Window give us a longer timeframe for two or more signals to agree with each other.

For custom use only. 0 = tick

</details>

<details>

<summary>Yellow Confirm Window (bars, 0=tick)</summary>

`Integer`

Default: 5

When applying signal stacking we have an option to increase the time period of the co-occurrence of the signals (the Window). Therefore more bars in the Window give us a longer timeframe for two or more signals to agree with each other.

For custom use only. 0 = tick

</details>

<details>

<summary>Red Confirm Window (bars, 0=tick)</summary>

`Integer`

Default: 0

When applying signal stacking we have an option to increase the time period of the co-occurrence of the signals (the Window). Therefore more bars in the Window give us a longer timeframe for two or more signals to agree with each other.

For custom use only. 0 = tick

</details>