Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
i'd suggest using Enum parameters instead of string parameters when appropriate in your indicators/strategies - you'll be able to optimize over the different values of any enum parameters in your strategy.
piersh i am enjoying this very much so thank you. i have noticed however the occasionally i make some code changes such as a Print() statement or commenting out such a statement, and when i re-run the optimizer the old code is still present. i am 100000% positive the new code was compiled and i have seen this on at least a half dozen occasions. it seems the information is cached and the only way to correct is to exit ninja and restart.
fyi.
"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain
thx i reached same conclusion (intellisense cache). could just delete it but i find easier to restart. however i dont recall ever seeing this before using piersh GO so was thinking might be something to do with the Dispose method and his GC method? it isn't a huge deal so long as I know it is occurring but what is scary is if i change code and did not realize it was cached i may dismiss code changes as ineffective when in fact they were not evaluated to begin with.
"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain
huh, that's weird. i've never seen this behavior myself but that might be because I always use an external editor (visual studio) and never open my code files in NT.
if you can find a way to reliably reproduce this problem, let me know and I'll try to work out if it's the optimizer causing it...
Piersh, As my very first post here, I want to thank you for the exceptional effort here with this optimizer -- it's an incredibly valuable tool that you've shared here with everybody! I truly wish I had something equally cool to share with you.... If you ever come to St. Paul, Minnesota, the beer is ABSOLUTELY on me. An absolutely massive contribution. Just incredible.
Sorry. I can't find a way to do this . The ninjatrader optimizer Api is very rudimentary and it doesn't allow one to acces this kind of information from within the optimizer. Let's hope they improve it in nt7...
Piersh, please forgive me for what is probably a stupid question, but is there some easy way to test out a strategy in multiple time periods? For example, testing a basic moving average strategy for 1 minute, 2 minutes, 3 minutes, 4 minutes... etc... all the way to 60 minutes, just as an example, --all in one long test? Again, I thank you for sharing this with everybody. I've been up the whole night (the past 2 nights!) playing with this thing... it's just awesome...!