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)
After sim-trading Method 1 for the past two weeks, I have modified the earlier BETA strategy as enclosed (still BETA).
Hopefully PerrySetUpV3c has captured Method 1's suggested entry criteria PLUS the optional requirements based on my preference. We may use different methods to code the entry requirements. I mapped them out on the enclosed jpeg file to facilitate your adapting them to your needs.
Note: Codes for Short are mostly opposite except Item 6.
This will be the last attempt from my end. I realize auto-trading is fun yet one must have a cushion to accommodate the occasional drawdown of a few Ks. Not to mention he/she will not lose zozozo when a trade or trades for certain days are not working to his/her favor.
I sincerely hope that the enclosed may help some of you visualize the signals. Please bear in mind that it's not 100% matching the discretionary method. My guess: Most indicators are lagged and if one or a few not happening at the same time, the strategy won't fire.
Hi Beth,
Can you tell me if you are using the original JeffsUniversalMovingAverage or the current version JeffsUniversalMovingAverage_v1? In looking at your strategy code, I see it listed without the"_v1" and am wondering why. I tried to set your strategy up in NT6.5 and compile it but i keep getting errors. I can't find the original indicator anywhere - only one seems to be the "_v1" version.
I also tried to open the strategy wizard and see how that works - i got as far as naming my strategy and got lost on the 2nd screen - sigh! Whenever I try to read the dang help files in NT, I feel like I'm reading a foreign language! I'd appreciate any hints you can give me.
I used the original indicator. Tried to locate the v1 version from both Downloads (Regular and Elite) minutes ago with no success. Let me suggest the following since you know how to use the Strategy Wizard (that's what I've been using to find out the code since I do not know C+ language):
1. Control Center - Tools - New NinjaScript - Strategy
Next (Create a new strategy) - Next (General) - Next (User Defined Inputs) - Add (Conditions and Actions)
- Indicators (click on "+") - select the indicator (for your case will be JeffsUniversalMovingAverage_v1)
2. You notice from the enclosed that the variables listed under Plot are the entry criteria available for coding. To save time, I usually choose MyInput0 for the right section UNLESS I need to find out a second code for another plot.
3. After pressing OK, choose View Code and you will get the code for the condition.
If you're certain of the name of your indicator, you may try to add "_v1" to the BETA strategy as quite often plots will remain the same, ie
1. Control Center - Tools - Edit NinjaScript - Strategy
2. Choose PerrySetUpV2c
3. Add "_v1" to the respective codes for both Long and Short conditions
4. Press "F5" to compile
Hopefully Compile Successfully. Else check the error message which may give you some hints what's going wrong.
Additional tips (based on my trouble-shooting experience):
1. When you're editing a strategy (or indicator), you may want to rename it and not replacing the original one. If yes, upon amending the strategy, right-click and choose Save As. Then "F5" after naming your strategy to compile.
2. If compile unsuccessfully, pay attention to the name of the strategy/indicator in question. Sometimes it may not be the one you're working on. That happened to me a few times.
3. Please bear in mind that if there's a strategy or indicator that has programming issues, NJ will not allow you to import or export NinjaScript until you either remove it from the Strategy/Indicator folder OR fix the code. For me, quite often I may end up removing the problemed one from the folder esp if I need to import a NinjaScript urgently.
Beth, I've downloaded your strategy, but haven't had time to play with it yet.
I've been testing the basic Perry method on the TF, ES, and 6E on simulator. So far, very good results. This method is excellent for providing plenty of trades, yet it takes much of the guesswork out of proper entry. It's really the best overall method I've seen to date. I've had enough experience to recognize the benefits of the method, being mainly reduction of stress in trading decision making. So I think the Perry method is well suited to both newbie, and experienced trader alike.
Thanks for the tips, Beth. I will try the edit 1st before trying to build a new strategy but I think I tried that already and it failed to compile. The errors were ref'ing that Jeff's indicator and something called MAType, saying it didn't exist or it couldn't find it - something like that. Not quite sure if I did something else wrong, though, so will try again. Also not sure I am smart enough to build one, even with the wizard. I was thinking I had to look for a video if there is one, to lead me by the nose! LOL.
If you search for JeffsUniversalMovingAverage there are 2 places that come up with the _v1 and none for the original one. Under "Platforms and Indicators" it is posted under " NT7 MA region color indicator " by Breakout and Perry has also posted it in the Elite Forum.
