Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - shushs

Pages: [1] 2 3
1
Help Me / Re: Point calculation seems... off.
« on: February 20, 2017, 07:19:30 PM »
Once again Corey, you nailed it. I had 2 set for "points for bust out". Thanks for fixing my math.

2
Help Me / Re: Point calculation seems... off.
« on: February 20, 2017, 09:23:11 AM »
I will try your recommendations, you haven't led me astray yet... The summary tab, in the scroll box, shows points awarded and place finished for all players. I only grabbed the top 5.

3
Help Me / Re: Point calculation seems... off.
« on: February 20, 2017, 04:55:14 AM »
The "Summary for the top 5 players" comes from the summary tab. It matches what is provided when I export the tournament. I do have points for hit set, but I think it is set to 1. Even if Brandon got a point for every hit, that still only takes it to 43. They also get one point for buying in.

I agree that the formula yields the same results. I am trying to figure out why TD gives me this unexpected value.  FWIW, I am running 3.4b2.

If you would prefer, I can provide the TD file, and the export. I'd prefer not to post it on the forums though because it has players full names and email addresses.

4
Help Me / Re: Point calculation seems... off.
« on: February 18, 2017, 01:32:22 PM »
Well, in the first case, brandon s awarded 50 points and when i do the math, he should have gotten 37. So, I either have something wrong doing it manually, or i am missing something that the Td software does. Can you show me your application of the math? Maybe i have a parenthesis in the wrong place.

5
Help Me / Point calculation seems... off.
« on: February 17, 2017, 07:22:16 PM »
We have been running, trusting the output from the 'Summary'and export functions. But when I check them manually, there is quite a discrepancy.  It is quite possible that I am missing something.

For example, our last tournament had 15 players. Using the following formula,

Code: [Select]
(sqrt(n*bc*bc/tc)/sqrt(r+nr))+(2*nh)
n       = number of players
bc      = buyin cost
r       = rank (place)
nr      = number of rebuys
tc      = total cost
nh      = number of hits (bounties)

From the Summary for the top 5 players, I get the following points:
Code: [Select]
Brandon L      50.00
Adam            22.68
Cap'n (ret.)   19.43
Buddy          25.50
Slick            12.18

None of these players re-bought, nor do we allow add-ons. The buy in is $50 with a  $10 bounty.
Code: [Select]
Brandon Adam Capín Buddy Slick
n 15 15 15 15 15
bc 50 50 50 50 50
r 1 2 3 4 5
nr 0 0 0 0 0
tc 60 60 60 60 60
nh 6 1 1 3 0

Points 37.00 19.68 16.43 18.50 11.18

These numbers obviously don't match up. Can I get a pointer or two... so I can understand where my issue(s) is/are??

6
Your assessment was correct.   I run a "$50 + $10 bounty" tournament and a $20 toward ToC. So, I had it set to a buy in of $50, a $10 bounty, and a $20 rake. So, my payouts were $20 * number of players short. Got it resolved though. Thanks again!

7
OOOh! I think I may have figured it out!! I need to set my buy in to $70, with a $20 rake. Boom! Bob's your Uncle!

Yes?

8
I recall seeing some posts a while ago about keeping money out for a TOC. IIRC, the suggestion was to use the Rake field. I did that last year, and TBH, I think I shorted some people.  An astute player at last week's game said "There is $800 in the pot, but you are only paying out $600, why?" Well, I looked and he was correct. the payouts totalled $600, there were 15 players, plus one rebuy, at $50 per. That equals $800. I have been using the rake field to take in the extra $20 from players each buy in to help inflate the ToC we run. The top 10 players (points wise) get to play a $100 buy in tournament with the extra from all the buy ins added.

When I collect the money from each player, I grab $80. $50 to the current prize pool, $10 for a bounty chip, and $20 for the ToC.

I had already removed the $300 from the $1200 total intake. But I in order to get the prizes to work, I had to put in a 'House contribution' of $200. This is going to throw my prizes off each month (if I even remember to do this). Did I do something wrong? Is there some other field I can use instead that doesn't get subtracted from the current tournament's pool?

9
Beta Testing / Re: 3.4 beta 2
« on: August 15, 2016, 03:53:27 PM »
Well, if it is Windows 10 that is the culprit, then please excuse my finger pointing. I've had and used your product for quite some time, and I am extremely happy with it. I will see if I can dredge up an older Windows machine and test b2 out on it.

10
Beta Testing / Re: 3.4 beta 2
« on: August 12, 2016, 06:01:44 PM »
The answer may be in the forums... but is there a way to roll back to 3.4beta1? The 'key press' stutter, and having to click multiple times (some times) is just not conducive to running a tournament. I have been struggling for a while, but it finally has me beaten. 

11
General Discussion / Player export --- request
« on: February 12, 2016, 02:59:47 PM »
Corey, I am wondering if there is a way to build more custom queries from the 'database'. What I am looking for is essentially a way to query things like 'last time played', 'total tournaments played', 'most frequent <timeslice> played', etc. IIRC, you have stated that this isn't really stored as any type of "database" but rather reads in the appropriate files and builds a temporary DB in memory, then allows for export from there... If I am correct in that thinking, then I'll have to find another way.. I have been running this software for quite some time now, and have many players that have come and gone. I'd like to archive those that will never return, and get some cool stats on those that still play. Ideas? Any chance the 'next' version will have a MySQL/PostGres back end?

12
Help Me / Re: Latency
« on: January 23, 2016, 04:26:55 PM »
I had/have the same issues CruiseLite. I will say that after installing more RAM into my computer, the problem appears far less often. I am not suggesting that you spend more money on RAM, but more RAM is always good, especially under windows. I wonder (and may actually test) trying to allocate a specific amount of memory for the TD software and see if that helps... Right now, I am stuck in SnowZilla 2016, so I may get to it.

13
Beta Testing / Re: 3.4 beta 1
« on: January 17, 2016, 02:41:27 PM »
I understand that this may not be a priority, but I just wanted to add more information, in case it helps...

Ok, ran the beta for the first time yesterday and here is what I found:

    <SNIP>
    • Has the memory requirement much increase in this new beta? I have experience many BLACK dialog boxes and even transparent one while attempting different duties throughout my tournament. Busting out players was a biggy: Right-clicking would produce a transparent dialog, you had to guess where the "Bust player" option was and if you got lucky, you would then be presented with a black window (offering you to check other players to bust) where again you had to guess where the "OK" button was.

      Later on in my tournament, I notice the whole app slowing down (countdown clock, scrolling info) where I simply decided to restart the whole thing (computer included). everything went fine after that... For information, TD is running under Windows 8, 8 Gig RAM 64 Bits, Intel Core i5-3230M CPU @ 2.60 Ghz
I can confirm that I have seen this since running the BETA also. I did purchase more RAM for my computer, and it hasn't been _as_ bad, but many buttons require me to "push" them twice. Personally, I think it is tied to the transitions. I turned them off prior to my memory upgrade, and saw some improvement, but I think the timing/logic tied to certain events is a component. (good finger pointing here) The reason, when typing / editing, just as the transitions fired, I'd lose keystrokes/clicks, then it'd be good until the next transition.
I am running an AMD A8-7410 APU / Radeon R5 with (now) 16GB RAM on Windows 10. My tournaments are smaller in size (less than 30 players) and I now lock the screen on the tournament screen. If there is anything I can do / test to help out... I'd be happy to.

14
apologies... typo

if (rank <= 15, log((n+1)/r),0)

Had the parenthesis in the wrong place.

15
Corey was able to help me get on with my top n calculations.  If I understand your request, you give points to the top 15 finishers in any given tournament.

I would think you need to modify your points calculation based on that criteria.

points = (if rank <= 15, log((n+1)/r), 0)

That should only give points to the top 15 players.
With each tournament keeping it's own score, and if you have player tracking turned on, then it would update the total points for a particular player based on their points for that particular season. <- sure hope that made sense.

I certainly hope this is proper advice.

Pages: [1] 2 3