Run Type in AFL

[DavidHarper]

Is there an AFL function or method that will enable me to determine if my code is running as a scan, an exploration, or a backtest?

[fxshrat]

See Status() function with status codes action and actionex

AFL Function Reference - STATUS

• "action" - gives information in what context given formula is run: 1 - actionIndicator (INDICATOR), 2 - actionCommentary (COMMENTARY), 3 - actionScan (SCAN), 4 - actionExplore (EXPLORATION), 5 - actionBacktest (BACKTEST / OPTIMIZE), 6 - actionPortfolio (portfolio backtest). The value of actionBacktest (5) (backtest) is used also in some other contexts (like code check and profile). Therefore you can use ActionEx to get more detailed/precise information
• "ActionEx" (new in 5.20) - more detailed information about action that triggered AFL execution. Note that 5 first codes are the same as Status("action") but scope is limited to 'core' meaning (see notes below).
  Possible values
  1. actionIndicator - when indicator is being repainted (NOTE: 5.32 - indicator can also give actionExInterpret when updating both chart and interpretation)
  2. actionCommentary (NOTE: commentary only, not interpretaion nor tooltip)
  3. actionScan - when AA Scan is performed
  4. actionExplore - when AA exploration is performed
  5. actionBacktest (NOTE backtest only, no optimization)
  6. actionPortfolio (2nd phase of portfolio backtest (custom backtest)
  7. reserved for future use
  8. reserved for future use
  9. reserved for future use
  10. • actionExAAShowArrows - when AA "Show arrows" command is used
  11. actionExAAParameters - when AA "Parameters" dialog is displayed/updated
  12. actionExEditVerifyFormula - when AFL editor verifies syntax
  13. actionExOptimizeSetup - when Optimize() parameters are read (to setup optimization engine)
  14. actionExOptimizeBacktest - when Backtest is performed as a part of optimization process
  15. actionExOptimizePortfolio - when portfolio-backtest phase (CUSTOM backtester) is performed as a part of optimization process
  16. actionExTooltip - when tooltip for given chart is being displayed/updated
  17. actionExInterpret - when the Interpretation window is being updated (can also mean indicator + interpretation in 5.32 above, see note below)
  18. (not used, reserved for future) actionExAAInit - when AA needs to initialize QuickAFL bars required information and/or formula contains functions changing general AA options

NOTE: for backward compatiblity with all formulas you have written already, the codes for Status("action") did NOT change.

NOTE ABOUT 5.32.x CHANGE: Since introduction of multi-threading, there is only ONE pass/execution that updates both indicator and interpretation when current chart pane has focus. Status("action") will always return actionIndicator and Status("actionex") will either return actionExInterpret (when chart pane has focus and intepretation window is visible) or actionIndicator otherwise (when pane does not have focus or interpretation is NOT visible). Be careful NOT to disable Plot() depending on Status("actionex") code. If you really think you need to execute Plot() conditionally you should only check for Status("action")==actionIndicator.

[DavidHarper]

Thanks for your assistance -- spot on reply to my inquiry.