Posts: 434
Joined: 6/6/2006
User Profile Hi support I thought I would try the random walk again in a basic test using this code 1,2, 3, minute time frames were all loaded.
if MTR(RWI_HIGH(5,7),1,0) > 1 then
signal=longsignal
end if
If tis is code is valid then it is not performing as it should.
Thanks JohnB
Posts: 3433
Joined: 3/13/2006
Location: L'ville, GA
User Profile Have you tried enclosing the function call in double quotes? I know that Barry said they were optional, but I’d suggest testing it anyways.
Reason: the function call has commas inside it that might be messing up the parser.
Posts: 434
Joined: 6/6/2006
User Profile Hi Jim Thanks for the suggestion and yes I have now tried that and sadly no luck either with or without quotes.
Posts: 2309
Joined: 1/1/1900
User Profile It looks like a bug. I'll report it. In the meantime this formula should work for you instead. Change the W to whatever timeframe you need if not weekly.
MT("RWI_HIGH(5,7)","W",1)
Posts: 434
Joined: 6/6/2006
User Profile Hi Barry thanks for coming back. Perhaps you will be able to notify the thread when there is a full fix and with the official protocols.
best wishes John B
Posts: 434
Joined: 6/6/2006
User Profile I tired this in real time and it shows no UP arrows...
if MT("RWI_HIGH(5,7)","1",1) = 0 then
signal=longsignal
end if
Posts: 2309
Joined: 1/1/1900
User Profile That isn't the correct syntax for MT. Try this...
MT("RWI_HIGH(5,7)","[timeframe]",1) where timeframe is the timeframe you want to reference. For example 15 Minutes would be "15M" & therefore...
MT("RWI_HIGH(5,7)","15M",1)
Posts: 434
Joined: 6/6/2006
User Profile Ah that's very helpful Barry thanks I had assumed it was like the +1 or
+2 in the dialog box of indicators etc but did not realise the problem. Is there a document on this as I seem to have missed it. I will try the revised formula.
JB
Posts: 2309
Joined: 1/1/1900
User Profile Click OmniTrader Help in OT2020, then What's New followed by Multi Timeframe OmniScript.
Posts: 434
Joined: 6/6/2006
User Profile Hi Barry thanks I had not investigated the what's new section; getting a bit ancient I think! Having looked I have to say it is appears to me to be rather ambiguous and the MTR example at the bottom of the left hand column indeed uses the plain 1. and the central picture also whilst the code that you have used is set out at the left hand. Perhaps you should take a look. thanks for the assistance JB
Posts: 2309
Joined: 1/1/1900
User Profile MT is different syntax from MTR. MT is used for a specific timeframe reference while MTR is used for the Current+1, Current+2, etc syntax. Your original report was using MTR, so I recommended using MT instead until the next PR comes out which will fix the MTR bug.
Posts: 434
Joined: 6/6/2006
User Profile Barry Thanks for the explanation. Will it be legitimate to use either method once enabled or is that a 'wait and see'. Any home code will need to be compliant after the fix obviously?
Posts: 2309
Joined: 1/1/1900
User Profile You can use either, but due to the bug you reported, you would want to wait until the next PR to use MTR. IE, if you use the MTR version currently you'll have the issue you reported until the next PR.