Quote:
Originally Posted by Djay
Did something come out of this? Im having the same problem - Even though im running full ring color coding i get 87% uncolored with reason: Wrong game size.
When someone isn't color coded, there is an explanation for each definition. Therefore if you're using the default color definitions, you will see "wrong game size" for every player since there are versions for 6 max in addition to the full ring versions.
If you've removed the 6 max definitions, then you'll still get wrong game size if that person has played a single hand with 6 players or less.
Example:
testing color definition: Whale
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: vpip too small
testing color definition: Whale
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: wrong game size
testing color definition: Whale
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: wrong game size
testing color definition: Whale
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: vpip too small
testing color definition: ABC
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: vpip too small
testing color definition: ABC
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: wrong game size
testing color definition: Calling Station
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: vpip too small
testing color definition: Fish
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: vpip too small
testing color definition: Fish
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: vpip too small
testing color definition: Fish
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: wrong game size
testing color definition: Gambler
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: vpip too small
testing color definition: Rock
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: wrong game size
testing color definition: Rock
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason:
vpip sample too small
testing color definition: Tag
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: vpip too small
testing color definition: Tag
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: wrong game size
testing color definition: Tornado
Found stats for : Holdem game size Medium OUTPUT: FAIL - reason: pfr too small
Conclusion: when someone isn't color coded it is because they don't have enough hands. Just like when you use hem autorate, not everyone has an icon. My recommendation is find a player who isn't color coded even though you think he should be, select all your color defs, right click->test and then analyze his stats versus the fail explanations and adjust your definitions accordingly. It should really only take a few minutes imo
Quote:
Originally Posted by lennois
Further to my issue, notecaddy creates notes fast as long as it's the first run through the database (like 50-100 HPS or something with my defs)
However, as soon as I reset the notes and re-run it on that DB it slows down dramatically (1-3 HPS)
Any ideas why this would be?
I hadn't seen this issue before. On the first run, NC would be doing inserts and then subsequently it would do updates. How many hands in your database?
I would recommend looking at the official hem recommendations for performance increases (not all will apply to you obviously)
http://forums.holdemmanager.com/mana...ease-tips.html
edit: new feature as of 5/18 - right click any note definition(s) and click "history" to see each instance where it was created for someone
Last edited by SretiCentV; 05-20-2011 at 06:43 AM.