dcbclimb: CVData: half card values (red 7)

[dcbclimb]

Can anyone tell me how CVData handles counts like Red Seven where only the red 7's are counted. Does it count every seven as +.5? If you count every seven as +.5 instead of counting red sevens as +1 wouldn't the variance/ standard deviation be diminished? Consider a single deck where you see the 2 red sevens first- you'll be over-estimating the edge. In the long run this will be balanced out by the times you under-estimate the edge when you see the black sevens first. But as far as simulations go wouldn't counting every seven as +.5 decrease the fluctuation/ variance versus counting just the red +1 sevens?

[Norm Wattenberger]

If you use the "Half point support" option, it can count sevens as .5. If you use the "Separate Red/Black values" option, it can count only Red 7's.

[dcbclimb]

Software is on it's way or I would have known. Does it also have an option to count 10's different than say Kings?

[Norm Wattenberger]

> Software is on it's way or I would have known. Does it
> also have an option to count 10's different than say
> Kings?

No and that's not likely to be added. CV Blackjack supports this for practice. But I really don't like the concept. Obviously you can get close by using the same technique most sims use to estimate Red7 -- with the attendant loss in accuracy.