Thank you for your response, I appreciate it. Some notes:
Tournament auto-detect is a system that is constantly improving. It takes everything at hand and figures out the best possible description of the tourney. For a few sites, hand histories contain very accurate data and auto-detect may be less accurate. Certainly for PokerStars, auto-detect should be used.
For PokerStars it's sometimes impossible for auto-detect to distinguish between a 2, 3 and 5+ table when you're eliminated in the early rounds. In the auto-detect dialog, you can coach the system by telling it what to use (rather than a generic MTT) when it's unsure. But yes, I see Audit file data can help here.
I don't understand how I can coach the system. I am also not aware of any auto-detect dialog.
You say that in some tourneys it's impossible to autodetect whether a tourney is a 2,3, 5+ table SNG if you get knocked out in the early rounds. I agree, this is the case. Crucially, no matter how good you are, you will get knocked out in the early rounds a certain percentage of times, so you will have a certain percentage of tournaments (5-15%) not getting detected.
But why is this a problem? We get 99.9% accurate information by importing emailed tournament summaries. This is a solved problem. Why are we trying to fix it with a method that we know won't work as accurately?
-problems combining Speed and Table filters. Yes, the table filter is seeking an exact match, so you'd need to click ALL the table types that contain "MTT" AND "Turbo" rather than Table:"MTT" and Speed:"Turbo" to get the desired result. We will fix this so it is more intuitive.
I agree. And I wanted to say it earlier. It does seem as if a large problem with autodetection is that it's trying to categorize every single tournament precisely. In that goal, it's failing. But if it was trying to just fill certain pieces of the puzzle complemented by other methods, then it could be useful.
PS Audit Files: Please understand that PokerStars Audit files have gone through some recent changes. When support was originally written there were less accurate details. We will do our best to improve audit file import. Code "3063" sure looks like a bug in the audit file, but you're right, it should be supported.
I agree. I know that a PS history audit didn't always contain as much analytical information as the one I posted. I was looking at an audit file I had from last year and it I don't think it contain as much information as the file from where I posted the screenshot. And certainly the code 3063 wasn't obvious to me either; I had to email PS support some time ago in order to find out what it was.
I do have to note that things have tremendously improved the last couple of years. These days our winnings are reported accurately. A couple of years ago, we couldn't import rebuys and addons. Now, we can and it just works.
I also understand that when PT3 introduced auto-detection, PS audit files hadn't yet been introduced by Pokerstars. So with what your development team knew then, trying to find out info through auto-detection was the reasonable course of action.
But here's an important reminder. Often times people and organizations set a course of action, but at some point the underlying data which made following that direction the logical choice change... But instead for those people and organizations changing their direction based on the new underlying data, they keep on going the original course just because they are so focused on the process of what they re doing. It's a mistake I ve often done in my life and you should think carefully if you re doing it yourself. I am not saying you are btw, because I truly don't know all the data myself.
Case in Point #2 & #3: We do attempt to decode table info from audit files. The problem is that other information like seat count is not supported, so importing audit files with "Overwrite Tourney Summary Data" should make table type more accurate but might make other data inaccurate. I will take a look into this area and see what I can do. BTW: PT4 tourney auto-detect has very accurate rebuy and addon detection for all sites.
What do you mean by seat count? And just to be clear, I would not check the option to overwrite tournament data when I am importing from a PS audit file. I would just let it import complementary data.
Just for the record, based on the information we know and the tournaments I play, this is how the process would look ideal for me.
1. Step one.
Import hands through auto-import.
Leave the autodetect on for players who perhaps have use for it. Perhaps let it do stuff like detect whether a tournament is a turbo or not.
2. Step two.
Import emailed tournament summaries with the option to overwrite tournament summary data checked.
This will give me:
a. Accurate gauge of my winnings. (the most reliable method of all it seems to me, and really accurate 99.9%)
b. Accurate gauge of my finishes and the number of players who entered a tourney. Again, the only method where you can get accurate data for these parameters.
c. Accurate gauge of the table types I play, whether they are 180s, 45s, MTTs, MTT Sats or Mtt bounties.
3. Step three.
Every month or so, but really whenever one feels like, import player history audit from pokerstars. This time, I would leave the option to overwrite tournament summary data unchecked.
This method would add -not overwrite-
the following information to tournament files:
a. How much I paid in rebuys and addons. (already does, very accurately)
b. How much money I won from bounties in knockout tournaments.
c. Which tournaments are turbos and which regular speed, which tournaments are rebuys and which aren't.
If those steps are established, I don't think I ll be missing any relevant data point (buyins, winnings, rebuys, addons, bounties would be counted) and all relevant filters would be working properly (MTT, MTT-SNG, MTT-SAT, Speed, Rebuys).
Again, thank you for your time.
Last edited by leviathan74; 11-10-2011 at 01:07 PM.