When a developer or service claims their AFL code is “verified,” they are making three distinct promises:
Plot key intermediate variables:
Plot(Close, "Close", colorBlack, styleCandle);
Plot(mySignalLine, "Signal", colorRed, styleLine);
Plot(myBuyCond, "Buy Cond", colorGreen, styleOwnScale);
Manually inspect 10–20 bars to see if conditions trigger at plausible points.
Professional verifiers add timestamps:
StaticVarSet("LastSignalTime", LastValue(DateTime()));
If the stored time is later than the bar being processed, you have a leak. amibroker afl code verified
SetOption("FuturesMode", 1);
SetOption("CommissionMode", 3); // per share
SetOption("CommissionAmount", 0.01);
SetTradeDelays( 1, 1, 1, 1 ); // enter next bar, exit next bar
Verification: Log every trade’s assumed fill price vs. actual bar OHLC.
To verify a backtest matches your intended capital, force the settings in the code rather than relying on the Analysis Window UI settings.
SetOption("InitialEquity", 10000);
SetOption("MinShares", 1);
SetPositionSize(100, spsPercentOfEquity); // Verify you are using 100% equity
| Criteria | Score (1–5) | |----------|--------------| | Syntax accuracy | 4 | | Strategy validation | 1 | | Value for money | 3 | | Transparency | 2 | | Usefulness for beginners | 4 |
Bottom Line:
Paying for “AFL code verified” is like paying someone to spell-check a business plan – it ensures readability, not success. Use it only to catch bugs, not to validate trading strategies. For the latter, learn backtest validation yourself or hire a quant developer for a proper walk-forward analysis. When a developer or service claims their AFL
Recommendation:
To have "Amibroker AFL code verified" means ensuring your trading script is syntactically correct, logically sound, and performance-optimized before committing capital. Verification in AmiBroker typically involves a three-stage process: syntax checking, logic debugging, and robust backtesting. 1. Syntax Verification
The first step is checking for "clean" code that follows AmiBroker's language rules.
Verify Syntax Tool: Use the Tools -> Verify syntax option (or the checkmark icon) in the AFL Editor. This identifies typos, missing semicolons, or improper operator usage (e.g., using = instead of == for comparisons). Manually inspect 10–20 bars to see if conditions
Prettify Selection: Use Edit -> Prettify Selection to format your code, making indentation errors and logical structures easier to spot. 2. Logic & Performance Debugging
Once the code runs, you must verify that the numbers it calculates are accurate.
Exploration Tool: Use the AddColumn() function and run an Exploration to see raw data values for every variable on each bar. This is the most effective way to verify if your buy/sell signals are triggering as intended.
_TRACE & Debugger: Insert _TRACE() or _TRACEF() functions to output variable values to the Log window in real-time. For complex logic, use the built-in AFL Debugger to step through code line-by-line.
Code Profiler: Use Tools -> Code check & Profile to identify slow functions or "loop-invariant" code that should be moved outside of loops for better performance. 3. Backtest & Optimization Verification
A "verified" strategy must show consistent results across historical data. How to optimize a trading system - AmiBroker