NOT turns a condition around. Wire in "today is an FOMC day" and you get "today isn't". One input, one output, nothing to set.
- Takes
- One condition
- Gives
- Its opposite: true whenever the input is false
- Reach for it
- You have a condition and need it to be false
How it works
You'll need it less often than you'd think. The opposite of "RSI above 70" is a Comparison set to Less Than or Equal, and that reads more clearly on the canvas. NOT earns its place when the condition arrives ready-made, like an Event Day, a Tally's pass or an AND of several things.
One difference from writing the opposite comparison: a condition whose value is missing (a level that hasn't formed yet, a divide by zero) reads false, so its NOT reads true. And two NOTs in a row cancel out, which is why the builder won't let you wire one straight into another.
Example: no trades on FOMC days
Add an Event Day node set to FOMC, wire its Event day output into a NOT, and AND the NOT with your entry signal through a Logic node. The strategy now sits out every FOMC day and trades the rest as before.
Settings
NOT has no settings.
When it doesn't behave
Every trade exits on the very next bar
Look for a NOT in front of a crossover in your exit. "Exit when NOT (EMA 20 crosses above EMA 50)" sounds right, but a Crossover is true on one bar only, so its NOT is true on nearly every bar, and each trade exits on the bar after it opens. To exit when the cross reverses, use the opposite state (a Comparison: EMA 20 below EMA 50) or the opposite crossover (crosses below). The builder and the Inspector's checks both flag this one.