Simulating shuffle tracking

[autonymity]

When making a shuffle tracking simulator an assumption might be made that for the duration of the simulation the player is playing the same deck of cards. These cards would start out "randomly" distributed, but with each shuffle thereon, to a degree, the shuffle tracker is determining how the shuffle will take place. This seems to be that it could be problematic. The reality is that no one is sitting down and playing the same deck of cards for a billion rounds. They are playing sessions where they encounter new random shuffles at the beginning of every session. This of course may not be an issue at all in the long run as the cards may simply drift back into a practically random state even if it was being cut by a shuffle tracker over and over, but to avoid it potentially being an issue I'm wondering if, when making shuffle tracking software, it would be better practice to add realistic "breaks" every x amount of shoes where the deck is reshuffled entirely randomly. Or alternatively if the tracker has no rich slugs to play have the cut be random before shuffling?

[iCountNTrack]

When making a shuffle tracking simulator an assumption might be made that for the duration of the simulation the player is playing the same deck of cards. These cards would start out "randomly" distributed, but with each shuffle thereon, to a degree, the shuffle tracker is determining how the shuffle will take place. This seems to be that it could be problematic. The reality is that no one is sitting down and playing the same deck of cards for a billion rounds. They are playing sessions where they encounter new random shuffles at the beginning of every session. This of course may not be an issue at all in the long run as the cards may simply drift back into a practically random state even if it was being cut by a shuffle tracker over and over, but to avoid it potentially being an issue I'm wondering if, when making shuffle tracking software, it would be better practice to add realistic "breaks" every x amount of shoes where the deck is reshuffled entirely randomly. Or alternatively if the tracker has no rich slugs to play have the cut be random before shuffling?

CVdata randomizes the shoe using an RNG after a number of shoes were shuffled using the specified real shuffle.

[Overkill]

iCountNTrack,

I am unclear about what you mean. I assume of course you are referring to the "Real Shuffle" option. And when you mentioned randomizing the shoe, are you referring to the option in CV Data wherein one can choose when (I believe it is the "number of shoes" before which) new cards are introduced?

[iCountNTrack]

iCountNTrack,

I am unclear about what you mean. I assume of course you are referring to the "Real Shuffle" option. And when you mentioned randomizing the shoe, are you referring to the option in CV Data wherein one can choose when (I believe it is the "number of shoes" before which) new cards are introduced?

Basically the sim engine is making sure that the simulation is realistic so you are not "stuck" in the initial shoe state and mimic the real case scenario where the casino washes the cards after a certain number of plays, or if you switched table.

CVData does the same thing, where after a certain number of shoes where the inputted "real shuffle" is used to shuffle the shoe, the shoe is totally randomized using a RNG and then the real shuffle is turned on for another set of shoes and so on

[Overkill]

iCountNTrack,

Now I am really confused. How can one shuffle track with a randomly generated set of cards, especially when I don't know where the last 'real shuffle cards' shoe ends and the first shoe of new, randomly generated cards begins?

Are you saying the "Real Shuffle" option in CV Data is not 100% a real shuffle? For years I have been analyzing the log data trying to make sense of the cards.

You said above: "Basically the sim engine is making sure that the simulation is realistic so you are not "stuck" in the initial shoe state and mimic the real case scenario where the casino washes the cards after a certain number of plays, or if you switched table(s)...CVData does the same thing, where after a certain number of shoes where the inputted "real shuffle" is used to shuffle the shoe, the shoe is totally randomized using a RNG and then the real shuffle is turned on for another set of shoes and so on"

I don't understand what you mean by "the casino washes the cards after a certain number of plays, or if you switch tables." Casinos don't wash the cards very often. In order to address the realistic condition of the casino washing the cards once or twice per day or whatnot, CV Data addresses that with the "Shuffles before new decks" feature found under "Nuances."

I have been operating under the assumption that when I ask CV Data to generate a log of rounds broken up by shoes, I am looking at the same shoe containing the same cards (until I ask CV Data Real Shuffle to introduce "new decks") that are being moved around (shuffled) in the same (hopefully predictably, in some small way) manner as a human dealer.

We all know most casino shuffles with human dealers cannot take the time to fully randomize the cards

Last night I sat at a casino table with only human dealers, and I played roughly 15 shoes consecutively. There was no wash of the cards. This is what I have been assuming CV Data has been mimicing all this time. Is this not true? If not, again, how can one shuffletrack with cards that are unpredictably randomly generated?

[Norm]

There is an option to set how often the cards are randomized. You can set it to 10,000 shuffles if you wish. But casinos do wash the cards when they break open new decks. There have been casinos that waste time washing the cards more often.

[Overkill]

Thanks, Norm. I think I misunderstood iCountNTrack. So, I believe you are indeed both referring to the "Shuffles before new decks" button under "Nuances," correct?

[Norm]

Yes.

[Overkill]

Thanks.