Whats wrong? diff results for diff ranges

[leonick]

Hey there.
I have created about 40 correct stats about now. But his time with range...strange things happen.

Let me try to explain short:
The specific cbet stat is working correctly.
I wanted to split in RANGE now.
Some ranges find opportunities where the action IS NOT right!(the cbet)


The CBET stat is divided by range now. in the preflop omaha tab.
stats have been copied to exclude error...only the range was changed.
The Range is calculated correctly....the only errors? are the opportunities.


There are 4 hands that went to showdown in my DB for that specific example.
ONE PAIR=AA shows 4 opportunities. =right
ONE PAIR=KK shows 5 opportunities. =wrong
DoubleSuited shows 5 opportunities. =wrong
Asuited shows 4 opportunities. =right
RAINBOW shows 5 opportunities. =wrong

After analysing i found the the specific hand where they differ.
In the specific extra hand which was in the 5 group the cbet did not happen.
But all the other cases did get filtered, cause there are only 4 cases that went to showdown
The TEST output of the correct 4 oppurtunities says:
++Action: Bet could have happened but did not

The TEST output of the misscounted hand says:
++group: Double Suited failed *OPPORTUNITY*

where it MUST not be a opportunitie!!



ok I try it more short:
One stat where action is filtered correctly has 4 hands that went to showdown.
By Copying this stat and applying different preflop ranges...suddenly for some ranges the action gets not filtered correctly.


Cant get my head around it.

[sreticentv]

No way to help you with the information provided http://forums.holdemmanager.com/note...ead-first.html

[leonick]

Ok I will try again...including definitions.

This Cbet definition is working correctly:
It is filtered by Showdownhands only.

__OOP_PFR_3PB_CBET_hu_sd!!.xml >>It shows me 4 Hands that went to showdown

When I use this stat now with "define opportunities by range"
And select preflop omaha range of: Onepair(A)
It counts correctly how often it was AA...and it shows 4 opportunities'=correct
__OOP_PFR_3PB_CBET_huAA.xml
The same with "suited to A"...counts correctly and shows 4 opp. = 4 hands that went to SD

But when I change to Onepair(K) or Doublesuited for example.....it suddenly shows 5!! opportunities.
In the one extra opportunity the CBET did NOT happen.
__OOP_PFR_3PB_CBET_huKK.xml

One Hand for example where it is counted as an opp...but where the CBET did NOT happen.
All the other cases where the cbet did NOT happen...get filtered correctly.

PokerStars Hand #139187219636: Zoom Pot Limit Omaha High ($0.02/$0.05 USD) - 2015/08/10 11:22:39 ET
Table 'Lynx' 6-max Seat #1 is the button
Seat 1: player1 ($1.62 in chips)
Seat 2: player2 ($4.34 in chips)
Seat 3: player3 ($2.66 in chips)
Seat 4: player4 ($6.31 in chips)
Seat 5: player5 ($5.45 in chips)
Seat 6: player6 ($8.55 in chips)
player2: posts small blind $0.02
player3: posts big blind $0.05
*** HOLE CARDS ***
player4: folds
player5: folds
player6: folds
player1: raises $0.12 to $0.17
player2: folds
player3: raises $0.36 to $0.53
player1: calls $0.36
*** FLOP *** [Th 7c 5c]
player3: checks
player1: bets $1.04
player3: raises $3.12 to $4.16
player1: calls $0.05
*** TURN *** [Th 7c 5c] [5h]
*** RIVER *** [Th 7c 5c 5h] [9c]
*** SHOW DOWN ***
player3: shows [As Jc 4s Ah]
player1: shows [3c Qc 9s 7s]
player1 collected $3.13 from main pot
*** SUMMARY ***
Total pot $3.26 | Rake $0.13
Board [Th 7c 5c 5h 9c]
Seat 1: player1 (button) showed [3c Qc 9s 7s] and won ($3.13)
Seat 2: player2 (small blind) folded before Flop
Seat 3: player3 (big blind) showed [As Jc 4s Ah] and lost
Seat 4: player4 folded before Flop (didn't bet)
Seat 5: player5 folded before Flop (didn't bet)
Seat 6: player6 folded before Flop (didn't bet)

Hope this makes everything easier
and thank you very much btw

[sreticentv]

Thank you for including the requested items. I agree this looks like it should not be an opportunity. I will take a closer look and give you a good answer or possibly make some fix with Omaha hands filtering by range which could have some issue with this exact definition

[sreticentv]

There was a change made for NC 2.6.0.4 to fix this Omaha bug. Please update How to make sure you have the very latest NoteCaddy build - Assaultware Wiki and let me know if you still see it

[leonick]

yep sir....everything working perfect now!!!
good job.