# Best Practices

*(timeframes, re-optimisation, common fixes)*

This page gives you ready-to-use setups for common markets/timeframes, a light routine for keeping settings fresh, and a quick fix list when something looks off.

***

### A. Playbooks (copy → tweak → save)

> Start in **Automatic**, confirm the winner on a few symbols, then lock with **Manual** if you want a consistent style.

#### 1) Scalping (1–5 min)

* **Strategy:** *SL/TP (ATR)*
* **Signal Length:** 6–25
* **Stop Loss (×ATR):** 1.0–1.6
* **Risk-Reward:** 1.5–2.0
* **TP count:** 2–3
* **RSI Bias:** 0–5
* **Min candles between signals:** 3–6
* **Notes:** Keep heatmap resolution modest; spreads/fees matter—enter your **Fees %**.

#### 2) Intraday (15–60 min)

* **Strategy:** *SL/TP (ATR)* or *Pure Signals*
* **ATR mode:** L = 10–40, SL = 1.2–2.0, RR = 1.8–3.0, TP = 2–3, RSI Bias = 5–10, Min candles = 6–10
* **Pure mode:** L = 10–60, **Length Smoothness** = 1.5–4.0, **Lengths Ratio** = 2.0–3.0
* **Notes:** Solid balance of trade frequency and quality.

#### 3) Swing (4 h – 1 D)

* **Strategy:** *Pure Signals* (simple flips) or *SL/TP (ATR)* (partial exits)
* **ATR mode:** L = 18–80, SL = 1.5–2.5, RR = 2.0–3.5, TP = 1–2, RSI Bias = 5–12, Min candles = 8–14
* **Pure mode:** L = 20–90, **Length Smoothness** = 2.0–6.0, **Lengths Ratio** = 2.2–3.5
* **Notes:** Fewer, cleaner moves. Prefer **Profit Factor** or **Min Drawdown** as the objective.

#### 4) Market notes

* **Crypto (24/7, volatile):** slightly **higher SL×ATR**, **lower RR**; prefer 2–3 TPs.
* **FX (liquid, lower fees):** **RSI Bias** helps filter chop on lower TFs.
* **Indices (session behavior):** avoid news spikes; use **Min candles** cooling.

***

### B. Best Practices

#### 1) Keep it simple

* Use **Automatic** with *narrow, realistic ranges* first.
* Only widen ranges if the heatmap looks uniformly weak.

#### 2) Size small, scale edge

* Start **Fixed Percent = 1.0–1.5 %** or **Fixed Drawdown goal = 10 %** (cap 3–5 %).
* Enter **Fees %**—results and labels are **fee-aware**.

#### 3) Confirm across contexts

* Validate the chosen combo on **2–3 symbols** and **2–3 timeframes**.
* If results swing wildly, your range or objective may be mismatched.

#### 4) Prefer robustness

* When in doubt, choose **Profit Factor** or **Min Drawdown** over raw profit.
* Use **RSI Bias** and **Min candles between signals** to cut noise.

#### 5) Save your work

* After dialing in: **Template** (TradingView) + screenshot the **Dashboard** and **Heatmap** for your playbook notes.

***

### C. Re-optimisation (light routine)

**When to re-run Automatic:**

* After **volatility/regime shifts** (large new swings or prolonged chop)
* When **switching symbol/timeframe**
* After major **fees** or **risk mode** changes

**5-step refresh (2–5 minutes):**

1. **Set Risk Management** (balance, mode, fees).
2. **Pick objective** (PF or Min DD for stability).
3. **Set ranges** (keep realistic; product of resolutions ≤ **1000**).
4. **Run**, review **Dashboard + Heatmap**.
5. **Lock** promising values in **Manual** if you want consistency.

***

### D. Quick Diagnostics (decision mini-tree)

* **No signals?**\
  → Zoom out / switch to a richer symbol • Lower **RSI Bias** • Reduce **Min candles** • Lower **Signal Length**.
* **Loads forever / empty heatmap?**\
  → Narrow ranges • Lower **Signal Length Resolution** × **Risk Resolution** (product ≤ **1000**).
* **Too many trades / whipsaws?**\
  → Raise **Signal Length** or **Smoothness** • Increase **RSI Bias** • Increase **Min candles**.
* **Great backtest, poor live feel?**\
  → Use **Profit Factor**/**Min Drawdown** • Re-optimise with tighter ranges • Check **Fees %**.
* **P/L labels look “small”?**\
  → Your **risk % / amount** is small or SL distance is wide (ATR mode). Revisit **Risk Management** or SL×ATR.
* **Cluttered chart?**\
  → **Visuals → Tables shown = Only Dashboard** • **Exit Signals = Not Show at all** • Reduce label sizes.

***

### E. Handy settings map (where to click)

* **General Settings →** *Settings Selection*, *Optimize For*, *Trading Strategy*, *Take Profits*
* **Automatic search ranges →** *Signal Length between*, ATR: *Stop Loss between* & *Risk-Reward between*; Pure: *Length Smoothness between*
* **Advanced (filters) →** *RSI Filter Bias*, *Minimum Candles between Signals*, *Trading Preference*
* **Risk Management →** *Mode*, *Account Balance*, *Fees %*
* **Visuals →** *Tables shown*, *Signals*, *LuxRibbon™*

***

### F. Minimal checklists

**Before running Automatic**

* [ ] Risk mode, balance, fees set
* [ ] Ranges realistic to timeframe/market
* [ ] Resolution product ≤ **1000**

**Before saving a template**

* [ ] Dashboard green where it matters (PF/Win/Max DD)
* [ ] Heatmap shows a *cluster* of good neighbors (not a lone outlier)
* [ ] Manual values copied (if locking)

***

### G. Safe defaults (copy/paste mindset)

* **ATR mode:** SL = **1.5 × ATR**, RR = **2.0**, TP = **2–3**, RSI Bias = **5**, Min candles = **6–10**
* **Pure mode:** L = **20–60**, Smoothness = **2.0–4.0**, Lengths Ratio = **\~2.5**
* **Risk:** Fixed Percent = **1.0–1.5 %** (or Drawdown goal **10 %**, cap **3–5 %**)

> Edge grows from **consistency**: same process, small risk, regular re-optimisation, and clean visuals you can stick to.

## Study Error - Calculation timed out

This can rarely happen and is normal when using LuxSignals, as it indicates that it's doing a lot of calculations and sometimes TradingView's server can get overwhelmed with them and temporarily shuts down LuxSignals' loading for safety reasons.

Quick fix: You don't actually have to remove the indicator,  just open the settings and change any setting, then wait, and change it back again. This will cause LuxSignals to re-load again and will likely cause the error to disappear next time. 

<figure><img src="/files/tCKxvixlAZhES1jrkPSk" alt=""><figcaption></figcaption></figure>

## Runtime error - The script takes too long to execute

To fix this, just reduce the resolutions in the **Automatic Settings Selection** section.&#x20;

Try to keep the product of both numbers below 1000, for example a Length Resolution of 20 and a Risk Resolution of 40 will probably load (product is 800, as 20 x 40=800, so below 1000) but if you use resolutions like 50 and 60 it will probably give the error, because 50x60=3000, so way above the recommended 1000-threshold.

<figure><img src="/files/AR7wsLynUah3o8XNNoju" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
If you get an error message that is not listed here, please report it to <info@luxsignals.com>, you will be compensated for it.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://luxsignals.gitbook.io/luxsignals/focus/best-practices.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.