Jeremy G. Konstenius
Quote: JeremyI do allot of research but no real betting. This is one of my systems that made it through 1 million spins. It made 788 dollars at the end of 1 million spins. The largest bet was 208 dollars. The system used D'Alembert to break even on betting zero. The break even was raised 1 dollar every 10,000 spins. A system that can withstand large amounts of spins has to be extremely conservative. Any way here is the equity line.
Jeremy G. Konstenius
These charts prove nothing. All betting systems will jump up and down, and all will end up slightly up or down.
Jeremy
I assume smallest bet is $1, so largest was $208, so the spike at 880,000 spins is a series of good results to get back again after a series of bad results?
Does your system bet size dependent on the bank roll (just curious)?
Quote: JeremyThe system did not break any of the rules of the BluJay or Wizards challenge other than that I did not do 1 billion spins. A system that can withstand that many spins even 1 million spins is going to be very boring with an incredibly slow growth line. That was in effect a 10,000 dollar draw down which is when the system was as high as 208 units. The reason it looks like a spike is because the graph is 1 million spins. That draw down happened over hundreds of spins.
Jeremy
I believe the point that he was making is that the graph clearly seems to go below zero at the relative min. there. What was the value of that relative min? Also yeah, looks like this system is pretty ineffectual to me, too, based on the results. There is no real progress in 1,000,000 spins, but alot of real close calls to hitting 0. This looks like a huge loss waiting to happen, supplemented by small wins. That has pretty much always been true for these types of systems.
Quote: DJTeddyBearFor the benefit of those that needed to scroll to read it:
Admin note: I believe I have fixed the problem with threads containing large images that need to be resized. Or what I should say, is that I have worked around the bug in Internet Explorer 8 which causes the problem.
(In case anyone is interested: IE8 does not fully respect the max-width CSS property applied to images inside a table cell. The workaround is to place the image inside a <div> which has an explicit width set.)