Quote:
I loaded the tree first in PioSOLVER-free.exe so I don't know why show_tree_params is not working except that in free version the command doesn't work :
load_tree D:\tree.cfr
load_tree ok!
show_tree_params
board: not set
As you can see , it says load_tree ok!
This is a bit advanced and not really useful for most people so it would be good to move that to emails or Skype (pm me and I will send my sn).
In short: those are part of the state which you set and then they are used to build a tree. If you load a tree they are not set by that. There are good reasons for that design but I can see how it's not obvious at first. The best way to start experimenting is to replicate what the viewer does exactly (by reading log.txt and repeating the commands). This way you can get the hang of things and start writing your own queries.
I am happy to help you with some details on either Skype or via pms/emails not to clog this thread too much with programming related discussion.
Quote:
hey punter, i will run a bunch of postflop trees on a dedicated server and i would like to know beforehand from which overbet size up does the solver starts getting trouble converging (you said it at some point)?
I don't know the answer to this question sadly. This is of course imperfection of the algorithm. In general the bigger they are and the least used they are the more problems they cause.
Quote:
I mean i will use a 200% overbet and in some spots the add allin option which triggers with a stack under 300% of the pot so overall i will not have obvertbets bigger then 300%.
Sounds good. Big overbets are used mainly on the river so I would limit myself to "add-allin" on the river and maybe some bigger bets (150% of the pot or something) on the turn/flop instead to see if they are chosen.
Quote:
when looking at a combo is there any way to lock it in the bottom right window? could be handy when comparing different strategies in different windows.
Two ways:
-you can hold left click and move your mouse away, then it won't change on hover
-Tools->Configuration->Behavior->[ ] require click to update zoom (at the top)
then they won't change on hover but will require a click to change.
Quote:
In the console I see : r:0:b25:c:2d:b104:b262
But in PioViewer : 2d : BET 79 : RAISE 237
I am not sure where b262 is coming from .
The solver always reports cumulative amounts internally (how much a player invested so far including that bet). This is easier to reason about/code for but it's not what people are used to that's why the viewer translates the bet amounts.
In your example Raise 237 is the same as :b262 as 262 is a total amount (so 25 bet before and 237 now which ends up being 262). The solver internally doesn't see a difference between bet/raise or check/call either (as a check is call 0). I hope that makes sense
Quote:
When you build a preflop tree as 'pure preflop tree (no flops exits)', does it mean that it gets checked down posflop or does it calulate the postflop plays without saving the flops to look at?
It assumes a check-down postflop, that's why it's instant to solve.
Quote:
If I bought PioSolver Pro, can I upgrade to the preflop version (edge) for the difference in price?
Please PM or post and let me know what to do and how to do it.
Yes and it's already taken care of via PM.