New Software Announcement - SIXTH SENSE

[SixthSense]

[ QUOTE ]
[ QUOTE ]
There's a known conflict between SS and the AutoResizer AHK script.


[/ QUOTE ]

FYI, AutoResizer isn't AHK; I think Juk wrote it in C# or something.


[ QUOTE ]
There might be conflicts with other scripts

[/ QUOTE ]

Correct. It's my MiniLobby script (which resizes the lobby and moves a bunch of controls around). Just not sure why that would be a problem?

Btw, any chance you'll add an auto-BuyIn feature ( as in "Take Seat or Join Waitlist" )?

[/ QUOTE ]

As for the mini-lobby script, I know that Dan setup the Open Table script to click the buttons by x,y coordinate, because the class names would not be consistent. So scaling/moving those buttons could definitely cause a misclick for our script.

OK, the auto-buyin feature sounds like a good idea. I'll put it on our list. Thanks. [img]/images/graemlins/smile.gif[/img]

-Ben

[SixthSense]

[ QUOTE ]
Hey,

Is anyone else experiencing problems getting onto:

www.sixthsensepoker.com ???

[/ QUOTE ]

Ohh, that's not good. You can go here for now:

http://www.pokerdojo.net/sixthsense/

-Ben

[SixthSense]

[ QUOTE ]
[ QUOTE ]


No, you should not reinstall postgres, that might try to overwrite the ADO driver we install.

Like previously, did you reboot first before trying to reinstall SS? and shut down all other running apps?

-Ben

[/ QUOTE ]

i did restart after uninstalling, then installed it again w/o deleting the 3 files that were left from the sixthsense folder, same thing happened, i shut it off after 4 min. should i delete the 3 files after uninstalling, then restart, then install? how long should it take to load all tables with info from database?

[/ QUOTE ]

Next time its running and scoring tables, open up the Job Status window (its on the Main Menu). It will give an estimate (somewhat unreliable) of how long it will take.

The actual times depends on how big your database is times the number of players you need to get stats on (x Number of databases).

-Ben

[miked002]

I found something that should help the recent slowdown in Sixthsenth performance.

The Monster Jackpot slider bars on the poker tables take a heck of a lot of CPU resources (How silly can PartyPoker programmers be?) Pretty much pegged my CPU at 100% with most of the resources applied to the Partygaming.exe application

APerfect10 created an AHK script called DeMonster that removes the jackpot slider bar. There is another thread in this forum that discusses the script, but the direct link to the script is

http://overcards.com/wiki/moin.cgi/DeMonster

After running the script, the CPU time for Partygaming.exe went down to single digits. Sixsense performance is good again. APerfect10 - you the man!!!!

[Roland]

[ QUOTE ]
As for the mini-lobby script, I know that Dan setup the Open Table script to click the buttons by x,y coordinate, because the class names would not be consistent

[/ QUOTE ]

Ahh, I see. Well, looks like the coordinates ain't consistent either [img]/images/graemlins/smile.gif[/img] Could you maybe change it to use the class name anyway? It doesn't change that often, and there's nothing I can do to MiniLobby to make it work (I tried just leaving the button where it was, but no luck).

[ QUOTE ]
OK, the auto-buyin feature sounds like a good idea. I'll put it on our list. Thanks.

[/ QUOTE ]

Cool, thanks.

[teddyFBI]

I haven't seen a new version in a while, and now that I've had time to play around with SS a bit, I'm going to give you the top 5 most important features / improvements you should implement...at the risk of sounding a little arrogant, I consider myself to be pretty well versed in datamining and table selection, and while some of the suggestions in this thread (e.g. "Hey, add support for site XYZ right now!!!") would be useful to some extent, I think the below 5 are "must-have" features that will improve your product immeasurably...most of them are mentioned somewhere throughout this thread, but I wanted to put them in front of your eyes all in one place to underscore their importance.

1) Is the "data aggregation" tool that you've referenced before almost finished? Because I still think that SS doesn't deal with multiple DBs very well...e.g. in an ideal world it should treat all the data across all of your DBs as though it's all part of one giant DB...but it sometimes has difficulty displaying things as aggregates, e.g. the problem with it showing 1 hand played for player X, when X has only 1 hand played in the default DB, but several thousand in the multiple DBs (from which SS draws, but which aren't selected as defaults)

2) The ability to exclude a player from contributing to the table averages if he doesn't have a minimum number of hands played. This is probably the most frustrating imperfection in SS for me...I can't count the number of times I've gotten wide-eyed in anticipation for a table with a 34 VPIP average, only to open it up and find that it's actually all TAGs...then I go back to SS to see why it had such a high average VPIP, and I see it's because there were 3 players with VPIPs between 50 and 100, but it was only on account of having played 10 or fewer hands. A player that only has 1 hand played in one's DB will contribute a VPIP of 100 to the table average, throwing everything into chaos. Simply allow the user to select the number of hands a player must have played (across all DBs) in order to contribute to the table averages.

***By the way, I just read through the entire SS thread again, and saw to my surprise that SS actually WEIGHTS player data in calculating the table average VPIPs. This is a big no-no. I was involved in a protracted discussion about this when Playerview was first being developed, and the issue popped up again with PAH. Bottom line: VPIPs should NOT be weighted in determining table averages. If player A has 3,000 hands with a 22% VPIP and player B has 150 hands with a 55% VPIP, a weighted calculation will show a table average VPIP of around 25%...when what the user would find much more helpful is seeing a 37% avg VPIP (weighting each player equally). Now the one complication is if a player has only 5 or so hands and therefore has a completely unreliable VPIP like 0% or 100%...but the way that problem is addressed is via my #2 suggestion above...having a user-defined minimum # of hands for a player's stats to even count in the table avg calculations. I typically set that number at 50 hands...

3) The second most-needed feature, after the above, is the ability for a user to set the min. # of players that must be seated at a table in order for SS to even scan it at all. Personally, I don't care much about tables that have 1-3 players at them...so I'd like to tell SS to completely ignore them for the purposes of the searches. (Players who DO want to search for tables that short-handed can set their minimum lower than I will). This seems like a pretty straight-forward and useful feature to implement, and will make searches much faster too!

4) Actually, I take back the above: I think this one is the most important feature you could implement, but may not be as straight-forward as #2 and #3 above. It would really, really help if SS filtered data based on # of players seated, like PAH does. Here's an example of the problem. I have one huge full-ring DB (with 8-10 players / hand), and one huge SH DB (with 4-7 players / hand). SS draws from both. Sometimes an SS search will show a full-ring table, for example, with a 33 average VPIP...so it looks quite juicy. But then I'll sit down and see that it's actually mostly TAGs, and the ACTUAL table avg VPIP is more like 22, which is what PAH displays BECAUSE PAH FILTERS THE DATA IT DISPLAYS FOR ONLY HANDS WITH 7-10 PLAYERS IN THEM, because that's the filter I set up in PAH options. In other words, the only reason the avg VPIP looked so high was because SS is unable to differentiate between stats from shorthanded games and stats from full games. If you could somehow add this functionality (PAH has it), it would be very, very, very useful. I mentioned this feature earlier in this thread, and baronzeus brought it up twice...but I haven't seen you address it...have we explained it clearly enough? I'd be happy to discuss it with you further if/when you want to implement it.

5) Sorry, I couldn't resist one more suggestion. I think you should allow users to save "search profiles"...what I mean is that I like to play both LHE and NL, and have separate PT DBs for each. But doing one mega-search for all the LHE and NL tables using all of my DBs can take 20-30 minutes...so I like to do the searches separately, but this involves the arduous process of going in and disabling / re-enabling the DBs in SS's DB selection window. First off, I made this suggesiton before, but a much better feature would be to allow users to just set up each DB ONCE, and then just enable/disable it with the check of a check-box instead of having to manually input all the SQL settings. But I digress...I would like to be able to somehow "save" the parameters of my LHE search, so that I can tell SS to only search the LHE tables and draw from my LHE PT DB(s), and then when I want to search for good NL games (and without having to change any settings) tell it to search NL tables drawing from my NL DB(s).

Whew, alright, I hope you put these near the top of your to-do list [img]/images/graemlins/smile.gif[/img]

[SixthSense]

All posts concerning the waitlist joiner and the Autoresizer conflict - I'd just suggest disabling any join-waitlist features of autoresizer, or any other 3rd party software while using Sixth Sense. The 2 programs will conflict and a universal fix for that would be a pain.

As for the mini-lobby, I'll try finding the text of the button and making the opener click it that way. I should be able to make that work.

An auto-seat-joiner would be possible, and probably will be put on the list.



I'm leaning toward putting a bunch of hours into the table opener and maybe giving it its own interface and making it more functional. It started out as just a nice little enhancement feature, but I think there is demand for it to become more than that.


This is a bit further in the future, but definitely something we'd like to do.



Our list keeps growing! [img]/images/graemlins/crazy.gif[/img]

-Dan

[bhudson]

Just wanted to say all ted's suggestions are excellent. #1 is most important for me.

[Roland]

[ QUOTE ]
As for the mini-lobby, I'll try finding the text of the button and making the opener click it that way. I should be able to make that work.


[/ QUOTE ]

Cool, thx. IIRC it doesn't have text though, only class name.

[ QUOTE ]
An auto-seat-joiner would be possible, and probably will be put on the list.

I'm leaning toward putting a bunch of hours into the table opener and maybe giving it its own interface and making it more functional. It started out as just a nice little enhancement feature, but I think there is demand for it to become more than that.

[/ QUOTE ]

There definitely is.

[SixthSense]

Build 27 of Sixth Sense has been released:

Main Feature is:
Support for multiple Poker Sites!

<font class="small">Code:</font><hr /><pre>
- Added: Support for multiple Poker Sites!
- Game Filter dialog now has a list of available Poker Sites
- Table List now has a "Site" column
- Currently support PartyPoker, Absolute. FullTilt coming soon.
- Added: Clickable labels to the Table &amp; Player headers to bring up the popup menus
- Added: Converge Hands to Advanced Options, defaults to 300
- This is used to calculate fish score and NumData column, and weighting for AvgVPIP
- Added: Shark Multiplier to Advanced Options, defaults to 1.0
- Change to a smaller number (e.g. 0.2) to concentrate on fish
and not worry about other sharks
- Added: Hot key (Ctrl-X) to toggle table open method, also menu on Table Popup
- Changed: Server Table list is now updated in real time!
- It receives updates by table, rather than all tables in one list
- This means each table is MUCH more up-to-date, average age &lt; 2 mins
- Added: Link from main menu to our "Getting Started" tutorial web page
- Changed: Option for auto-showing the history file now defaults to True (new installs only)
- Fixed: Timezone problem for Updated column
- Fixed: Desktop Icon now uses the proper starting directory (so no temp files stored on desktop)
</pre><hr />

-Ben