userque
Well-known member
Troubleshooting update.
I keep copies of the last 26 versions of anything of importance I'm working on. Upon inspection, I saw where I broke stuff. (There was more involved than my previous post indicated. I realized that after conducting longer backtests, which showed Houston that there was a problem.)
Fixed stuff and added new features. Currently hill climbing (optimizing). Optimizing on a meticulous scale. Not even one quarter of the way finished with what I believe will be the likely complete search field.
Optimizing is simply plugging in different parameters in some orderly fashion and noting which performs best. It is used with complex systems such that a determination can't simply be made with maths etc as to what should be the best configuration.
I start optimizing with 'easier'/'quicker' parameters first, then move to longer ones. When not being meticulous, I start with the likely 'best' parameters first.
I'm testing essentially all configurations, to ensure the best possible result...even if I won't finish until after the opening bell...it's currently good enough to trade with right now.
To break any ties between two or more configuration settings, I simply expand the time frame of the testing until only one 'best' is left. Currently:
The time frame is from 4/6 through 3/16
The best possible result (trading perfectly) would turn $1000 into about $1934.40
The best settings so far yield $1311.46 from $1000...again, not 1/4th done yet with the settings search. (The worst settings so far were in the $800's, btw)
Anyway, the best-thus-far likes being in NUGT right now (what I'm in). Instead up posting an update every time the system finds a better configuration, I'll post the best-so-far, and the position I'll be taking or not (circa the open), before the opening bell.
I keep copies of the last 26 versions of anything of importance I'm working on. Upon inspection, I saw where I broke stuff. (There was more involved than my previous post indicated. I realized that after conducting longer backtests, which showed Houston that there was a problem.)
Fixed stuff and added new features. Currently hill climbing (optimizing). Optimizing on a meticulous scale. Not even one quarter of the way finished with what I believe will be the likely complete search field.
Optimizing is simply plugging in different parameters in some orderly fashion and noting which performs best. It is used with complex systems such that a determination can't simply be made with maths etc as to what should be the best configuration.
I start optimizing with 'easier'/'quicker' parameters first, then move to longer ones. When not being meticulous, I start with the likely 'best' parameters first.
I'm testing essentially all configurations, to ensure the best possible result...even if I won't finish until after the opening bell...it's currently good enough to trade with right now.
To break any ties between two or more configuration settings, I simply expand the time frame of the testing until only one 'best' is left. Currently:
The time frame is from 4/6 through 3/16
The best possible result (trading perfectly) would turn $1000 into about $1934.40
The best settings so far yield $1311.46 from $1000...again, not 1/4th done yet with the settings search. (The worst settings so far were in the $800's, btw)
Anyway, the best-thus-far likes being in NUGT right now (what I'm in). Instead up posting an update every time the system finds a better configuration, I'll post the best-so-far, and the position I'll be taking or not (circa the open), before the opening bell.