Timeframe, Operator, Value, And Params
Every filter rule in the editor is built from the same core pieces. If you understand those pieces, you can read almost any rule in the strategy and spot mistakes quickly.
What this is
This article explains the anatomy of one filter rule in the bot editor.
When to use it
Use this article if:
- you do not understand what a rule field means
- you want to build filters more precisely
- you need to debug why a rule behaves differently from what you expected
Before you start
Before editing an individual rule, know these basics:
- a rule is defined by type , timeframe , op , value , and params
- supported timeframes are 1 , 5 , 15 , 30 , 60 , 240 , and D
- the core operator set is above , below , cross_above , cross_below , and eq
- some filters expose additional params, while others do not
- some filters, such as funding_rate , hide timeframe entirely
Step by step
Step 1: Choose the rule type
The rule type is the indicator or trigger itself, such as:
- RSI
- EMA crossover
- Bollinger %B
- volume ratio
- TradingView signal
The rule type decides which other fields are relevant.
Step 2: Set the timeframe
The timeframe tells the rule which candle interval to evaluate.
Use higher timeframes for slower context and lower timeframes for faster triggers. The key principle is consistency: the timeframe should match the setup idea instead of being chosen at random.
Not every rule shows the timeframe selector. That is expected for filters whose data source is not candle-based in the same way.
Step 3: Set the operator
The operator defines the relationship that must be true.
The current operator set is:
- above
- below
- cross_above
- cross_below
- eq
Use crossing operators when the event matters. Use above or below when the level itself matters. Use eq for fixed-value cases such as TradingView signal actions.
Step 4: Set the value
The value is the threshold or target the rule compares against.
Examples:
- RSI value such as 30
- percentage threshold
- fixed option values such as TradingView BUY or SELL
Do not assume the value is always a price. In many filters it is a threshold, not a quote.
Step 5: Configure params
params are indicator-specific settings. They can include:
- lookback period
- smoothing period
- multiplier
- rule-specific tuning fields
Examples from the available filters:
- rsi uses period
- ema_crossover uses fast_period and slow_period
- supertrend uses period and mult
- funding_rate can use:
- max_seconds_to_next_funding (entry window; allow the rule only when funding is close enough)
- target_seconds_to_next_funding (submit target; hold order placement until the target window starts)
- submit_slack_seconds (execution slack; accounts for gateway/exchange latency around the target)
- cancel_unfilled_seconds_after_funding (post-funding TTL; cancels a still-unfilled entry order after settlement)
Step 6: Validate the rule in context
After editing a rule, check:
- does the timeframe match the setup idea
- does the operator match the behavior I want
- is the value a threshold, an event, or a fixed option
- do the params make the rule too slow or too noisy
Then run Test Filters instead of trusting the rule by inspection only.
What you should see
After reading a rule, you should be able to answer:
- what the rule measures
- on which timeframe it measures it
- what condition must be true
- which threshold or option it checks
- which extra params modify the calculation
Common mistakes
- using cross_above when you only need a stable above condition
- copying a value from one indicator into another indicator with different meaning
- treating params as decoration instead of part of the calculation
- mixing timeframes without a deliberate design
- forgetting that some rules use fixed value options rather than free numeric thresholds
Related articles
- How Entry Filters Work
- Grid Settings
- Exit Settings And Risk Management