CVCX/CVData Suggestions List

1) With regard to CVData, where do things stand with creating a feature which allows the backcounter to abandon tables while observing and specify a lag time for these scenarios? This is an important aspect to wonging simulations which should not be discounted. Would you remain behind at a table where the TC = -3 or would you move on? SCORE is certainly being understated by omitting this feature.

2) Another suggestion is spreading to multiple hands during the final round of the shoe. Just put a radio button there which allows the user to select the option and specify the wager and number of hands for any given TC.

3) Lastly, the ROR/Goal simulator should be expanded to include a feature which allows for expenses. For every 'X' number of rounds played, the user should be able to specify a fixed penalty of 'Y' units. This will surely exacerbate ROR while mitigating Goal. In the real world we all have expenses that are associated with our play. Such expenses should not be neglected in the simulations.

For others CV users, what do you guys think? Feel free to add to the list as QFIT keeps his products live!!!

MJ

You'll need to define this better.

Funny, I was just thinking about this today. I was thinking of a much harder way of doing it requiring two betting strategies. I think I simpler may be better here.

Have to think about how to accurately work this into variance.

Suggestions are more than welcome.

i know you won't do it but i'd like to see cvbj able to run on auto pilot.:devil::whip:

RoR suggestion

Couple more:

1. It is annoying to time and time again input your BR, var, EV etc into the RoR tool every time you reopen it.
Would be great if instead of the dummy values, it would retain the last values used. Or pick some up from the last sim run.

2. Have mentioned this a few times... ESA requires indices for surrender for small totals as well (4,5,6,7), it's a bit of a pain to use CD for this, would be nice to have them as a simple total.

D.

You're right.

Planned

That's more of a problem as I would need to convert all users' current strategies.

If you take a look at the BJA3 ODP study you will understand what I mean. Basically I want a feature in CVData that will permit a WiWo simulation that takes into account entry and departure points based upon penetration and factor in # rounds missed when Force Shuffle on Exit is selected. The software can handle all of this already, I know.

But what about those instances while observing a shoe in progress when the count goes deeply south? CVData does not currently have a feature where Force Shuffle can be applied at a certain TC while observing a shoe is progress. This very feature is what I am requesting. Additionally, the user should be able to impose a lag time to account for rounds lost to find a new table to observe.

You are already half way there, you just need to add the other half.

MJ

In CVData I would love to see a graph which shows winrate, std dev, SCORE or whatever the user specifies vs. # of simulation rounds in real time while a sim is running. It would be nice to see how the values converge as the sim is running to give you an idea of how many rounds you should run or how accurate the results were when you stopped. Sometimes when I'm doing a lot of messing around I run a bunch of short sims to ballpark the results, and only experience tells me how long I should let the sim run before stopping.

It would be great to integrate CVCX with CVData more. For example, it would be convenient if you could generate a betting strategy in CVCX and then have a button to import it directly into CVData, along with the rules used.

In CVCX instead of "Play two hands", let us specify how many (Play __ Hands)
It would also be nice to only apply multiple hands to positive counts, since that's the only time I would play multiple hands, but based on my other CVCX thread it sounds like that would be too complex for post-sim calculations.

In CVData for shuffle tracking, allow us to cut an ace to any player at the table. Right now only first base can get it, but in real life I've been able to occasionally cut myself an ace in third base (just requires cutting above a few extra buffer cards).

Implement CVCX's optimal bet calculating algorithm into a tab in CVData results so we can get an optimal betting ramp for any detailed situation we simulate.

You can use the Find Table Delay option to create a time lag. I have to look at what Force Shuffle would mean when not playing.

Have to think about this.

I added this to CVBJ. Should be able to add to CVData.

Play two hands is an estimate. I don't think I want to stretch the estimate further.

Multiple hands in positive counts is supported now, but only for balanced strategies that use Truncation or Flooring.

Have to look at this.

This is planned. Of course it cannot be done in the case of some cover play or other complex betting strategies.

One way to do it might be to simply allow a bet of 0, and infer that the player is receiving no cards when the bet is 0.

This can be currently faked out using a play all, force shuffle strategy and going to the Cumulative True Count table, pointing the arrow downward and seeing your advantage and win rate if you only play counts above some count. But it doesn't do the SCORE and SD calculations for you, and isn't workable in the Multi-Tracking simulator because it never really lets you force a shuffle.

Thought about this again. I don't see what this gains you. Problem is, if you tell it when to give up backcounting a table, this still doesn't tell you how long it will take to find a table that is shuffling. Depends on open tables, crowd conditions, dealer speed, player speed. The way I handle this now is to allow the user to set a Find Table lag based on experience. Suggestions for improvement are welcome.

The gain is obvious. Why do backcounters stop observing a given table when the count dives? Answer: The count will most likely not recover to warrant entry into the shoe. It becomes more profitable to find a freshly shuffled table.

Right. That is why you give the user an option to specify how many rounds it would take to find a freshly shuffled shoe. The user already has the option to specify this number when wonging out of a table, now just extend it to include those instances when we stop observing a shoe in progress.

See above.

Have to look at this again. I was using the table lag to include both lags. This also supports those that count two tables at once. It might be more accurate to pull this out of the table lag.

i apologize, if i asked this question before.

does cvdata have the capability to make a scientific investigation of the quantitative value of approach's such as those described by Leon Dubey in his book No Need to Count?

i'm already know that you have stated his methods only provide a tiny advantage if any at all.

the thing i'm wondering is if cvdata is capable of making such a determination.

But does CVdata currently allow the backcounter to depart a shoe while observing in the first place? Or is this feature just implied...the departure points while observing are the same as those for playing. Just as the lag times for playing are the same as those for observing, I guess?

All this is news to me.

No. Currently, you just set the table find time to what your experience shows you is the total time it takes between leaving a table and finding a table, given casino conditions.

What is the method?

But if the counter never departs while observing a shoe, then what did you mean by the above?

What I mean is that the Table Find Time is ALL of the time between stopping play and starting either play or backcounting at another table, whatever the reason.