1

##### Help Me / Re: Each Players Starting Table

« Last post by**Guzzler**on

*April 19, 2018, 10:09:23 PM*»

I've seen a couple of other posts asking similar questions. If the data is there, why not include this into the program?

1

I've seen a couple of other posts asking similar questions. If the data is there, why not include this into the program?

2

Not quite there... not sure what's missing, but it's only assigning points to the top 9.

3

Some, in a couple of sessions, but I've not really come to any conclusions. Other than I suspect the simple size of your DB could be an issue. When you add players from the DB, the entire list is rendered (thousands of players). Buy in 100 players, one at a time, and that list of 1000s is displayed 100 times. This should not be a problem, but we're talking about Internet Explorer here. I imagine that's exploiting an IE memory leak.

4

Hi Coorey,

did you have time to look into the files I sent you?

did you have time to look into the files I sent you?

5

Thanks! I'll try it out and let you know... thanks for the help!!

6

Yes, just as I forgot the decimal point previously, in my haste to fix it I added it incorrectly:

`5 + (5 * numberOfHits) + (switch(rank, 1, .33, 2, .22, 3, .12, 4, .08, 5, .07, 6, .06, 7, .05, 8, .04, 9, .03) * (10 * buyins))`

I'm also fixing this quickly. I apologize if there's yet another aspect I've overlooked.

I'm also fixing this quickly. I apologize if there's yet another aspect I've overlooked.

7

OK, here's what I came up with. I worked on this, realized I wasn't doing it right, started to re-work it, and had to leave for a while. Hours later I picked it back up, so I could be completely off in la-la-land at this point. Keep that in mind.

`assign(p, n - 9)`

assign(p20, round(p * .2))

assign(p30, round(p * .3))

round(switch(r,1,477.45,2,238.75,3,214.845,4,190.97,5,179.05,6,167.1,7,143.25,8,131.27,9,119.35)*pow(n,0.125))

+ if((r > 9) and (r <= 9 + p20), 95.49 * pow(n, 0.125))

+ if((r > 9 + p20) and (r <= p + 9 + p20 + p30), 47.745 * pow(n, 0.125))

+ if(r > p + 9 + p20 + p30, 23.875 * pow(n, 0.125))

First, "next 20%, 30%, 50%" implies that the*remainder* of the players, after the top 9, must add up to 100%. So those percentages are referring NOT to the total number of players in the tournament, but the players in the tournament minus the top 9.

So I found it easiest to compute the number of players remaining, and 20% of them and 30% of them. That makes the actual formula simpler. We don't need to compute 50% of them because that's simply what is left.

Essentially each line awards a "class" of player. Either you're in the top 9, or the next 20%, or the next 30%, or the next 50%. Any player will only qualify for one of those categories, so adding them up is fine, since 3 out of 4 will always evaluate to 0.

I hope the rest is self-explanatory. Let me know if there are questions. And check my math. The odds that I made a mistake are high.

assign(p20, round(p * .2))

assign(p30, round(p * .3))

round(switch(r,1,477.45,2,238.75,3,214.845,4,190.97,5,179.05,6,167.1,7,143.25,8,131.27,9,119.35)*pow(n,0.125))

+ if((r > 9) and (r <= 9 + p20), 95.49 * pow(n, 0.125))

+ if((r > 9 + p20) and (r <= p + 9 + p20 + p30), 47.745 * pow(n, 0.125))

+ if(r > p + 9 + p20 + p30, 23.875 * pow(n, 0.125))

First, "next 20%, 30%, 50%" implies that the

So I found it easiest to compute the number of players remaining, and 20% of them and 30% of them. That makes the actual formula simpler. We don't need to compute 50% of them because that's simply what is left.

Essentially each line awards a "class" of player. Either you're in the top 9, or the next 20%, or the next 30%, or the next 50%. Any player will only qualify for one of those categories, so adding them up is fine, since 3 out of 4 will always evaluate to 0.

I hope the rest is self-explanatory. Let me know if there are questions. And check my math. The odds that I made a mistake are high.

8

Thanks Corey. From what I've been told from our league manager, the formula above is not producing correct results. I'm being told that it's awarding points correctly for the first 3 spots, but spots 4-9 are getting too many points. Lets take a 28 player field for example:

28 Players * 10 points per player = 280 points

Place of Finish Points

1st 92.4 33%

2nd 61.6 22%

3rd 33.6 12%

4th 22.4 8%

5th 19.6 7%

6th 16.8 6%

7th 14 5%

8th 11.2 4%

9th 8.4 3%

Would you be able to please check the formula and see if you get these results. Much appreciated, trying to get this tested and working properly before Saturday's season kick-off!

Thanks,

28 Players * 10 points per player = 280 points

Place of Finish Points

1st 92.4 33%

2nd 61.6 22%

3rd 33.6 12%

4th 22.4 8%

5th 19.6 7%

6th 16.8 6%

7th 14 5%

8th 11.2 4%

9th 8.4 3%

Would you be able to please check the formula and see if you get these results. Much appreciated, trying to get this tested and working properly before Saturday's season kick-off!

Thanks,

9

correct. In the actual WSOP, it would be next 20% of ITM players, but I'm wanting to modify for our league.

10

Unfortunately no, because the application doesn't keep tracking of starting table, ending table, etc. Only current table.

You can find the starting table/seat in the Tournament History (press the History button on the Game tab). But you'd have to collate the data yourself.

You can find the starting table/seat in the Tournament History (press the History button on the Game tab). But you'd have to collate the data yourself.