> For the complete documentation index, see [llms.txt](https://docs.algopro.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.algopro.us/tradingview-indicators/v1.7.md).
# V1.7
## AlgoPro V1.7 User Guide
> Complete setup, optimization, trade-management, dashboard, and alerts guide for AlgoPro V1.7.
AlgoPro V1.7 is an adaptive TradingView indicator that self optimizes directly on any symbol or timeframe. It supports two entry engines, four trading styles, four optimization goals, staged ATR take profits, an optional invalidation-zone exit, performance reporting, and chart alerts.
The indicator has two distinct jobs:
1. **Auto Optimize** searches for signal settings that performed best under the selected rules.
2. **Manual (Fixed)** locks a chosen Sensitivity and Tuning value so the signal behavior remains fixed.
> **Important:** AlgoPro is an indicator and research tool. Its dashboard is a built-in simulation, not a broker statement or TradingView Strategy Tester report. It does not place orders, or guarantee future results.
***
### What's included in V1.7
* Selectable V1.2 and V1.4 entry systems
* Auto Optimize and Manual Fixed entry modes
* 400-candidate, style-aware signal optimization
* Normalized multi-metric optimization goals
* User-controlled six-level ATR take-profit management
* A single next-target gradient line and percentage label
* Optional invalidation-zone exits in optimizer and Manual reporting
* A streamlined two-column performance dashboard
* Bull/Bear Strength, signal coloring, and six alert conditions
***
### Quick start
For a first run:
1. Add **AlgoPro V1.7** to a chart.
2. Set **Entry Mode** to `Auto Optimize`.
3. Choose either the `V1.2` or `V1.4` Entry System.
4. Choose the Trading Style that matches the holding period you want.
5. Leave **Bars To Evaluate** at `5000` while testing.
6. Leave **Optimize For** at `Net Profit + Profit Factor` for a balanced starting point.
7. Configure Smart Take Profit and the Invalidation Zone under **Trade Management**.
8. Wait for the dashboard to show `OPTIMIZING • N QUALIFIED`.
9. Review the current winning Sensitivity and Tuning values.
10. To lock those settings, copy them into **Manual Fixed Settings**, keep the same Entry System and trade-management settings, and change Entry Mode to `Manual (Fixed)`.
#### Recommended first-run defaults
| Setting | Starting value |
| --------------------------------- | -------------------------- |
| Entry Mode | Auto Optimize |
| Entry System | V1.2 |
| Trading Style | Day Trading |
| Optimize For | Net Profit + Profit Factor |
| Use Heikin Ashi Calculations | On |
| Bars To Evaluate | 5,000 |
| Minimum Trades Before Ranking | 5 |
| Smart Take Profit | On |
| TP Sensitivity | 2.0 |
| Position Closed Per TP | 20% |
| Invalidation Zone | On |
| Include Zone Hits In Optimization | Off initially |
These are starting points, not universal best settings. The purpose of Auto Optimize is to adapt the entry settings to the chart being used.
***
### How AlgoPro is organized
| Component | Purpose |
| ------------------ | ----------------------------------------------------------------------------------- |
| Entry System | Chooses the V1.2 or V1.4 signal engine. |
| Entry Mode | Chooses adaptive optimization or fixed manual settings. |
| Trading Style | Defines the search range, required number of trades, and acceptable holding period. |
| Optimize For | Ranks qualified signal candidates. |
| Smart Take Profit | Simulates staged exits at six ATR-based targets. |
| Invalidation Zone | Displays a trend-dependent risk zone and can optionally close simulated trades. |
| Dashboard | Shows the active setup and its simulated performance. |
| Bull/Bear Strength | Shows a separate Gaussian trend-strength reading. |
| Alerts | Provides entry, take-profit, and invalidation alert conditions. |
The optimizer changes **entry Sensitivity and Tuning only**. It does not search for TP Sensitivity, TP close percentage, or Invalidation Sensitivity. Every candidate is tested with the trade-management values currently entered by the user.
***
### Entry modes
#### Auto Optimize
Auto Optimize runs a 20-by-20 parameter grid for the selected Entry System:
* 400 total candidates
Each candidate generates and simulates its own trades over the selected evaluation window. Candidates must pass both the minimum-trade rule and the selected Trading Style's holding-period rule before they can be ranked.
On every confirmed bar, the best currently qualified candidate becomes the **current winner**. Its parameters drive the live Buy/Sell signal stream shown on the chart.
Because the winner can change as new data arrives, Auto Optimize is adaptive. Historical Auto signals can also change when the script is recalculated, the evaluation window rolls forward, or the winning candidate changes.
Use Auto Optimize for:
* discovering settings for a symbol and timeframe;
* comparing V1.2 with V1.4;
* evaluating different optimization goals;
* adapting to changing market behavior;
* research and periodic re-optimization.
#### Manual (Fixed)
Manual mode stops the 400-candidate ranking process and uses the Sensitivity and Tuning entered under **Manual Fixed Settings**.
Use Manual mode for:
* locking a setup found in Auto Optimize;
* keeping alerts stable;
* comparing the same settings across charts;
* avoiding ongoing changes in the adaptive winner;
* reducing calculation load after research is complete.
The dashboard displays `SETTINGS LOCKED • FIXED`, and **Optimize For** displays `NOT RUNNING` because there is no candidate ranking in Manual mode.
#### How to copy an Auto winner into Manual mode
1. Note the dashboard's **Signal Sensitivity** and **Signal Tuning**.
2. Open the indicator settings.
3. Enter those exact values under **Manual Fixed Settings**.
4. Keep the same Entry System.
5. Keep the same Heikin Ashi, TP, invalidation, and evaluation-window settings.
6. Change Entry Mode to `Manual (Fixed)`.
> **Why the chart can still look different:** Auto mode's displayed signal stream is adaptive and may have used different winners at different historical points. The Auto performance panel, however, reports the current winning candidate's own fixed-parameter simulation. The Auto and Manual dashboard results are designed to closely match when that exact winner and every related input are copied at the same chart state. A material dashboard difference usually means an input differs, the Auto winner changed before it was locked, or the evaluation window moved.
***
### Entry systems
AlgoPro V1.7 includes two selectable signal engines. The selected engine controls chart signals, optimizer candidates, dashboard reporting, TP direction, invalidation direction, and Buy/Sell alerts.
#### V1.2 Engine
V1.2 is the original AlgoPro entry system. It's goal is to avoid lag and choppy markets.
In general, larger Tuning values react more slowly, and larger Sensitivity values create wider thresholds. Either change will usually reduce signal frequency, although the exact result depends on the chart.
#### V1.4 Engine
V1.4 is another popular entry system that looks for more frequent signals.
V1.4 often behaves like a thresholded trend filter: a wider range can ignore more small price movement, while a shorter period can react more quickly.
#### Shared Sensitivity and Tuning controls
Both systems use settings named **Sensitivity** and **Tuning**, but those values feed different mathematics. A Sensitivity of `2.0` in V1.2 is not equivalent to a Sensitivity of `2.0` in V1.4.
When switching Entry Systems:
* Auto Optimize searches the new system's own parameter grid.
* Manual mode applies the entered values to the newly selected system.
* Existing alerts should be recreated after the switch.
***
### Trading styles
Trading Style is more than a label. It changes three parts of optimization:
1. the Sensitivity and Tuning values tested;
2. the acceptable average holding-period range;
3. the required minimum number of completed trades.
The style does **not** directly force a specific number of signals. A candidate is eligible only when its actual simulated behavior fits the style.
#### Holding-period rules
| Style | Minimum average hold | Target average hold | Maximum average hold |
| ------------- | -------------------- | ------------------- | -------------------- |
| Scalping | 10 minutes | 30 minutes | 2 hours |
| Day Trading | 1 hour | 4 hours | 12 hours |
| Swing Trading | 12 hours | 3 days | 10 days |
| Investing | 10 days | 60 days | 250 days |
Holding duration is measured in real elapsed time, not simply in a fixed number of candles. Partial TP exits are included using capital-weighted holding time. For example, closing part of a position early lowers the position's average capital-weighted hold duration.
If two candidates receive the same optimization score, the one with average holding time closer to the style's target is preferred.
#### Practical timeframe guidance
The indicator does not restrict which style can be used on which timeframe, but the timeframe must make the style's holding window achievable. These are practical starting points, not enforced rules:
| Style | Practical chart timeframes |
| ------------- | -------------------------- |
| Scalping | 1-minute to 15-minute |
| Day Trading | 5-minute to 1-hour |
| Swing Trading | 1-hour to daily |
| Investing | 4-hour to weekly |
Using Scalping on a four-hour chart, for example, makes a 10-minute to two-hour average hold effectively impossible. That will commonly produce `NO STYLE MATCH`.
#### V1.2 search ranges
| Style | Tuning values | Sensitivity values |
| ------------- | ------------------ | -------------------------- |
| Scalping | 5 to 43, step 2 | 0.500 to 1.925, step 0.075 |
| Day Trading | 15 to 72, step 3 | 0.750 to 2.650, step 0.100 |
| Swing Trading | 35 to 130, step 5 | 1.250 to 4.100, step 0.150 |
| Investing | 80 to 270, step 10 | 2.000 to 5.800, step 0.200 |
#### V1.4 search ranges
| Style | Tuning values | Sensitivity values |
| ------------- | ------------------ | ----------------------- |
| Scalping | 5 to 24, step 1 | 1.00 to 5.75, step 0.25 |
| Day Trading | 10 to 48, step 2 | 1.25 to 6.00, step 0.25 |
| Swing Trading | 20 to 96, step 4 | 1.50 to 6.25, step 0.25 |
| Investing | 40 to 230, step 10 | 2.00 to 6.75, step 0.25 |
Each row still contains 20 Tuning values and 20 Sensitivity values, for 400 combinations.
#### Style-adjusted minimum trades
The **Minimum Trades Before Ranking** input is a floor. AlgoPro may raise it according to the style and Bars To Evaluate setting.
The effective minimum is the greater of the user input and the style minimum below:
| Style | Style minimum formula | At 5,000 bars | At 20,000 bars |
| ------------- | ---------------------------------------- | ------------- | -------------- |
| Scalping | Greater of 15 or Bars ÷ 125, rounded up | 40 | 160 |
| Day Trading | Greater of 10 or Bars ÷ 250, rounded up | 20 | 80 |
| Swing Trading | Greater of 6 or Bars ÷ 500, rounded up | 10 | 40 |
| Investing | Greater of 3 or Bars ÷ 1,000, rounded up | 5 | 20 |
This scaling helps prevent a very active style from winning a long evaluation window on only a handful of completed trades.
***
### Auto Optimizer
#### What the optimizer tests
For each of the 400 candidates, AlgoPro independently tracks:
* signal direction and reversals;
* next-bar-open entries;
* the six user-defined Smart TP levels;
* the percentage remaining after each TP;
* optional invalidation-zone exits;
* completed trade count and win count;
* compounded equity and net profit;
* gross profits and losses;
* maximum drawdown;
* average win versus average loss;
* capital-weighted holding duration.
All candidates use the same current symbol, timeframe, Heikin Ashi choice, evaluation window, TP settings, and invalidation settings. Only signal Sensitivity and Tuning vary.
#### Candidate qualification
A candidate can rank only if both conditions are true:
1. It has at least the effective minimum number of completed trades.
2. Its capital-weighted average holding duration falls inside the selected Trading Style's range.
Candidates that have enough trades but do not fit the holding-period range are counted as **Ready**, not **Qualified**.
#### Optimization goals
| Optimize For | Ranking behavior | Best use |
| ---------------------------- | ---------------------------------------------------------------------------------------- | ------------------------------------------- |
| Net Profit | Ranks candidates by net profit only. | Aggressive return-first research. |
| Net Profit + Profit Factor | 50% normalized net profit and 50% normalized profit factor. | Balanced profitability and loss efficiency. |
| Net Profit + Lowest Drawdown | 50% normalized net profit and 50% normalized drawdown quality. Lower drawdown is better. | Return with stronger downside control. |
| Net Profit + Win Rate | 50% normalized net profit and 50% normalized win rate. | Return balanced with trade consistency. |
For combined goals, the relevant metrics are normalized from `0` to `1` across the candidates that are qualified on the current confirmed bar. This makes the two selected metrics comparable even though they use different units. If every qualified candidate has the same value for a metric, that metric receives a neutral normalized value of `0.5` for all of them.
Example: a net profit of 30% and a Profit Factor of 2.0 are not added directly. AlgoPro first determines where each value sits between the current qualified minimum and maximum, and then weights those normalized positions equally.
> **Lowest Drawdown does not mean drawdown is ignored until it reaches a threshold.** It continuously rewards the candidate with the smaller absolute peak-to-trough decline relative to the other qualified candidates.
#### Why different goals can select the same settings
This is not automatically an error. It can happen when:
* only one candidate is qualified;
* one candidate leads on several metrics at once;
* many parameter combinations generate the same trades;
* net profit differences dominate the candidate set;
* the secondary metrics are identical or nearly identical;
* rounding makes different underlying results appear the same on the dashboard.
The dashboard's `N QUALIFIED` value is the first item to check. If it shows `1 QUALIFIED`, every optimization goal must select the same candidate.
#### Evaluation window
**Bars To Evaluate** controls how many recent chart bars are used for the optimizer and Manual performance report.
* Minimum: 1,000 bars
* Default: 5,000 bars
* Maximum: 20,000 bars
* Step: 500 bars
A larger window provides more history and usually more completed trades, but it also increases calculation time. The script evaluates up to 400 candidates across that window, so doubling the number of bars roughly doubles the main simulation workload.
TradingView's total script-execution allowance can be reached on demanding combinations of symbol, timeframe, history, and Entry System. TradingView currently documents a 20-second allowance for Basic accounts and 40 seconds for other account types. The `20,000` maximum is an available AlgoPro input, not a promise that every chart will finish within the platform limit. See TradingView's official [Pine Script limitations](https://www.tradingview.com/pine-script-docs/writing/limitations/).
For efficient testing:
1. Start at 5,000 bars.
2. Confirm that a reasonable number of candidates qualify.
3. Increase to 7,500 or 10,000 only when more history is needed.
4. Use Manual mode after selecting settings.
5. Avoid changing several heavy inputs at once while diagnosing a timeout.
***
### Signal and execution model
Understanding the timing model is essential when reading the dashboard.
#### Signal timing
* Buy and Sell entries are confirmed at candle close.
* Signals alternate between bullish and bearish states.
* The signal label appears on the confirmed signal candle.
* The performance simulation queues that signal and enters or reverses at the **next candle's open**.
This avoids assuming that a trade could be entered at a closing price before the signal was known.
#### Reversals
An opposite signal:
1. closes 100% of the position still open;
2. completes the current directional trade;
3. opens the new opposite-direction trade at the next bar open.
If one or more take profits already fired, the reversal closes only the fraction that remains. For example, if one 20% TP fired, the opposite signal closes the remaining 80%.
#### Intrabar TP and invalidation touches
TP and invalidation events use the candle's high and low. When one candle crosses several consecutive TP levels, all crossed targets are processed in order.
If a candle touches both the active invalidation center and a TP target, the invalidation event is processed first. This conservative rule avoids overstating performance when the true intrabar path is unknown.
#### No commission or slippage
Dashboard performance does not deduct:
* brokerage commission;
* exchange fees;
* spread;
* slippage;
* funding or borrowing costs;
* taxes.
Real-world results will therefore differ, especially on lower timeframes or less-liquid markets.
***
### Smart Take Profit system
Smart Take Profit is a six-stage ATR target system. It affects both the chart visuals and the optimizer/Manual performance report.
#### TP Sensitivity
TP Sensitivity controls target spacing. The ATR length is 14, and targets are anchored to the signal candle's closing price.
Let:
`TP step = ATR(14) × TP Sensitivity`
The six targets are:
| Target | Distance from signal close |
| ------ | -------------------------- |
| TP1 | 1 × TP step |
| TP2 | 3 × TP step |
| TP3 | 5 × TP step |
| TP4 | 7 × TP step |
| TP5 | 9 × TP step |
| TP6 | 11 × TP step |
Long targets are above the signal price. Short targets are below it.
Higher TP Sensitivity places targets farther away. Lower TP Sensitivity places them closer. TP Sensitivity is entered by the user and is **not optimized**.
#### Position Closed Per TP
Each TP closes the configured percentage of the position that is **still open**, not the same percentage of the original position.
With a 20% setting:
| Event | Closed at event | Total closed | Remaining |
| ----- | --------------- | ------------ | --------- |
| Entry | 0% | 0% | 100% |
| TP1 | 20.000% | 20.000% | 80.000% |
| TP2 | 16.000% | 36.000% | 64.000% |
| TP3 | 12.800% | 48.800% | 51.200% |
| TP4 | 10.240% | 59.040% | 40.960% |
| TP5 | 8.192% | 67.232% | 32.768% |
| TP6 | 6.554% | 73.786% | 26.214% |
If an opposite signal arrives after TP1, it closes the remaining 80%. If it arrives after TP3, it closes the remaining 51.2%.
The remaining fraction after `n` targets is:
`Remaining = (1 − TP percentage)ⁿ`
#### What appears on the chart
* A white checkmark appears when each TP is hit.
* Only the **next unhit target** is displayed as a colored gradient-dotted line.
* Its label reads `TP N (X%)`, such as `TP 1 (20%)`.
* When the target is hit, its line and label are replaced by the next target.
* All six target lines are never displayed at the same time.
* The sequence clears after TP6 or resets on an opposite signal.
* An invalidation-zone touch does not clear the technical TP sequence.
The visual target tracker and the performance position tracker are deliberately separate. If an included invalidation event closes the simulated position, the next-TP visual may remain until an opposite signal or TP6. Similarly, setting Position Closed Per TP to 100% removes all simulated exposure at TP1, while the technical checkmark sequence can continue to show later target achievements.
#### Why changing the TP percentage may not visibly change stats
Common reasons include:
* no TP was reached before the opposite signal;
* only a very small fraction of total return changed;
* dashboard rounding hides the difference;
* the same candidate remains best even though its exact result changed;
* most of the position was ultimately closed at a similar reversal price;
* the changed TP setting altered all candidates similarly.
A move from 20% to 10% can create a modest difference. A move to 100% is much more likely to be obvious because TP1 removes all remaining exposure.
#### Disabling Smart Take Profit
When **Enable Smart Take Profit** is off:
* no TP partial exits are applied in performance;
* TP checkmarks and the next-target line are disabled;
* positions remain open until an opposite signal or an included invalidation-zone exit;
* the dashboard shows TP Sensitivity as `OFF`.
***
### Invalidation Zone
The Invalidation Zone is a trend-dependent VIDYA/ATR risk area. It selects the side of the underlying VIDYA structure that challenges the current signal:
* after a Buy signal, the active zone is the lower zone;
* after a Sell signal, the active zone is the upper zone.
Both V1.2 and V1.4 route their final selected Buy/Sell signals into the same trend-state variable, so the active zone resets from the entry system actually running.
#### How the zone is calculated
The center is based on:
* a Variable Index Dynamic Average using a 10-period base and 20-period momentum measurement;
* additional 15-period smoothing;
* ATR(200) multiplied by Invalidation Sensitivity.
Conceptually:
* Long center = smoothed VIDYA − ATR(200) × sensitivity
* Short center = smoothed VIDYA + ATR(200) × sensitivity
Increasing Invalidation Sensitivity moves the zone farther from its center trend calculation. Decreasing it brings the zone closer.
Here, **upper** and **lower** mean above or below the VIDYA value. The current V1.7 calculation does not clamp the zone to the current market price. During a fast move, a sell-side upper VIDYA band can therefore appear below the current candle, or a buy-side lower band can appear above it. That is a consequence of the lagging VIDYA structure, not a switch to the opposite signal state.
#### Visual behavior
* A new Buy selects the lower zone.
* A new Sell selects the upper zone.
* The zone intentionally disappears on the exact direction-change candle while its new trend state resets.
* It reappears on the following bar when sufficient values are available.
* Hitting the zone does not remove it from the chart.
* It remains associated with the current signal direction until an opposite signal changes that direction.
#### Include Zone Hits In Optimization
This switch determines whether zone interactions affect optimizer and Manual performance.
When off:
* the zone remains visible;
* invalidation alerts can still fire;
* zone touches do not close simulated positions;
* zone touches do not affect ranking or dashboard metrics.
When on:
* trading through the active zone center closes 100% of the simulated position still open;
* the completed trade is added to trade count;
* the result affects net profit, drawdown, Profit Factor, win rate, and average win/loss;
* all 400 candidates use the same user-entered Invalidation Sensitivity;
* Invalidation Sensitivity itself is not optimized.
If price gaps beyond the zone, the model uses the worse price between the bar open and the zone center for the simulated exit. This avoids granting an unrealistically favorable fill through a gap.
> **Important:** Enable Invalidation Zone must also be on for `Include Zone Hits In Optimization` to have an effect.
#### Delta Volume label
The zone label includes a Delta Volume reading from the visual invalidation module. It provides context for buying versus selling volume accumulated by that module. It is not an optimizer score and is not used by the four Optimize For methods.
***
### Heikin Ashi calculations
When **Use Heikin Ashi Calculations** is enabled, AlgoPro requests Heikin Ashi values for the current symbol and chart timeframe and uses them as the smoothed source for the entry engines.
Potential effects include:
* less reaction to isolated candle noise;
* smoother trend changes;
* fewer or later entry transitions;
* different winning Sensitivity and Tuning settings.
The option does not require changing the visible chart to Heikin Ashi. Signals can be calculated from Heikin Ashi data while displayed on standard candles.
Execution-level modeling still uses real chart prices in important places, including next-bar opens, TP/zone touch tests, and ATR-based trade-management calculations. Treat Heikin Ashi as an entry-source smoothing option, not as a claim that every simulated fill occurs at a synthetic Heikin Ashi price.
When comparing Auto and Manual results, keep this switch unchanged.
***
### Dashboard guide
The dashboard is a two-column summary of the active setup. It can be shown or hidden and placed in any supported chart corner.
#### Status section
| Dashboard field | Meaning |
| --------------- | ----------------------------------------------------------------- |
| ALGOPRO / V1.7 | Indicator and version. |
| Status | Current optimizer or Manual state. |
| Active Settings | Whether values are the current winner, still searching, or fixed. |
#### Status messages
| Status | Meaning | What to do |
| -------------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| `LEARNING • 400 TESTS` | No candidate has reached the effective minimum completed-trade requirement yet. | Add history, reduce the lookback cautiously, use a more active style/timeframe, or wait for more completed cycles. |
| `NO STYLE MATCH • N READY` | `N` candidates have enough completed trades, but none has an average hold inside the selected style window. | Choose a style compatible with the chart timeframe or use another timeframe/Entry System. |
| `OPTIMIZING • N QUALIFIED` | `N` candidates meet both trade-count and holding-period rules. The current winner is active. | Review the selected result and winning settings. |
| `SETTINGS LOCKED • FIXED` | Manual mode is active. | The entered Manual values are controlling signals. |
`READY` does not mean qualified. It means trade-count ready. `QUALIFIED` means ready **and** style matched.
#### Active settings section
| Field | Meaning |
| ------------------ | ----------------------------------------------------- |
| Trading Style | Current style and its qualification rules. |
| Entry Mode | Selected system plus Auto Optimize or Manual Fixed. |
| Chart Signal | Current Bullish, Bearish, or Neutral state. |
| Signal Sensitivity | Winning Auto value or entered Manual value. |
| Signal Tuning | Winning Auto value or entered Manual value. |
| TP Sensitivity | User-entered ATR target spacing, or `OFF`. |
| Optimize For | Active ranking goal, or `NOT RUNNING` in Manual mode. |
#### Performance section
| Field | Definition |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Net Profit | Compounded marked-to-market change from a starting equity value of 1.0 over the evaluation window. An open position is included at the current selected close. |
| Max Drawdown | Largest peak-to-trough decline in marked equity during the evaluation window. |
| Profit Factor | Gross positive completed-trade returns divided by absolute gross negative completed-trade returns, capped at 5.0. |
| Avg Win / Loss | Average completed winning return divided by average completed losing return. `2.00 : 1` means the average win is twice the average loss. |
| Win Rate | Winning completed trades divided by total completed trades. |
| Trade Count | Number of completed directional trades, not the number of signal labels or TP checkmarks. |
#### What Auto and Manual performance represent
* In Auto mode, the dashboard shows the **current winning candidate's own simulated result**.
* In Manual mode, it shows the fixed Manual settings' result under the same evaluation and trade-management model.
* An open trade affects current net profit and drawdown but is not added to trade count until the directional trade is completed.
* TP partial exits contribute to the final trade result but are not counted as separate trades.
* An included invalidation exit completes a trade and increments trade count.
Avg Win / Loss is a **realized payoff ratio** from completed simulated trades. It is not a planned target-to-stop Risk/Reward ratio.
#### Profit Factor edge cases
* If there are profits and no losses, Profit Factor displays the capped value of `5.00`.
* If there are neither profits nor losses, it is `0.00`.
* If there are no completed wins or no completed losses, Avg Win / Loss displays a dash because the ratio cannot be calculated.
***
### Bull/Bear Strength meter
Bull/Bear Strength is a separate market-structure display. It is not the optimizer's confidence score and is not used to choose the winning candidate.
The meter calculates 21 Gaussian-smoothed price curves with lengths from 20 through 40. The length-20 curve is the reference. For each of the 20 longer curves:
* if the longer curve is above the reference, Bear Strength gains 5%;
* otherwise, that 5% remains with Bull Strength.
Therefore:
* the readings move in 5% increments;
* Bull Strength plus Bear Strength always equals 100%;
* 16 of 20 longer curves above the reference produces 80% Bear and 20% Bull.
The percentage uses regular chart close data and is independent of:
* V1.2 versus V1.4 optimizer scoring;
* Net Profit, Profit Factor, drawdown, or win rate;
* Smart TP settings;
* invalidation-zone settings;
* Delta Volume;
* RSI or ADX.
The meter can update while the current candle is open. Treat it as contextual trend information, not a confirmed entry signal.
***
### Display settings
| Setting | Function |
| ------------------------- | ------------------------------------------------------------------------------ |
| Bullish Color | Sets the bullish signal, target, meter, and dashboard accent color where used. |
| Bearish Color | Sets the bearish signal, target, meter, and dashboard accent color where used. |
| Show Buy/Sell Labels | Shows or hides the Buy and Sell text labels. |
| Show Buy/Sell Circles | Shows or hides the layered gradient circles at entry signals. |
| Show Smart Bar Coloring | Enables or disables AlgoPro candle coloring. |
| Show Dashboard | Shows or hides the V1.7 dashboard. |
| Dashboard Position | Middle Right, Bottom Left, Bottom Right, Top Left, or Top Right. |
| Dashboard Text Size | Tiny, Small, Normal, Large, or Huge. |
| Show Trend Strength Meter | Shows or hides Bull/Bear Strength. |
Hiding labels or circles changes only the display. It does not disable the underlying signal or its alerts.
***
### Alerts
AlgoPro V1.7 provides six alert conditions:
| Alert condition | Trigger |
| ---------------------------- | -------------------------------------------------------------------- |
| Buy Entry Alert | Confirmed Buy signal from the selected Entry System and Entry Mode. |
| Sell Entry Alert | Confirmed Sell signal from the selected Entry System and Entry Mode. |
| Buy Take Profit Alert | Any long TP level is hit. |
| Sell Take Profit Alert | Any short TP level is hit. |
| Buy Invalidation Zone Alert | Price interacts with the active long invalidation center. |
| Sell Invalidation Zone Alert | Price interacts with the active short invalidation center. |
#### Creating an alert
1. Configure AlgoPro exactly as desired.
2. Select **Create Alert** in TradingView.
3. Choose AlgoPro V1.7 in the Condition menu.
4. Select one of the six alert conditions.
5. Set the desired frequency and notification method.
6. Create separate alerts for each condition you want to receive.
Recommended frequency:
* Entry alerts: **Once Per Bar Close**, because entries are confirmed-bar signals.
* TP and invalidation alerts: **Once Per Bar** for faster intrabar notification, or **Once Per Bar Close** for more conservative confirmation.
All entry alerts follow whichever Entry System and Entry Mode are active when the alert is created. The TP and invalidation alerts then follow the states created by those selected signals.
The TP and invalidation feature switches control their chart drawings and performance behavior, but their underlying alert conditions remain available. If you disable one of those features, do not create that alert type, and delete any existing alert for it if you no longer want notifications.
TradingView alerts run on TradingView's servers using a saved snapshot of the script, inputs, symbol, and timeframe. Changing indicator settings later does not update an already-running alert. Delete and recreate alerts after changing Entry System, Entry Mode, Manual settings, TP settings, invalidation settings, symbol, or timeframe. See TradingView's official [Alerts documentation](https://www.tradingview.com/pine-script-docs/concepts/alerts/).
***
### Recommended workflows
#### Workflow 1 — Find and lock settings
1. Select a symbol and timeframe.
2. Choose the Entry System and Trading Style.
3. Start with 5,000 bars and Net Profit + Profit Factor.
4. Wait for multiple qualified candidates where possible.
5. Record the winning Sensitivity, Tuning, and performance.
6. Test a neighboring timeframe or a second evaluation-window length.
7. Copy the selected values into Manual Fixed Settings.
8. Switch to Manual mode.
9. Recreate any alerts from the locked configuration.
#### Workflow 2 — Favor downside control
1. Choose `Net Profit + Lowest Drawdown`.
2. Keep the same lookback and trade-management settings used in the comparison.
3. Confirm that more than one candidate is qualified.
4. Compare net profit, maximum drawdown, Profit Factor, and trade count together.
5. Prefer a setting that remains acceptable across more than one nearby lookback rather than relying on a single best reading.
#### Workflow 3 — Include invalidation risk
1. Enable the Invalidation Zone.
2. Set an Invalidation Sensitivity suitable for the chart's volatility.
3. Turn on `Include Zone Hits In Optimization`.
4. Allow the optimizer to recalculate.
5. Confirm how trade count, drawdown, and average win/loss change.
The optimizer does not search Invalidation Sensitivity, so repeat this comparison manually if you want to study different zone distances.
#### Workflow 4 — Compare V1.2 and V1.4 fairly
Keep these items unchanged:
* symbol and timeframe;
* Trading Style;
* Optimize For method;
* Heikin Ashi choice;
* Bars To Evaluate;
* minimum-trade input;
* TP Sensitivity and close percentage;
* invalidation settings.
Then switch Entry System and let each system fully recalculate. Compare not only net profit, but also candidate qualification, trade count, drawdown, Profit Factor, and signal character.
***
### Troubleshooting and FAQ
#### What does `LEARNING • 400 TESTS` mean?
All 400 candidates are being evaluated, but none has yet completed the effective minimum number of trades. The style-adjusted minimum may be higher than the visible Minimum Trades input.
#### What does `NO STYLE MATCH • 801 READY` mean?
In V1.7 the active search contains 400 candidates, so the Ready count should relate to that candidate set. Conceptually, `N READY` means candidates have enough completed trades but none has an average holding duration inside the selected style window. If a displayed count exceeds the expected candidate count, make sure the current V1.7 script is loaded and allow a full recalculation.
#### Why does Scalping not look like scalping?
The style qualifies candidates by real average hold duration. It cannot make a high-timeframe chart behave like a low-timeframe scalper. Use a timeframe on which a 10-minute to two-hour average hold is possible, and confirm that the dashboard reaches `QUALIFIED` rather than only `READY`.
#### Why do all Optimize For methods show the same result?
Check the qualified count first. With one qualified candidate, every goal must select it. With several candidates, the same winner can still lead on multiple metrics or share identical trades with nearby settings.
#### Why does optimization time out above 10,000-20,000 bars?
The main workload is approximately 400 candidates multiplied by the number of evaluated bars, plus indicator and display calculations. TradingView currently allows 20 seconds of total execution for Basic accounts and 40 seconds for other account types. Use 5,000 bars for exploration, increase gradually, and switch to Manual after selecting settings. See the official [Pine Script limitations](https://www.tradingview.com/pine-script-docs/writing/limitations/). Test to find out what the limit is for your account.
#### Why does Manual performance differ after copying the Auto values?
Verify all of the following:
* Entry System;
* exact Sensitivity and Tuning values;
* Heikin Ashi selection;
* TP enabled state, TP Sensitivity, and TP close percentage;
* invalidation enabled state, sensitivity, and inclusion switch;
* Bars To Evaluate;
* chart symbol and timeframe.
The dashboard models are intended to be directly comparable. Auto chart labels can adapt as the winner changes, but that does not explain a large mismatch between the current winner's Auto performance and an exactly copied Manual report. If all settings match, allow a full recalculation and confirm that the winner did not change while it was being copied.
#### Is trade count Buy-to-Sell and Sell-to-Buy?
Yes. A completed long cycle normally runs from Buy entry to Sell reversal, and a completed short cycle runs from Sell entry to Buy reversal. If zone hits are included, an invalidation exit can complete the trade earlier. TP checkmarks do not count as separate trades.
#### Does one 20% TP mean the opposite signal closes 80%?
Yes. Each TP closes its percentage of what is open at that moment. After one 20% TP, 80% remains for the opposite signal or invalidation exit.
#### Why did changing TP close percentage not change performance?
The trade may not have reached a TP, the effect may be hidden by display rounding, or the winner may not change even though underlying returns did. Larger percentage changes are more visible because they change more of the trade's remaining exposure.
#### Is TP Sensitivity optimized?
No. Auto Optimize searches signal Sensitivity and Tuning only. TP Sensitivity and Position Closed Per TP are used exactly as entered for all candidates.
#### Is Invalidation Sensitivity optimized?
No. It is user-controlled. The inclusion switch determines whether its hits affect ranking and performance.
#### Why does the invalidation zone disappear on a signal?
The zone is intentionally blanked on the direction-change candle while the new trend-dependent side resets. It should return on the next bar once the new value is available.
#### Does the invalidation zone disappear after it is hit?
No. The visual zone remains until an opposite signal changes direction. If zone hits are included, the simulated position can close internally even while the visual zone remains on screen.
#### Why is the zone below price after a Sell signal?
After a confirmed Sell, V1.7 selects the upper VIDYA/ATR band. “Upper” means above the VIDYA value, not necessarily above the live market price. Because VIDYA is lagging and the zone is not price-clamped, a fast move can temporarily leave that upper band below the current candle. Allow the signal candle to finish—the new zone appears on the next bar—and review the placement before enabling zone hits in performance.
#### Is Bull/Bear Strength optimizer confidence?
No. It is a separate Gaussian curve-position calculation. It does not measure the probability that a trade will win and does not affect candidate ranking.
#### Why can Net Profit include a current trade that Trade Count does not?
Net profit and drawdown are marked to market, so the still-open fraction is valued at the current selected close. Trade Count increments only when a directional cycle is completed.
#### Do hidden labels disable alerts?
No. Display switches hide visual objects only. The underlying signal and alert conditions remain active.
***
### Complete settings reference
#### 1. Entry Mode
| Input | Default | Options or range | Purpose |
| ---------------------------- | -------------------------- | ----------------------------------------------- | ------------------------------------------- |
| Entry Mode | Auto Optimize | Auto Optimize; Manual (Fixed) | Adaptive candidate ranking or fixed values. |
| Entry System | V1.2 | V1.2; V1.4 | Selects the entry engine. |
| Trading Style | Day Trading | Scalping; Day Trading; Swing Trading; Investing | Sets search and qualification rules. |
| Optimize For | Net Profit + Profit Factor | Four ranking goals | Selects candidate score. Ignored in Manual. |
| Use Heikin Ashi Calculations | On | On; Off | Smooths the entry calculation source. |
#### 2. Manual Fixed Settings
| Input | Default | Range | Purpose |
| ----------- | ------- | ------------------------ | ---------------------------------- |
| Sensitivity | 2.0 | 0.25 to 10.0, step 0.025 | Fixed signal threshold multiplier. |
| Tuning | 70 | 5 to 400 | Fixed signal period. |
#### Auto Optimizer
| Input | Default | Range | Purpose |
| ----------------------------- | ------- | ------------------------- | ------------------------------------------------------------------- |
| Bars To Evaluate | 5,000 | 1,000 to 20,000, step 500 | Historical simulation window. |
| Minimum Trades Before Ranking | 5 | 2 to 100 | User floor before a candidate can rank. Style scaling may raise it. |
#### Trade Management
| Input | Default | Range | Purpose |
| --------------------------------- | ------- | ---------------------- | ------------------------------------------------------------------------- |
| Enable Smart Take Profit | On | On; Off | Enables six staged ATR targets. |
| TP Sensitivity | 2.0 | 0.5 to 10.0, step 0.25 | Controls TP spacing. Not optimized. |
| Position Closed Per TP (%) | 20% | 1% to 100%, step 1% | Fraction of the remaining position closed at each TP. |
| Enable Invalidation Zone | On | On; Off | Shows the VIDYA/ATR invalidation zone. |
| Invalidation Sensitivity | 2.0 | 0.5 to 10.0, step 0.5 | Controls zone distance. Not optimized. |
| Include Zone Hits In Optimization | Off | On; Off | Makes center touches close the simulated remainder and affect statistics. |
#### Display & Dashboard
| Input | Default | Options | Purpose |
| ------------------------- | --------- | ----------------- | ---------------------------- |
| Bullish Color | Green | Color selector | Bullish visual theme. |
| Bearish Color | Red | Color selector | Bearish visual theme. |
| Show Buy/Sell Labels | On | On; Off | Buy/Sell text labels. |
| Show Buy/Sell Circles | On | On; Off | Layered signal circles. |
| Show Smart Bar Coloring | On | On; Off | AlgoPro candle colors. |
| Show Dashboard | On | On; Off | V1.7 dashboard. |
| Dashboard Position | Top Right | Five positions | Dashboard location. |
| Dashboard Text Size | Small | Tiny through Huge | Dashboard typography. |
| Show Trend Strength Meter | On | On; Off | Bull/Bear Strength displays. |
***
### Glossary
| Term | Meaning in AlgoPro V1.7 |
| ------------------- | ------------------------------------------------------------------- |
| Candidate | One Sensitivity/Tuning combination tested by the optimizer. |
| Current winner | Highest-ranked qualified candidate on the latest confirmed bar. |
| Ready | Candidate has enough completed trades. |
| Qualified | Candidate is Ready and its average hold matches the selected style. |
| Marked to market | Values an open position using the current selected close. |
| Profit Factor | Gross completed gains divided by gross completed losses. |
| Avg Win / Loss | Average winning trade divided by average losing trade. |
| Max Drawdown | Worst decline from a previous marked-equity peak. |
| TP step | ATR(14) multiplied by TP Sensitivity. |
| Remaining position | The fraction not yet closed by prior TP events. |
| Invalidation center | The active long or short VIDYA/ATR center used for zone-hit logic. |
***
### Risk and interpretation
AlgoPro's optimizer describes what performed best among a finite group of settings over a selected historical window. It does not prove that the same relationship will continue.
Results can be affected by:
* changing volatility and market regime;
* symbol liquidity and spread;
* timeframe and available history;
* the rolling optimization window;
* adaptive winner changes;
* intrabar price-path uncertainty;
Use the dashboard as comparative research, validate settings outside the optimized sample, and apply independent risk management before using any signal in live trading.
***
