the time exit in that sleep-safe crypto setup bugs me a bit

read the strategy library post about running crypto unattended with three separate ways out. the part that stuck with me is the reasoning for writing the exits as separate branches instead of one big condition — "clarity is a safety feature". i've definitely written combined conditions at 1am that i could not decode a week later, so fair. but i keep chewing on the HoldTime exit. 2400 seconds, and it fires regardless of where the position sits. so if i'm at +1.8% and the clock hits, out i go, one notch under the take profit. that's the whole point of a time stop i guess, it doesn't negotiate. still feels like it throws away the good tail along with the dead ones. two things i want to ask people who actually run stuff overnight: 1) does anyone make the time exit conditional, like only cut on time if ProfitPct is between say -0.5 and +0.5, and otherwise let the other two branches handle it? or does that just quietly reinvent the combined condition the author was warning about 2) the angle scaling note. the same degrees over a longer window demands a much bigger move, so widening the window means lowering the angle. i normally run 1m-5m stuff and i was going to stretch the window out to calm down the entries. so i'd be dropping the threshold at the same time. Which means i'm changing two knobs at once and i'll have no idea which one did what. anybody got a sane way to test that one variable at a time without spending a month on it not planning to leave anything running until i can explain both branches out loud sober.
CryptoKarl
30 posts · 0 followers
+ Follow

Related reading

3 replies

P
PremarketPete· Jun 2026 ago
- separate branches, always. i've eaten a bad fill because a combined condition had an operator precedence thing i never noticed - on your q2: fix the angle, move only the window, note what happens to entry count. then fix the window, move only the angle. boring but it's the only way you learn anything - time exit at breakeven-ish only is a real pattern, just write it as its own branch with a comment saying why
MLcurious· Jun 2026 ago
I'm still fuzzy on the ChangeAngle thing honestly. So the degrees aren't the price move, they're the angle of the rate of change over the window? Then when you widen the window and keep the same degrees you're asking for a way steeper cumulative move, which is why it fires less often? Sorry if that's obvious, I keep drawing it on paper and half convincing myself.
D
DrawdownDave· Jun 2026 ago
I once had a time exit and a stop that could both be true in the same evaluation and I genuinely could not tell you for weeks which one had closed my positions, because I'd merged them into one line. Cost me nothing directly, but I spent a month tuning the wrong number, which is its own kind of expensive. Not telling you what to do with the profit-band idea, just — whatever you write, make sure the log tells you which branch fired.
Sign in to reply →
← All strategies & backtesting