Im having some problems with inputting potsize and stacksizes. I first put in dollar amounts but switching to bb takes way less memory. Shouldn't it be the same since spr is same in both?

Yes that is a better approach, thanks, i will try it. Nice additions in 1.6!

Please copy-paste the whole configuration ("copy to clipboard" button in tree building).
We don't do fractions in bet sizes and that could be a reason why additional branches appear (for example something gets rounded to bet of 2 into pot of 5 but is a bet of 25 into pot of 50 and then there is less space for additional raise somewhere along the way).
In general it's the best to use blinds of 5/10 as you don't care about fractions in bet sizes then.

#TreeBuilding#V2
#Range0#88,77,66,55,44,33,22,AJo,AT,A9,A8,A7,A6,A5 ,A4,A3,A2,KJo,KT,K9,K8,K7,K6,K5,K4s,K3s,K2s,QJ,QT, Q9,Q8,Q7,Q6,Q5s,Q4s,Q3s,Q2s,JT,J9,J8,J7,J6s,J5s,J4 s,J3s,J2s,T9,T8,T7,T6s,T5s,T4s,T3s,T2s,98,97,96s,9 5s,94s,93s,92s,87,86,85s,84s,83s,82s,76,75s,74s,73 s,72s,65s,64s,63s,62s
#Range1#AA,KK,QQ,JJ,TT,99,88,77,66,55,44,33,22,AK, AQ,AJ,AT,A9,A8,A7,A6,A5,A4,A3,A2,KQ,KJ,KT,K9,K8s,K 7s,K6s,K5s,K4s,K3s,K2s,QJ,QT,Q9,Q8s,Q7s,Q6s,Q5s,Q4 s,Q3s,Q2s,JT,J9,J8s,J7s,J6s,J5s,J4s,J3s,J2s,T9,T8s ,T7s,T6s,T5s,T4s,T3s,T2s,98s,97s,96s,95s,94s,93s,9 2s,87s,86s,85s,84s,83s,82s,76s,75s,74s,73s,72s,65s ,64s,63s,62s,54s,53s,52s,43s,42s,32s
#Board#Kc 9d 7h
#Pot#55
#EffectiveStacks#975
#AllinThreshold#67
#AddAllinOnlyIfLessThanThisTimesThePot#500
#MinimumBetsize#0
#UseUnifiedBetAfterRaise#False
#UnifiedBetAfterRaise#
#ForceIPBet#False
#ForceOOPBet#False
#Cap#3
#UseCap#True
#FlopConfig.BetSize#33,50
#FlopConfig.RaiseSize#
#FlopConfig.AddAllin#False
#FlopConfig.IncludeDonk#False
#TurnConfig.BetSize#33,50
#TurnConfig.RaiseSize#60
#TurnConfig.AddAllin#False
#TurnConfig.IncludeDonk#True
#RiverConfig.BetSize#33,50
#RiverConfig.RaiseSize#60
#RiverConfig.AddAllin#False
#RiverConfig.IncludeDonk#True
#FlopConfigIP.BetSize#33,50
#FlopConfigIP.RaiseSize#
#FlopConfigIP.AddAllin#False
#FlopConfigIP.Dont3bet#False
#TurnConfigIP.BetSize#33,50
#TurnConfigIP.RaiseSize#50
#TurnConfigIP.AddAllin#False
#TurnConfigIP.Dont3bet#False
#RiverConfigIP.BetSize#33,50
#RiverConfigIP.RaiseSize#50
#RiverConfigIP.AddAllin#False
#RiverConfigIP.Dont3bet#False


The tree size is roughly the same if I put potsize and stacks as a 200nl, 400nl, 600nl or a 1knl hand, but drops at 100nl.

The reason for that is that we don't do fractions in pot size, stack size and bet sizes.
That was a design decision which makes many other features possible or way more convenient as having fractions in bet sizes would make identifying lines by bet sizes a pain.
To work around that just multiply by 10 or 100 and everything will work as expected (max pot size/stack size is 65535 though).

Aight man makes sense thank you

Bought the basic version yesterday and atm a bit confused.

So I built a tree and solved it to some extent.

https://gyazo.com/e6a635ac2347f4f1aea4ec6348015832

But when I try to browse the tree, none ranges are shown at the browser??

https://gyazo.com/8460abb90bf35502160f50d2dede7d3d




PS: Is there any significant differences between basic and pro versions if I only havbe 4 cores? Can't queue calcs on many flops?

Also wondering this. What are scripts used for other than the multiple flop features? I have i7-4790, would the speed difference be much in basic vs pro? Id be mostly doing hands with short stacks and wide ranges if that makes a difference.

Make sure to watch the quick start video:
https://www.youtube.com/watch?v=JqGQoQKbCB8

The explanation how to show various things in 13x13 grid starts at 7:50.
You can show ranges, strategies, EVs, EQs and various combinations of those as well.

I think this post is a good explanation:
http://forumserver.twoplustwo.com/sh...&postcount=332

Basically the solver makes the whole programming interface available so you can script whatever you want. Quering the trees and solving many of them is the main purpose though if you are not willing to do any programming.

Very small difference - maybe 20%.

It doesn't.

Is this a bug?

When I click in K7s for example it appear in the square of the right, 0.7 instead of 0.175
I think it's a bug related with the Round Strategies Tab, it doesn't work properly in my opinion, I have to switch it everytime, in the gif it's set to 1/10 and I see: 0.0033
What do you think?

P.S. There is another strange problem:

Why the strategie change in some combos? and as you can see here, there is different kinds of round types in the same screen

Maybe but I don't see anything unexpected so far.

Why do you think it should be 0.175?
There is a difference between a range (how often we have a given hand at given point) and a strategy (what we do with it).
In the first screenshot you are showing ranges, on 2nd one you are showing strategies.
Again, try a quick start video: https://www.youtube.com/watch?v=JqGQoQKbCB8 where description of what various buttons who starts at about 7:50

To be honest I have 0 idea of what you are doing so it's hard to say if it does or doesn't work properly.

Maybe try giving some more data, like a tree config (in tree building tab there is "copy to clipboard button") so I can re-run. Also try to describe what you are doing step-by-step and then what is unexpected about the result you get.

Because you are checking a checkbox which influences how strategies are displayed on 13x13 grid. After checking that checkbox the width of the bars are proportional to current weights of the combos instead of being equal for every combo regardless of the weight so the result is exactly how it should be.
Same goes for the numbers. Remember that after every square there is more than 1 combo (for suited hands there are 4, for offsuit hands there are 12, for pairs there are 6) and there is only one set of numbers. There is a choice how to make one number out of many (average, weighted average and if so weighted by what) and the checkbox you are clicking/unclicking influences how those numbers are created.

In K7s that it is in the 13x13 grid it says 0,175, and I thought it was the average weight of all individual suited combos of K7s, when I click on it, in the small grid of the left, there is 0.7, some combos have the same number and other combos have different number

I'm just testing a random board CO vs BU http://pastebin.com/aNXRrred
and when I was testing everything I found little annoyances with the rounding type, I put 1/10 to flop-turn-river and I found some combos that are not rounding in that way

tytyty


In the same hand:

Is ok that call with AA with that low EV ? (-63)

Yeah but on your screenshot it's not visible though (I think you are only showing spades).
Pasting the config solves it though as I can now re-run it and see myself

Ok, so it seems to me that you are looking at the raising range (by clicking on a big red rectangle with a string "raise 108" on it). You do that after rounding to 1/10.
So let's go through it point by point:

1)It's OOP decision (raise 108/call/fold) and K7s is in the range with weight 1.
2)When we look at raising range we get: Ks7s: 0.7, Kh7h: 0, Kd7d: 0, Kc7C:0
3)Average weight for all K7s'es is (0.7 + 0 + 0 + 0) / 4 = 0.175 and that's why you see it
4)Remember that you are looking at ranges here. Ranges are not rounded, strategies are.

Again, remember that the strategies are rounded, not the ranges. If we call with 50% on the flop and then 10% on the turn we wil have a hand with 0.05 weight on the river.

First, remember that you have rounded the strategies. It means they are no longer optimal so the mistakes are bigger than they would be if you haven't rounded.
2nd thing is that AA is almost never (or just never) in range at this point (if you check "square sizes proportional to weight" checkbox you will see it disappears.

As to your 2nd screenshot in your first post I am still unable to comment because I don't see what spot it is, I would need a screenshot with the upper part of the window as well.

It seems to me that there is some confusion about the difference between a strategy (how often we do something) and a range (how often we have a given combo at certain place in the tree). I invite you again to watch the quick start video and I hope this answer clears things up a bit as well.

Is it possible to like cut the solved tree lets say from turn ->. Then edit betsizes for turn and river spots, and run the solver again, without recalculating flop? In simplepostflop this is possible and it's easy way of checking and trying different turn/river sizes.

There is no way to do it automatically at this point.
There is however a way which doesn't require that much effort:

1)go to the turn (don't choose any card)
2)click "OOP Range", copy the range, paste it to the range selector and save for later (or copy paste to notepad or w/e)
3)do the same with "IP Range"
4)make a turn tree, insert w/e bet sizes you like, insert the ranges from 1) and 2)
5)Solve

It's true it's not as convenient as "make a turn case from here" button would be but I think it's a workable solution for now.

We have added some video material to the site which I hope is going to be helpful. Check out the blog post (http://piosolver.myshopify.com/blogs...1062341-videos).
Quick links:

1)A quick start guide:
https://www.youtube.com/watch?v=JqGQoQKbCB8

2)A sample hand analysis:
https://www.youtube.com/watch?v=Jk4kWoA6UuI

3)FAQ:
https://www.youtube.com/watch?v=VhG_YsEvfwU

4)New features overview in 1.6 version:
https://www.youtube.com/watch?v=F4-7v-dUVPw

5)Node locking guide/example:
https://www.youtube.com/watch?v=a_OhaxBi7mY

All the feedback and suggestions for the future are welcome!

How do I make sure I have the latest version or update if I don't?

thanks

edit: I found the updater link in my emails but I get the following error when I try to update

Checking for new versions
Downloading information about available versions.
Comparing with current version.
New version found. Preparing for update.
Downloading the update...
Download complete.
Extracting files.
End of Central Directory record could not be found.
Update FAILED
ERROR:
Failed to unpack the package. Download link is incorrect or corrupted.

http://piosolver.myshopify.com/pages/quick-start-guide (point 1 and 2) in commercial version.

You are almost surely using incorrect personal link. If you can't find it in your email history just email support@piosolver.com and you will get it from us.

why arent copied ranges in crev format? so tilting

is there a way to see wages instead of absolute # of combos in range selector?

Because CREV format is silly. I explained it before, it's not suitable for a tool which produces ranges with any kind of precision and it has a lot of redundancy which makes it about twice as long as it needs to be.

Tools->Configuration->show total combos in range boxes checkbox regulates it, it seems you have it checked.

i see your point, but its commonly used format so it wouldnt hurt to have this option available

thx anyway

is it a bug? or freqs will not shows when more than 4 raising sizes?

Hey, do you have any plans of making available more bets on streets, like 4b, 5b?

No, it's not a bug.
The numbers appear once there is enough space for a minimum size font to fit. You can wider the area by:

1)moving the vertical bar between 13x13 area and the information area (the thing with the rectangles)
2)making the whole window bigger

I am not sure what that means. You can insert many sizes already:
https://www.youtube.com/watch?v=VhG_YsEvfwU (question 2)

Do you mean that or something else?

Yeah I see, didn't know I can put multiple raise sizes here also. Thanks