OmniTrader Forum OmniTrader Forum
forums calendars search
today this week
 
register logon control panel Forum Rules
You are currently browsing as a guest.
You should logon to access more features
A Self-Moderated Community - ALL MEMBERS, PLEASE READ!
Vote for Members who contribute the most to your trading, and help us moderate content within the Forums.


  Current location        Thread information  
OmniTrader 2017 Upgrade Forums
Trade Plans
Moving Average Crossover Stop
Last Activity 7/17/2018 10:46 AM
2 replies, 1041 viewings

Jump to page : 1
Now viewing page 1 [25 messages per page]
 
back reply
Printer friendly version

^ Top
Vinay

Legend
100100100100252525
Posts: 479

Joined: 12/9/2011
Location: Planet Earth

User Profile
 
Subject : Moving Average Crossover Stop
Posted : 3/10/2014 10:35 AM
Post #31093

I tried to configure a "Moving Average Crossover Stop" pictured below in a Trade Plan in OmniScript.


 



However I am getting significantly different results from these two configurations. Where I am making the mistake? Thanks in advance for any help.


[Edited by Vinay on 3/10/2014 10:41 AM]

Attached file : MACrossover Stop.jpg (59KB - 366 downloads)
Attached file : OS.jpg (14KB - 352 downloads)

^ Top
Jim Dean

Idol
200050010010010025
Posts: 2825

Joined: 9/21/2006
Location: L'ville, GA

User Profile
 
Subject : RE: Moving Average Crossover Stop
Posted : 3/10/2014 11:12 AM
Post #31094 - In reply to #31093

Since you've not provided the strategy, nor snapshots of the charts, it's a little hard to know what it is you are seeing, or to duplicate it.

My GUESS is that one or more of three things are the case:

1. "During Session" is checked and you are using Realtime, which could maybe make the OScript formula exit based on H/L prices at the HRE ... try unchecking that box and see if it helps.

2. Since OT's helpfile gives only a general explanation of this stop, it could be that their method is a little different ... for example, they might use EMA(41)[1], and/or maybe <= rather than <

3. OT's stop is described as a "crossover" stop, and yours may not be (depending on what the rest of your strategy is). By strict definition, a "crossover" is identified by comparing "before and after". It's possible that a strategy might enter the trade with C initially below EMA(41) ... which the OScript formula would immediately exit, but MAYBE OT's would not, UNTIL C first was found to be above EMA(41), then subsequently (during the trade) crossed below EMA(41)
... if that is the case, then this OScript formula would likely be closer to the (not totally revealed) OT logic:
C < EMA(41) and C[1] > EMA(41)[1]

BOTTOM LINE:

Since, for their own reasons, Nirvana chooses to provide "overview conceptual" explanations of their canned stops, it's sometimes tricky to write code that matches precisely what their stops do (ie to reverse engineer their canned stops).

So, the user has a choice ... WORK WITH the canned stops, trusting that N's code is a decent implementation of the concept they explained,
OR
The user can WRITE THEIR OWN stops that do precisely what they want them to do, using OScript or OLang.

I have learned, the hard way, that it's not a very productive use of time to try the reverse-engineering route. That's why I recommend OT Pro so highly for users that feel uncomfortable with a "trust me" blackbox approach &/or want to "customize/tweak" things in detail.

[Edited by Jim Dean on 3/10/2014 11:16 AM]

^ Top
Vinay

Legend
100100100100252525
Posts: 479

Joined: 12/9/2011
Location: Planet Earth

User Profile
 
Subject : RE: Moving Average Crossover Stop
Posted : 3/10/2014 11:25 AM
Post #31095 - In reply to #31093

Thanks Jim. Since I am using EOD data so your point #1 is ruled out. However your point #2 & #3 makes sense to me. Thanks once again for so painstakingly explaining this.
Jump to page : 1
Now viewing page 1 [25 messages per page]
back reply

Legend    Action      Notification  
Administrator
Forum Moderator
Registered User
Unregistered User
E-Mail this thread to a friend
Toggle e-mail notification


Nirvana Systems
For any problems or issues please contact our Webmaster at webmaster@nirvsys.com.