Complete Input Handbook — all 102 fields, explained through the Highway metaphor
This handbook covers every single input field in the EA — grouped exactly as in MT4's Properties window, in the exact order they appear. Every field now carries a fixed, permanent number (001–102) baked directly into both its name and its on-screen description in MT4, so you can always find the exact same field, in the same spot, in any conversation, any recipe, and any future version of this handbook.
0. The Ignition Lock
One single field, but the most important one in the whole handbook — everything else is meaningless if this one is set wrong.
| # | Field | Default | Explanation |
| 001 | Inp001_AllowRealTrading | false | The master ignition lock for real money. Left off, the EA can only ever drive on a demo track, no matter what else is configured. Only turn this key if you have deliberately, consciously decided to let the car drive on a real road — never flip it as a side effect of testing something else, and never flip it back on without re-checking every other setting first. |
1. Transmission (Gear System)
These eight fields control the car's gearbox itself — which gear it starts in, and how the guardrails (Stop Loss / Take Profit) behave for the classic Gears 1 through 7. None of this touches Gear 8/ARS, which has its own separate sections below.
| # | Field | Default | Explanation |
| 002 | Inp002_CurrentGear | GEAR_8 | Which gear the car starts in — Park, Reverse, 1st through 7th, or ARS (Gear 8). This is the single most consequential setting in the whole file, since it decides which strategy runs at all. |
| 003 | Inp003_StartInAutoMode | false | If true, an automatic gearbox picks the gear itself on every startup — completely overriding field 002 above. Kept false so your manually-chosen gear actually sticks. If you ever wonder why ARS "isn't starting," check this field first. |
| 004 | Inp004_BaseSL_Feet | 10.0 | For Gears 1–7 only: how many "Feet" of road behind the car count as the safety guardrail (Stop Loss) before a trip is called off as a loss. One Foot equals 10 pips / roughly 1 USD of price movement on most instruments. |
| 005 | Inp005_BaseTP_Feet | 20.0 | For Gears 1–7 only: how many Feet ahead marks the finish line (Take Profit) where the trip ends successfully. |
| 006 | Inp006_TrailingStep_Feet | 3.0 | Once trailing kicks in (see field 008), how many Feet behind the car the guardrail follows as it advances. |
| 007 | Inp007_BreakEven_Feet | 4.0 | How far ahead the car must have driven before the guardrail is pulled all the way up to the starting line — from that point on, the trip can no longer end in a loss. |
| 008 | Inp008_MinProfitToTrail | 2.0 | Minimum distance already driven before the trailing guardrail (field 006) starts following at all. Keep this larger than field 006 — we found out the hard way that if the trail step is bigger than this threshold, the very first guardrail placement can land behind the starting line, turning a small profit into an automatic small loss. |
| 009 | Inp009_MinSLDistance | 5.0 | The guardrail is never allowed closer than this many Feet to the car, regardless of what the other trailing math above suggests — a hard minimum safety clearance. |
2. Vehicle Size
Controls how big each car is (position size), how many can be on the road together, and how long the garage waits between departures.
| # | Field | Default | Explanation |
| 010 | Inp010_LotMode | LOT_RISK_PERCENT | Vehicle sizing mode: either every car is the same fixed size (LOT_FIXED), or each car is sized dynamically based on how much fuel — account risk — you're willing to spend on that particular trip (LOT_RISK_PERCENT). |
| 011 | Inp011_FixedLotSize | 0.01 | The size of the car when field 010 is set to Fixed mode. |
| 012 | Inp012_RiskPercent | 10.0 | The percentage of account "fuel" allowed per trip when field 010 is set to Risk Percent mode instead. |
| 013 | Inp013_MaxPositions | 1 | How many vehicles are allowed on the road, across everything the EA controls, at the same time. |
| 014 | Inp014_TradeCooldownMin | 5 | Minimum minutes the garage waits after the last car departed before it's allowed to send out the next one. |
3. Curb Touch Detection
This single field tunes how sensitively Gears 1–7 detect their entry trigger — the "curb touch" moment.
| # | Field | Default | Explanation |
| 015 | Inp015_CurbTouchTolerance | 5 | How close (in tics — the smallest price unit MT4 tracks) the car must get to the curb/sidewalk edge before it counts as an actual "curb touch" and triggers an entry attempt for Gears 1–7. |
4. Quarter Level TP/SL
A single switch that changes how Gears 1–7 aim their guardrail and finish line.
| # | Field | Default | Explanation |
| 016 | Inp016_UseQuarterLevelTPSL | false | For Gears 1–7: instead of the fixed Feet distances in section 1, aim the guardrail and finish line at the nearest round, structurally meaningful road marker (a Quarter Level — e.g. every 25 USD for gold) instead. Gear 8/ARS has its own, separate Quarter Level exit (field 021) — this field does not affect ARS. |
5. ARS Exit Modules (Gear 8 only)
Gear 8/ARS deliberately opens every trip with no Stop Loss and no Take Profit — these nine fields are the only things standing between "no exit at all" and "an automatically managed exit." All default to off except field 025 (Bounce), which is a deliberate exception.
| # | Field | Default | Explanation |
| 017 | Inp017_G8_UseTrailingLock | false | Module 1 on/off. Watches the highest floating profit reached so far on a trip and closes it automatically if profit falls back too far from that peak. |
| 018 | Inp018_G8_TrailStartUSD | 2.0 | Profit (USD) the trip must first reach before Module 1's trailing watch even begins paying attention. |
| 019 | Inp019_G8_TrailBufferUSD | 1.0 | How far profit is allowed to fall back from its peak before Module 1 ends the trip. |
| 020 | Inp020_G8_TrailMinResultUSD | 1.0 | A hard floor on top of the two fields above: Module 1 may never auto-close a trip below this result, even if the peak/buffer math would otherwise suggest it — this is the fix for a real bug we found where a peak that only briefly touched the start threshold could let the math close a trade at a small loss. Manual closes (CLOSE ALL / CLOSE LONG / CLOSE SHORT / COLLECT) are never affected by this floor — it only limits Module 1's own automatic behavior. |
| 021 | Inp021_G8_UseQuarterExit | false | Module 2 on/off. Ends the trip once the car reaches the next round road marker (Quarter Level) in its favor. |
| 022 | Inp022_G8_UseTrendBreakExit | false | Module 3 on/off. Ends the trip if the bigger-picture road (M30/H1/H4) is no longer unanimously heading the direction it was when the trip began — regardless of current profit or loss. Gated by the Candle Freshness guard (field 024). |
| 023 | Inp023_G8_UseReversalFlip | false | Module 4 on/off. If a brand-new, fully-formed opposite pullback pattern appears, this ends the current trip AND immediately sends a new car the other way in one motion. Also gated by field 024, and by the Mixing Console's Flip Threshold (field 028) if the Mixer is on. |
| 024 | Inp024_G8_CandleFreshnessSec | 45 | How many seconds a newly-opened M5-or-larger road segment must "settle" before Modules 3 and 4 trust its color at all. This exists because we observed real false alarms right after a timeframe switch, when a color reading can briefly flicker before stabilizing. |
| 025 | Inp025_G8_UseBounce | true | The only ARS module defaulting to on. Governs the two "Bounce" windows, :15:00–:16:00 and :45:00–:46:00 server time, where signals were observed to be unreliable. true = deliberately drive the opposite of the computed direction during these windows (applies separately to both a fresh entry and a Module 4 flip). false = refuse to drive at all during these windows instead. The windows themselves are always watched — this field only decides which of the two responses happens, it cannot switch the window-watching off entirely. |
6. The Mixing Console (Gear 8 only)
Thirty-eight fields, but don't let the count intimidate you — they break down into a simple, repeating pattern: a master switch and two scoring thresholds, then nine independent "gauges" (each with its own on/off switch, a point value, and sometimes a couple of measurement settings), and finally one separate volatility veto that isn't a gauge at all. Every gauge is off by default; the whole console is inert until field 026 is switched on.
6.1 — Master Switch and Thresholds
| # | Field | Default | Explanation |
| 026 | Inp026_Mix_UseMixer | false | Turns the entire Mixing Console on or off. Off (default) means every field below this point is completely inert — ARS behaves exactly as it did before this feature was built. |
| 027 | Inp027_Mix_EntryThreshold | 3 | The minimum total score, added up across every active gauge below, needed before a new Trend Trade is allowed to actually depart. |
| 028 | Inp028_Mix_FlipThreshold | 3 | The same idea, but for Module 4's Reversal Flip specifically — kept as its own separate number since flipping an existing position is arguably a bigger decision than opening a fresh one, and you may want a stricter (or looser) bar for it. |
6.2 — Gauge 1: Curve Memory (ZigZag alternation)
Reads the Compass/ZigZag calculation already built into the indicator. After a confirmed peak ("Zig"), a trough ("Zag") is statistically expected next, and vice versa — this gauge checks whether that expectation lines up with the direction you're about to drive.
| # | Field | Default | Explanation |
| 029 | Inp029_Mix_UseCurveMemory | false | Gauge 1 on/off. |
| 030 | Inp030_Mix_WeightCurveMemory | 2 | Points awarded toward the score when Gauge 1 fires. |
6.3 — Gauge 2: Sidewalk Proximity (pedestrian zone)
Reads the inner-lane boundary already computed by the indicator. If price has already drifted off the normal lane onto the sidewalk on the side against your intended direction, a U-turn back toward you is considered more likely.
| # | Field | Default | Explanation |
| 031 | Inp031_Mix_UseSidewalk | false | Gauge 2 on/off. |
| 032 | Inp032_Mix_WeightSidewalk | 2 | Points awarded toward the score when Gauge 2 fires. |
6.4 — Gauge 3: Mileage Streak (candle-series consistency)
Checks whether the last few road segments — not just the current one — have all pointed the same way, as a simple measure of trend consistency over time rather than a single snapshot.
| # | Field | Default | Explanation |
| 033 | Inp033_Mix_UseMileageStreak | false | Gauge 3 on/off. |
| 034 | Inp034_Mix_WeightMileageStreak | 1 | Points awarded toward the score when Gauge 3 fires. |
| 035 | Inp035_Mix_MileageStreakBars | 2 | How many consecutive bars on the timeframe below must all agree on direction for the streak to count. |
| 036 | Inp036_Mix_MileageStreakTF | PERIOD_H1 | Which timeframe the streak in field 035 is measured on. |
6.5 — Gauge 4: Rush Hour Bonus (:00 / :30 timing preference)
Rewards trades that fall close to the top of the hour or the half-hour, based on the observation that these moments tend to carry more decisive, purposeful moves than random in-between times.
| # | Field | Default | Explanation |
| 037 | Inp037_Mix_UseRushHourBonus | false | Gauge 4 on/off. |
| 038 | Inp038_Mix_WeightRushHourBonus | 1 | Points awarded toward the score when Gauge 4 fires. |
| 039 | Inp039_Mix_RushHourWindowSec | 90 | How many seconds after a fresh :00 or :30 still counts as "rush hour" for this gauge's purposes. |
6.6 — Gauge 5: Road Steepness (trend strength)
Checks not just whether the road is colored consistently, but whether the incline is actually strong — using the same underlying calculation traders know as ADX.
| # | Field | Default | Explanation |
| 040 | Inp040_Mix_UseSteepness | false | Gauge 5 on/off. |
| 041 | Inp041_Mix_WeightSteepness | 1 | Points awarded toward the score when Gauge 5 fires. |
| 042 | Inp042_Mix_SteepnessPeriod | 14 | Measurement period (in bars) the steepness reading is calculated over. |
| 043 | Inp043_Mix_SteepnessMinLevel | 25.0 | The minimum steepness reading required before this gauge awards its points. |
6.7 — Gauge 6: Engine Overheat (extreme-move filter)
Warns against joining a move that has already run too far, too fast, in your intended direction — the same underlying idea traders know as RSI overbought/oversold.
| # | Field | Default | Explanation |
| 044 | Inp044_Mix_UseEngineOverheat | false | Gauge 6 on/off. |
| 045 | Inp045_Mix_WeightEngineOverheat | 1 | Points awarded toward the score when Gauge 6 fires. |
| 046 | Inp046_Mix_OverheatPeriod | 14 | Measurement period (bars) for the overheat reading. |
| 047 | Inp047_Mix_OverheatHighMark | 70.0 | Above this reading, driving further uphill is considered overheated, and Gauge 6 will not award points for a long trip. |
| 048 | Inp048_Mix_OverheatLowMark | 30.0 | Below this reading, driving further downhill is considered overheated, and Gauge 6 will not award points for a short trip. |
6.8 — Gauge 7: Road Edge (stretched-range filter)
A second, differently-calculated way of asking the same kind of question as Gauge 6: has price already stretched to the outer edge of its normal recent range? Built on the same math traders know as Bollinger Bands.
| # | Field | Default | Explanation |
| 049 | Inp049_Mix_UseRoadEdge | false | Gauge 7 on/off. |
| 050 | Inp050_Mix_WeightRoadEdge | 1 | Points awarded toward the score when Gauge 7 fires. |
| 051 | Inp051_Mix_RoadEdgePeriod | 20 | Measurement period (bars) for the "normal range." |
| 052 | Inp052_Mix_RoadEdgeWidth | 2.0 | How many standard deviations wide the "normal range" is considered to be. |
6.9 — Gauge 8: Brake Lights (reversal candle pattern)
Looks for a simple, well-known reversal candle — a bullish or bearish engulfing pattern — on the most recently closed bar, in your favor.
| # | Field | Default | Explanation |
| 053 | Inp053_Mix_UseBrakeLights | false | Gauge 8 on/off. |
| 054 | Inp054_Mix_WeightBrakeLights | 1 | Points awarded toward the score when Gauge 8 fires. |
6.10 — Gauge 9: Cloud Cover (Ichimoku)
Checks whether price is clearly flying above or below the Ichimoku cloud bank in your intended direction — "Ichimoku" literally translates to "cloud" in Japanese, which is where this gauge's name comes from.
| # | Field | Default | Explanation |
| 055 | Inp055_Mix_UseCloudCover | false | Gauge 9 on/off. |
| 056 | Inp056_Mix_WeightCloudCover | 1 | Points awarded toward the score when Gauge 9 fires. |
| 057 | Inp057_Mix_CloudFastLine | 9 | The cloud's fast (Tenkan) line period. |
| 058 | Inp058_Mix_CloudBaseLine | 26 | The cloud's base (Kijun) line period. |
| 059 | Inp059_Mix_CloudFarSpan | 52 | The cloud's far (Senkou Span B) period. |
6.11 — Storm Warning (veto, not a point gauge)
This one is different from all nine gauges above: it doesn't add points, it can block a trade outright, regardless of how good the score is — like a storm warning telling every car to pull over, no matter how good the road looks. Built on the same math traders know as ATR (Average True Range).
| # | Field | Default | Explanation |
| 060 | Inp060_Mix_UseStormWarning | false | The Storm Warning veto on/off. |
| 061 | Inp061_Mix_StormPeriod | 14 | Measurement period (bars) for the storm reading. |
| 062 | Inp062_Mix_StormTimeframe | PERIOD_H1 | Which timeframe the storm reading is measured on. |
| 063 | Inp063_Mix_StormSensitivity | 1.5 | A "storm" is declared whenever the current reading exceeds its own recent 20-bar average multiplied by this number. Higher = only truly extreme volatility trips the veto; lower = more cautious, trips more easily. |
7. Trading Hours
Four fields that define the garage's opening hours for new departures. Trips already on the road are always still managed, regardless of these hours.
| # | Field | Default | Explanation |
| 064 | Inp064_TradingStartHour | 9 | The garage doesn't open, and no new trip departs, before this hour (server clock). |
| 065 | Inp065_TradingStartMinute | 16 | The minute within the start hour above. |
| 066 | Inp066_TradingEndHour | 21 | The garage stops sending out new trips from this hour onward. |
| 067 | Inp067_TradingEndMinute | 35 | The minute within the end hour above. |
8. Display
Two fields, neither of which affects any trading decision — purely cosmetic, safe to change at any time.
| # | Field | Default | Explanation |
| 068 | Inp068_LocalTimeOffsetHours | -1 | Adjusts the on-chart dashboard clock from the garage's server time to your own local time. Display only — never affects when the garage actually opens or closes (that's fields 064–067, always server time). |
| 069 | Inp069_ShowDashboardComment | false | Shows or hides the on-chart dashboard text entirely. Display only. |
9. Close All / No-TP Mode
These three fields are about Gears 1–7's relationship with the CLOSE ALL button and account-wide auto-close — they do not affect Gear 8/ARS, which already has no TP by design.
| # | Field | Default | Explanation |
| 070 | Inp070_NoTP_UseCloseAllInstead | false | For Gears 1–7: skip the normal finish line (Take Profit) entirely, relying on the CLOSE ALL button or the auto-close threshold (field 072) to end trips instead. A wide, catastrophe-only guardrail (field 071) still stays in place as a last-resort safety net. |
| 071 | Inp071_SafetyNetSL_Feet | 50.0 | How wide that catastrophe-only guardrail is, when field 070 is on. |
| 072 | Inp072_CloseAllProfitThreshold | 0.0 | Automatically calls every car on the entire account back to the garage once total floating profit reaches this amount — not just this EA's own trades. 0 disables this; the manual CLOSE ALL button remains available regardless. |
10. Rush Hour Timing
One field, feeding the Quiet Street / Rush Hour distinction used by Gears 1–7's curb-touch logic (not to be confused with Gauge 4's :00/:30 Rush Hour Bonus in the Mixing Console, which is a different, separate concept despite the similar name).
| # | Field | Default | Explanation |
| 073 | Inp073_RushHourWindowMin | 10 | How wide, in minutes, the Rush Hour / Quiet Street windows are — this decides whether a curb touch for Gears 1–7 gets read as a U-turn (reversal) or a continuation (drive on). |
11. Convoy Check
Three fields controlling an independent second confirmation group used from Gear 4 upward.
| # | Field | Default | Explanation |
| 074 | Inp074_UseConvoyCheck | true | For Gear 4 and above: require a second, independent group of vehicles (USDCHF/USDDKK, the "Convoy") to also confirm the direction before departing. |
| 075 | Inp075_ConvoyTimeframe | PERIOD_M5 | Which timeframe the Convoy's own direction is read from. |
| 076 | Inp076_DriveWithConvoy | true | true = require driving together with the Convoy's direction; false = require driving deliberately against it instead. |
12. Traffic Rules
Four fields, general road-safety filters that apply broadly across gears.
| # | Field | Default | Explanation |
| 077 | Inp077_UseSpreadFilter | true | Refuses to depart if the toll-gate fee (spread) is too high right now. |
| 078 | Inp078_MaxSpreadPoints | 50 | The toll-fee ceiling used by field 077. |
| 079 | Inp079_UseSessionBarrier | false | An additional session-based road barrier that can block departures at certain times, independent of the Trading Hours in section 7. |
| 080 | Inp080_TradeEUUS_Cross | true | Allows or disallows trading through the European/US session border crossing specifically. |
13. Road Construction (advanced)
These 22 settings control the Highway curve itself — the road's underlying shape, sensitivity, and how far back it looks on each timeframe, plus a handful of display and instrument-detection settings that ride along in the same section. Changing the curve-math fields mid-session changes how the EA "sees" trend and curb-touch entirely, so treat the first half of this table with noticeably more caution than everything above.
| # | Field | Default | Explanation |
| 081 | Inp081_CompassSens | 12 | Sensitivity of the ZigZag Compass (the same calculation Gauge 1 in the Mixing Console reads) — how significant a swing must be before it's marked as a genuine turn rather than noise. |
| 082 | Inp082_MinDistSigns | 3 | Minimum spacing required between two road signs (ZigZag pivots) before a new one is allowed to appear. |
| 083 | Inp083_TurnThreshold | 5.0 | How sharp a turn must be, in absolute terms, before the Compass registers it at all. |
| 084 | Inp084_CurveType | 2 | Which mathematical curve shape the road itself is drawn with. |
| 085 | Inp085_LaneWidth | 2.0 | How wide the normal driving lane is. |
| 086 | Inp086_Smoothing | 3 | How much the road's curve is smoothed out, reducing small jitters at the cost of slightly more lag. |
| 087 | Inp087_SidewalkSep | 0.5 | How far the sidewalk (the pedestrian zone Gauge 2 in the Mixing Console reads) sits beyond the normal lane edge. |
| 088 | Inp088_HwLenM1 | 90 | How many bars back the road is drawn on the M1 timeframe. |
| 089 | Inp089_HwLenM5 | 45 | Same, for M5. |
| 090 | Inp090_HwLenM15 | 38 | Same, for M15. |
| 091 | Inp091_HwLenM30 | 35 | Same, for M30. |
| 092 | Inp092_HwLenH1 | 24 | Same, for H1. |
| 093 | Inp093_HwLenH4 | 16 | Same, for H4. |
| 094 | Inp094_HwLenD1 | 12 | Same, for D1. |
| 095 | Inp095_ShowDash | true | Shows or hides the indicator's own multi-timeframe dashboard boxes. Display only. |
| 096 | Inp096_DashPos | 2 | Which chart corner the dashboard sits in. Display only. |
| 097 | Inp097_DashUpdate | 5 | How often, in seconds, the dashboard refreshes. Display only. |
| 098 | Inp098_AmpelPos | 1 | Which chart corner the traffic-light panel sits in. Display only. |
| 099 | Inp099_AutoHighPrice | true | Automatically detects whether the instrument trades at a "high" price level (which affects the road-marker step size), instead of you having to set it manually. |
| 100 | Inp100_PriceThresh | 100.0 | The manual price threshold used instead, when field 099's auto-detection is switched off. |
| 101 | Inp101_CustomStep | 0.0 | A fully custom road-marker step size. 0 means "use the automatic default instead." |
| 102 | Inp102_MagicNumber | 0 | The EA's own license-plate number, so it can always tell its own cars apart from anyone else's — including its own cars from a previous timeframe, which is why this now stays fixed to the symbol only. 0 means "auto-generate one." |
AISHE Highway Pro ARS — Complete Input Handbook · all 102 fields, catalog-numbered 001–102 · companion to the Example Settings / Recipes document
AISHE Highway Pro ARS
Example Settings / Recipes — ready-to-try starting points for the Gear 8 / ARS Mixing Console
These are starting points, not proven answers. None of them have been backtested against real data yet — they're reasonable first guesses to make experimentation easier, built directly from what we've discussed and observed together so far. Try one, watch it for a while, then adjust.
Numbering: every field carries a fixed, permanent, EA-wide catalog number (001–102), baked directly into both its variable name and its on-screen description in MT4 — the same number everywhere, in this document, in the Complete Input Handbook, and in MT4's own Inputs list. See the Complete Input Handbook for the full explanation of every field.
All recipes assume Gear 8 / ARS is already active (field 002 = GEAR_8, field 003 = false) and that you are on a demo account (field 001 = false).
Recipe 1 — "Bare Minimum" (Mixer off entirely)
The simplest possible baseline: pure pullback entries, no mixer, no extra gauges, no storm veto. This is exactly what ARS has been doing throughout all of our testing so far — every trade you've already seen came from this configuration. Useful purely as a reference point to compare every other recipe against.
| # | Field | Value |
| 026 | Inp026_Mix_UseMixer | false |
Every other Mixing Console field (027–063) is irrelevant while 026 is off — you don't need to touch any of them for this recipe.
Recipe 2 — "Your Own Manual Habits"
Built directly from your own description of what you actually watch for in practice: ZigZag alternation, sidewalk proximity, and the :00/:30 timing preference — with the storm warning added as a safety net, since your 15-point drawdown day is exactly the kind of situation it's meant to catch.
| # | Field | Value |
| 026 | Inp026_Mix_UseMixer | true |
| 027 | Inp027_Mix_EntryThreshold | 3 |
| 029 | Inp029_Mix_UseCurveMemory | true |
| 030 | Inp030_Mix_WeightCurveMemory | 2 |
| 031 | Inp031_Mix_UseSidewalk | true |
| 032 | Inp032_Mix_WeightSidewalk | 2 |
| 037 | Inp037_Mix_UseRushHourBonus | true |
| 038 | Inp038_Mix_WeightRushHourBonus | 1 |
| 060 | Inp060_Mix_UseStormWarning | true |
| 063 | Inp063_Mix_StormSensitivity | 1.5 |
The scoring math: three gauges are active, worth 2 + 2 + 1 = 5 points maximum. With the threshold at field 027 = 3, at least two of the three gauges must agree for a trade to fire — Curve Memory alone (2) or Sidewalk alone (2) is not enough by itself; either needs Rush Hour Bonus (1) added on top, or the two 2-point gauges need to agree with each other.
Recipe 3 — "Storm Shelter Only"
Isolates the Storm Warning by itself, with absolutely nothing else changed — the cleanest possible way to see its effect in isolation, exactly as we agreed to prioritize testing it first before anything else.
| # | Field | Value |
| 026 | Inp026_Mix_UseMixer | true |
| 027 | Inp027_Mix_EntryThreshold | 0 |
| 060 | Inp060_Mix_UseStormWarning | true |
| 061 | Inp061_Mix_StormPeriod | 14 |
| 062 | Inp062_Mix_StormTimeframe | PERIOD_H1 |
| 063 | Inp063_Mix_StormSensitivity | 1.5 |
The scoring math: with every gauge switched off, the score is always exactly 0. A threshold of 0 (field 027) means that score always clears the bar — so the only thing that can still stop a trade here is the Storm Warning veto (fields 060–063). This is deliberately a pure isolation test: any difference you observe versus Recipe 1 can only be attributed to the storm veto, nothing else.
Recipe 4 — "Strict Trend Confirmation"
Asks "is this actually a strong, consistent trend?" from four different angles at once, and requires all four to agree. Noticeably stricter than Recipe 2 — expect fewer trades, but each one backed by more independent confirmation.
| # | Field | Value |
| 026 | Inp026_Mix_UseMixer | true |
| 027 | Inp027_Mix_EntryThreshold | 4 |
| 033 | Inp033_Mix_UseMileageStreak | true |
| 034 | Inp034_Mix_WeightMileageStreak | 1 |
| 035 | Inp035_Mix_MileageStreakBars | 2 |
| 036 | Inp036_Mix_MileageStreakTF | PERIOD_H1 |
| 040 | Inp040_Mix_UseSteepness | true |
| 041 | Inp041_Mix_WeightSteepness | 1 |
| 043 | Inp043_Mix_SteepnessMinLevel | 25.0 |
| 044 | Inp044_Mix_UseEngineOverheat | true |
| 045 | Inp045_Mix_WeightEngineOverheat | 1 |
| 055 | Inp055_Mix_UseCloudCover | true |
| 056 | Inp056_Mix_WeightCloudCover | 1 |
The scoring math: four gauges, worth 1 point each = 4 points maximum. Threshold field 027 = 4 means every single one must fire — deliberately maxed out, to explore the "fewer but higher-conviction" end of the spectrum. If this turns out to fire too rarely to be useful, the first thing to try is dropping the threshold to 3, allowing exactly one disagreement.
Recipe 5 — "Everything Loosely Combined"
Turns on all nine gauges, but sets a threshold that's low relative to the maximum possible score — so a trade can still fire even if most gauges disagree, as long as a handful of the highest-weighted ones line up. Useful mainly for observing how often each individual gauge actually fires in real conditions, without the hard blocking effect of Recipe 4.
| # | Field | Value |
| 026 | Inp026_Mix_UseMixer | true |
| 027 | Inp027_Mix_EntryThreshold | 4 |
| 029 | Inp029_Mix_UseCurveMemory | true |
| 031 | Inp031_Mix_UseSidewalk | true |
| 033 | Inp033_Mix_UseMileageStreak | true |
| 037 | Inp037_Mix_UseRushHourBonus | true |
| 040 | Inp040_Mix_UseSteepness | true |
| 044 | Inp044_Mix_UseEngineOverheat | true |
| 049 | Inp049_Mix_UseRoadEdge | true |
| 053 | Inp053_Mix_UseBrakeLights | true |
| 055 | Inp055_Mix_UseCloudCover | true |
| 060 | Inp060_Mix_UseStormWarning | true |
| — | All Weight... fields (030, 032, 034, 038, 041, 045, 050, 054, 056) | leave at defaults (2 for Curve Memory and Sidewalk, 1 for everything else) |
The scoring math: maximum possible score with every gauge's default weight = 2+2+1+1+1+1+1+1+1 = 11 points. A threshold of 4 (field 027) is a relatively low bar against that maximum of 11 — most trades will still need at least two or three gauges agreeing, but nowhere near all nine.
This recipe exists mainly to observe and learn, not necessarily to trade on long-term. With nine separate live calculations running on every single signal check, it's also by far the heaviest recipe computationally.
Recipe 6 — "Flip Only" (leave fresh entries alone)
A different kind of recipe: instead of gating new trades, this one only makes Module 4's Reversal Flip stricter, leaving Trend Trade entries completely untouched. Useful if you're satisfied with how often ARS enters, but want more confirmation before it flips an existing position.
| # | Field | Value |
| 023 | Inp023_G8_UseReversalFlip | true |
| 026 | Inp026_Mix_UseMixer | true |
| 027 | Inp027_Mix_EntryThreshold | 0 |
| 028 | Inp028_Mix_FlipThreshold | 3 |
| 029 | Inp029_Mix_UseCurveMemory | true |
| 030 | Inp030_Mix_WeightCurveMemory | 2 |
| 044 | Inp044_Mix_UseEngineOverheat | true |
| 045 | Inp045_Mix_WeightEngineOverheat | 1 |
The scoring math: field 027 = 0 means fresh Trend Trade entries pass unconditionally, exactly like Recipe 1. But field 028 = 3, evaluated against the same two active gauges (2 + 1 = 3 points maximum), means a flip needs both gauges to agree — a much stricter bar than an entry gets under this recipe.
Suggested order to actually try these
| Step | Recipe | What you learn |
| 1 | Recipe 1 — Bare Minimum | Your existing baseline — you already have real data for this one |
| 2 | Recipe 3 — Storm Shelter Only | Does the volatility veto alone reduce the size of the big drawdown days? |
| 3 | Recipe 2 — Your Own Manual Habits | Does formalizing your existing manual judgment actually help, or hurt? |
| 4 | Recipe 6 — Flip Only | Does a stricter flip bar reduce the false-flip problem we found earlier, without slowing down entries? |
| 5 | Recipe 4 — Strict Trend Confirmation | What happens at the very strict, low-frequency end of the spectrum? |
| 6 | Recipe 5 — Everything Loosely Combined | Broad exploration once you have a feel for how each individual gauge behaves on its own |
AISHE Highway Pro ARS — Example Settings / Recipes · companion to the Complete Input Handbook (fields 001–102)