Originally Posted by
Cacarulo
Hi k_c,
I don't realize what the index would be in each case. Maybe you can tell me a bit more about those tables. Thanks.
Sincerely,
Cac
Hi,
The data is the same format as my previous data for insurance which lists minimum running count insurance indexes where ins EV >= 0 for a given number of cards remaining. If the next cards remaining value in the list has the same RC index as the previous it is skipped. When the index changes that cards remaining/RC index is displayed. This continues until there are no more cards remaining.
An example I think you're familiar with is single deck generic insurance-
Code:
Count tags {1,-1,-1,-1,-1,-1,0,0,0,1}
Decks: 1
Insurance Data (without regard to hand comp)
No subgroup (removals) are defined
**** Player hand: x-x ****
Cards RC TC ref
48 1 1.08
47 2 2.21
38 1 1.37
2 0 0.00
1 1 52.00
You don't care about the value for 48 cards because ins EV = 0 (no advantage) but I list it anyway since I list EV >= 0.
RC index for 39-47 cards = 2
RC index for 3-38 cards = 1
I have the option to create subgroups within the main groups of a counting system which consist of any combination of cards within the main group. The number of cards removed from the subgroup is input directly and is constant.
The difference in the data in this thread is that I have included the option to side count aces as a subgroup. This is not the same as specifically removing aces. The minimum input for single deck generic insurance side counted ace subgroup removals is 1 since insurance requires at least 1 ace. The max is 4 so input range is 1-4 and whatever is input is constant. If hand composition was A-2 instead of generic, ace subgroup removal range would be 2-4.
So what I have done is to input 1,2,3,4 ace subgroup removals respectively which fixes number of remaining aces to 3,2,1,0 for all number of remaining cards before generating RC indexes.
Hope that is at least somewhat clear. This simple case just fixes the number of aces present before determining RC indexes in each case.
Edit: I may have found an anomaly in this. I have to find time to check it out.
Edit #2: I found an error in my code for subgroup side count. Different data below.
exactly 1 ace played (3 aces present)
Code:
Count tags {1,-1,-1,-1,-1,-1,0,0,0,1}
Decks: 1
Insurance Data (without regard to hand comp)
Side counted subgroup removals (no input defaults to minimum):
{1} (1 to 4): 1
**** Player hand: x-x ****
Cards RC TC ref prob ace prob ten
48 1 1.08 3/48 1/3
47 2 2.21 3/47 .34043
39 3 4.00 3/39 .34490
27 4 7.70 3/27 .35036
15 5 17.33 3/15 .36451
exactly 2 aces played (2 aces present)
Code:
Count tags {1,-1,-1,-1,-1,-1,0,0,0,1}
Decks: 1
Insurance Data (without regard to hand comp)
Side counted subgroup removals (no input defaults to minimum):
{1} (1 to 4): 2
**** Player hand: x-x ****
Cards RC TC ref prob ace prob ten
48 -1 -1.08 2/48 1/3
47 0 0.00 2/47 .34043
41 1 1.27 2/41 .34395
30 2 3.47 2/30 .34911
18 3 8.67 2/18 .35896
6 4 34.67 2/6 .43096
5 3 31.20 2/5 .33889
4 4 52.00 2/4 .5
3 3 52.00 2/3 1/3
exactly 3 aces played (1 ace present)
Code:
Count tags {1,-1,-1,-1,-1,-1,0,0,0,1}
Decks: 1
Insurance Data (without regard to hand comp)
Side counted subgroup removals (no input defaults to minimum):
{1} (1 to 4): 3
**** Player hand: x-x ****
Cards RC TC ref prob ace prob ten
48 -3 -3.25 1/48 1/3
47 -2 -2.21 1/47 .34043
46 -1 -1.13 1/46 .34783
45 -2 -2.31 1/45 .33573
44 -1 -1.18 1/44 .34455
32 0 0.00 1/32 .34742
21 1 2.48 1/21 .35574
10 2 10.40 1/10 .38311
exactly 4 aces played (0 aces present)
Code:
Count tags {1,-1,-1,-1,-1,-1,0,0,0,1}
Decks: 1
Insurance Data (without regard to hand comp)
Side counted subgroup removals (no input defaults to minimum):
{1} (1 to 4): 4
**** Player hand: x-x ****
Cards RC TC ref prob ace prob ten
48 -4 -4.33 0 1/3
47 -3 -3.32 0 .34043
35 -2 -2.97 0 .34683
23 -1 -2.26 0 .35263
12 0 0.00 0 .37162
3 1 17.33 0 .56481
2 0 0.00 0 .41451
1 1 52.00 0 1
k_c
Bookmarks