Quote:
Yes the spot is a forced 3b spot so could be that I'll just have to stop it at some point if the explo doesn't seem to go down much further.
It likely won't improve. Another factor which hurts the preflop solver a bit are smaller starting ranges (which is likely in your case). I already have some test cases for it and the situation improved in dev but it's still not solved entirely.
Quote:
this is not open source so can not grasp mechanism and reliability.
Opening the source wouldn't change much as verifying that the code works correctly is an impossible task.
We made an effort to make results exportable and browseable in many ways. We display EV of every action at every point. We also compared our results to other implementations we have as well as to those of other people (namely Oskari and his solver, Oskari's work got published in Science). Verifying things on your end would require coding your own solver (or at least a tool to verify EVs) and comparing the results but you can also try doing it manually on some toy cases.
Quote:
ex.said GTO-solution..what mean? analytical? numerical? approximate?
Those are apprxoimate equilibria. We display exact distance to the equilibrium as well.
Quote:
so,someone or developer proved fundamental reliability of piosolver?
Proving software correctness is an impossible task. A lot of people did work with Pio and compared it to other solutions though. We also have several implementations which we can compare and verify the results against. At this point correctness is the least of our worries (there are thousands of people using Pio every day, many developers doing tools working with it, there was never a case of Pio producing incorrect results).
Quote:
Hi punter, would you please recommend some single posflop sizes for us, at least as a starting point in solving 100 bb preflop trees?
It's reasonable to use small'ish cbet (say 40% or 50%) and then 75% bets on the turn and river. 3x raise is reasonable as well. The EVs don't change that much so it's not very important to get those right.
Quote:
Why is it bad to have "all in" checkbox checked for pf sims, and how could it affect the ranges in a bad way, making them less accurate?
The preflop solver operates on limited precision (to save memory). Having multiple bet sizes (and especially overbets) make it difficult for it to get the EVs right because of it. The situation is going to be improved in the future so accuracy won't be much of an issue but the part about it being not very productive (EVs don't change much so multiple bet sizes don't influence preflop ranges almost at all) is going to stand. I recommend using bigger subsets or adding more interesting preflop options instead of making postflop play more detailed when solving for preflop ranges.