the left and right side of an operation must be compatible

[Parket]

I imported my HU SNG HUD profile into PT4, and my Effective Stacksize panel is producing this value while playing : "the left and right side of an operation must be compatible" rather than the number of big blinds it is supposed to show.
The variable is defined as follows : "min(var_live_amt_stack,var_live_avg_stack*2-var_live_amt_stack) / var_live_amt_bb" which correcty validates and saves.

What's wrong ?

[WhiteRider]

I don't think that live stats transfer correctly from PT3 as the structure is slightly different. Have a look at how the existing live stats in PT4 are built and recreate the ones you need for your layout. If you have problems please let us know and we'll give you a hand.

[Parket]

Have a look at how the existing live stats in PT4

Not sure if I correctly understand. The 3 stats that I use in my expression are already built-in live stats in PT4: var_live_amt_stack, var_live_avg_stack, var_live_amt_bb. So it's not like I need to build those stats. From the error message it more looks like there's a problem with using min(x,y) or x/y.

[Talsac]

I have the same problem and so far I have not found a solution :(

[Talsac]

I think the problem is the "var_live_avg_stack" variable.

Place the above (or "live_avg_stack") in a new definition and it wont validate.

The live stat "Live Avg Stack" uses "live_amt_stack" which is not the average just the stack size not unless I'm missing something?

But a quick fix (if you are playing standard HU SNG's) might be to replace "var_live_avg_stack" with 1500?

Something like this..
min(live_amt_stack,1500*2-live_amt_stack) / live_amt_bb
or just
min(live_amt_stack,3000-live_amt_stack) / live_amt_bb

[WhiteRider]

I think there is a slight complication with the way that the live average stack variable is set up currently. I will make a note to check this out when I have a little more time. Thanks for bringing this to our attention.

[Parket]

I looked into the database itself, and it does seem like there is an average stack field available.
You can then add it in PT4 as a new column 'live_amt_avg_stack' as follows : live_tourney_table.amt_avg_stack

Once this is done, the correct effective stacksize formula is : min(live_amt_stack,2*live_amt_avg_stack-live_amt_stack) / live_amt_bb

[Parket]

I'm still getting the error though, and it looks like it has nothing to do with the value to be displayed. I eventually simply had the constant '1000' as the value, and still got the error. It seems like the expression for the formatting was the culprit. Stupidly enough I no longer know what it was, as I changed it to 'Number' and then the 1000 showed up.
Now let's see if I can get that Effective Stacksize to display.

EDIT: yay, it worked !!!

[kraada]

I'm glad to hear you got everything working!

[PartyAnimal]

I was trying to configure the statistics and the "Live Amt BB" definition is
live_amt_stack / live_amt_bb
so it does not seem to make sense that "Live Avg Stack" would have a definition of
live_amt_stack :?

Will the PT4 developers be creating a live_avg_stack column (live_tourney_player.avg_stack?) or does each player have to try Parket's fix?
I think this wrong definition is why the average stack displayed in the HUD is usually wrong and keeps fluctuating even when there are no new players in the table.

I think there is a slight complication with the way that the live average stack variable is set up currently. I will make a note to check this out when I have a little more time. Thanks for bringing this to our attention.