MurreyMath

Discussion in 'Educational Resources' started by traderbambu, May 18, 2002.

  1. Yeah. The 8 ball gives it a good run for ya money.

    Hey, Oddi! I thought you had gone,man! Or that they had caught ya!!! :)

    I'm getting a 'sell the s+P below 814.5', 'buy it over 834' feeling.

    What does the great Murrey Line Method predict?
     
    #491     Mar 6, 2003
  2. pretzel

    pretzel

    wd78,

    This script produces the same lines as in your chart but dont know if it will still do for the the next frame.

    pretzel
     
    #492     Mar 6, 2003
  3. That was really good fun dude!
     
    #493     Mar 6, 2003
  4. colion

    colion

    Looks OK. Suggest, however, checking it out with other time frames and a variety of stocks with different volatilities. That maze should find any problems, if there are any. I have not looked at your code, but if you are concerned about stability between frames then just watch it for a while. However, my experience is that changing volatility and time frame should be enough, absent anything unusual in the code.
     
    #494     Mar 6, 2003
  5. If you haven't seen discrepencies, then you're not looking at enough different price ranges. As I said, the Kruzel algorithm WILL produce the correct #s part of the time, but it will always produce the wrong #s for a bunch of different price ranges. If you're looking at mostly daily charts for a handful of symbols you might not notice it because the price ranges don't change enough or don't represent a large sample of diverse price ranges. It's more obvious when comparing dozens of symbols using several different frame sizes and different intraday timeframes throughout the day for a few days - then you end up seeing thousands of different price ranges to compare the results over.

    If you don't believe the error rate I noted, that's up to you, believe what you want - but you missed the actual message. The Kruzel algorithm is wrong 100% of the time when presented certain price ranges - the 25%+ error rate came from hitting those price range conditions (in which the algorithm fails) in about 25% of the cases. It's possible that if it was done again over a different set of days (and thus a different sample of price ranges) it might be 10% or it might be 50%. Frankly after seeing that it wasn't reliable, I didn't bother trying it out over a whole year's worth of intraday data to see what would happen.

    If you're looking for a example of an error - compare the WL and TS charts that someone posted earlier at http://www.elitetrader.com/vb/attachment.php?s=&postid=214104 and http://www.elitetrader.com/vb/attachment.php?s=&postid=214109 to the one attached to this message.

    Same day (3/5), same 64 bar frame setting - but the WL and TS #s are wrong. Someone else previously posted a chart using eSignal that was noted at the time as having the wrong #s (had nothing to do with colors as the person later suggested - the #s were just wrong).
     
    • mm.gif
      File size:
      12.1 KB
      Views:
      154
    #495     Mar 6, 2003
  6. colion

    colion

    You are behind the times. I pointed out those errors yesterday, and couple of messages ago the prezel noted that the code was corrected. As I noted just above your message, the MMLs are now correct.
     
    #496     Mar 6, 2003
  7. Yep, I missed the revised QQQ example. But try SPY:

    Pretty obviously wrong.
     
    #497     Mar 6, 2003
  8. Here's what it should look like (uses 3/5 as the last bar like WL did).
     
    #498     Mar 6, 2003
  9. colion

    colion

    Yes, I agree that Pretzel has a coding error, which is why I suggested he check other stocks and volatilities before assuming everything was OK. However, that does not mean that a correctly coded program will not produce the same result. For example, the attached shows the correct MMLs in AmiBroker. And if it can be coded correctly in one program it can be coded correctly in another.
     
    #499     Mar 6, 2003
  10. Hi Wappers, have you made it to Stockholm yet???

    Long yesterday at 827, is what the system says.
     
    #500     Mar 6, 2003