Open Side Menu Go to the Top
Register
PioSOLVER - postflop equilibrium solver for Holdem PioSOLVER - postflop equilibrium solver for Holdem

09-11-2018 , 06:28 PM
Quote:
And what about commans to set FlopConfig.BetSize or FlopConfig.RaiseSize? Can we make tree sizing by script using Tree Building v2 format? Or current format is only for handly using?
I am sorry I don't really understand the question. You can use add_line command in script.
The lines starting with # are comments which are readable for PioViewer (but won't work in scripts).

Quote:
Any thoughts on implementing a playable bot that uses our piosolver .cfr solution files? I'm currently using simplegto but it has some bugs/kinks with pio.
You mean something you can train against? I don't have any thoughts on it other than it will likely happen on our side sooner or later.

Quote:
Building on this question, I'm curious if there is a way to nodelock an entire tree at root (say force the solver to raise with 50% less frequency with its bluffs on all streets) and then solve?
If you node-lock entire tree then there is no point in solving as no strategy is going to change.

Quote:
This would be really useful for practicing against an exploitable bot that uses the nodelocked solutions. Currently I have to nodelock individual cards on individual streets, but this is really cumbersome when practicing against a bot that is using a large .cfr database of 50+ flops.
It's not clear to me what you want to achieve. Can you describe it? I don't see the point of locking the whole tree.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-11-2018 , 10:13 PM
I have a similar question about node locking.

Is there a way to change a node strategy without choosing combos? For example say you want to change the check raising strategy to 20% without picking the exact combos, just letting the solver pick the best 20% and call/fold the rest?

Building on what the last guy asked, I think he wants a way to change the general strategy, not node lock the entire tree. For example, inputting a certain aggression frequency such that the overall bet/call ratio of one player is locked accross all nodes, but the solver still picks which combos to bet/call with.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-12-2018 , 02:16 AM
Quote:
Is there a way to change a node strategy without choosing combos? For example say you want to change the check raising strategy to 20% without picking the exact combos, just letting the solver pick the best 20% and call/fold the rest?
Not possible right now. What we are likely to implement is choosing frequencies once the solution is at least in the ballpark of correct one so the solve knows which combos are good candidates for raising/calling etc. Without it the solver would need to guess before solving which is very difficult.

Quote:
Building on what the last guy asked, I think he wants a way to change the general strategy, not node lock the entire tree. For example, inputting a certain aggression frequency such that the overall bet/call ratio of one player is locked accross all nodes, but the solver still picks which combos to bet/call with.
Yes but locking general frequencies is difficult to implement. Imagine that the optimal solution is to call 70% and fold 30% at some point. You lock 50%-50% frequency. At this point the solver needs to discard a lot of +EV calls and make them folds. Now depending of which calls becomes folds opponent's strategy changes. As the EV differences between calls and folds change from iteration to iteration (due to opponent adjusting) it will cause fluctuation and the strategy will not converge.

It's doable to change strategy to given frequencies once there is solution but it's not possible to lock general assumptions and solve with those. At least it's not clear how to implement it in a way that it converges.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-12-2018 , 02:42 AM
Quote:
Originally Posted by Vinni121
a) reboot your PC
b) delete "pioviewer_log.txt" and turn off logging in solver.

Did it helped?
cant find that file , and also looks like pio is not saving logs (just checked at debugging/logging tab)
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-12-2018 , 10:18 AM
I think the utility of node-locking large parts of the tree is in coming up with maximally exploitative strategies against weak opponents. If you can perfectly model the entire villain half of the game tree (as they actually play, not a perfect opponent) then solving for the maximally exploitative counter-strategy should be trivial. It would be great to be able to start with an assumption about villain strategy (i.e. never bluffs when flush draw hits on river, only bluffs with nut flush blocker perhaps) and then solve for the exploitative strategy all the way back to flop/preflop decisions. Of course manually node-locking all/many rivers is not practical which is where some broad modelling assumptions would have to come in.

The trouble with locking check/bet % is that a weak opponent with an exploitable bet % probably isn't betting the optimal combos for that % either. Of course the way opponent check/bet % varies across different boards might be massively different from optimal as well. So even though plugging PT4/HEM2 database check/bet or fold/call/raise % into pio might seem like an easy way to find exploits I don't think it would be an accurate way to model opponent behaviour.

The ideal solution I think would be an interface that allows you to select all/some boards on a given street from the full game tree to node lock villain. You could then apply a simplified rule-based strategy at those nodes (bet all two pair or better, all hands worse than X-high, all nut flush blockers etc) and solve for exploits. This would require a deeper understanding (or assumptions) of opponent strategy but I think would be a lot closer to how people actually play (and can therefore be exploited).

I've got to be honest, it sounds like a lot of work and would be a tough interface to make user-friendly. But it would be enormously useful if possible.

Last edited by Lanky; 09-12-2018 at 10:24 AM.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-12-2018 , 06:14 PM
If you’re using a server to run simulations what do you suggest is the best way to save the trees for use on other computers?
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-13-2018 , 04:56 AM
Quote:
Originally Posted by punter11235
I am sorry I don't really understand the question. You can use add_line command in script.
The lines starting with # are comments which are readable for PioViewer (but won't work in scripts).



You mean something you can train against? I don't have any thoughts on it other than it will likely happen on our side sooner or later.



If you node-lock entire tree then there is no point in solving as no strategy is going to change.



It's not clear to me what you want to achieve. Can you describe it? I don't see the point of locking the whole tree.

So currently I have a .cfr database of about 100 different flops involving a sb vs btn 3bet pot.

The bot I use reads these .cfr files and allows me to play vs the bot either IP or OOP, generating a random flop from the database and picking hands from the given ranges. While this is great practice for playing against an optimal opponent, it would be great if I could somehow tell the bot to play an exploitable strategy. (Say bluffs less frequently on the river by 50%, or always folds to overbets without two pair+, etc)

While I can go and nodelock an individual .cfr file to practice against the bot on a single flop, it would be amazing if I could somehow nodelock all 100 flops in my database for one player to follow certain tendencies and then have pio resolve to maximally exploit.


This would be amazing for practicing and studying maximal exploit strategies.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-13-2018 , 01:50 PM
I have looked around for this in the FAQs and I didn't see it.

I am just trying to node lock one bet size for villain (IP). Basically I solved for 3 sizes (33,66,100) for each player. The solution said that villain should bet small with more or less his entire range, but he bet 66%. I want to node lock in the sub-optimal bet size and see how to exploit it with my range.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-14-2018 , 05:31 PM
hi guys im choosing a 49 flop subset @
https://www.piosolver.com/blogs/news...the-whole-game

and i have this question... can anyone tell me what those numbers at the right of the flops mean?
https://cdn.shopify.com/s/files/1/07...46264467327999
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-14-2018 , 06:41 PM
Quote:
If you can perfectly model the entire villain half of the game tree (as they actually play, not a perfect opponent) then solving for the maximally exploitative counter-strategy should be trivial
It is in fact easy. We even have this functionality in the solver. You can call set_mes command from arbitrary solver command to set one of the strategies to maximum exploit. Please be aware that it's not possible to get the original solution back (so you need to make a full tree save if you want to recover it) an that it is in general not very useful because set_mes is going to exploit small imperfections in the solution (even if it's very close to 0 exploitability) by setting strategies to 100%-0%.

The exact commands to call are:
set_mes OOP
set_mes IP

Quote:
It would be great to be able to start with an assumption about villain strategy (i.e. never bluffs when flush draw hits on river, only bluffs with nut flush blocker perhaps) and then solve for the exploitative strategy all the way back to flop/preflop decisions. Of course manually node-locking all/many rivers is not practical which is where some broad modelling assumptions would have to come in.
Yes, the problem is in designing a language for those general assumptions. It is an interesting project but it needs to wait a bit more.

Quote:
I've got to be honest, it sounds like a lot of work and would be a tough interface to make user-friendly. But it would be enormously useful if possible.
That's how we see it as well. Not easy to design well, a lot of work in both coding it first and then supporting/improving it from user's feedback. Potentially very interesting and useful though.

Quote:
If you’re using a server to run simulations what do you suggest is the best way to save the trees for use on other computers?
Make small saves, zip it, copy-paste to your computer.
Quote:
While this is great practice for playing against an optimal opponent, it would be great if I could somehow tell the bot to play an exploitable strategy. (Say bluffs less frequently on the river by 50%, or always folds to overbets without two pair+, etc)
Yes, this sounds very interesting and I hope it happens one day. It's not an easy thing to make though.

Quote:
I am just trying to node lock one bet size for villain (IP). Basically I solved for 3 sizes (33,66,100) for each player. The solution said that villain should bet small with more or less his entire range, but he bet 66%. I want to node lock in the sub-optimal bet size and see how to exploit it with my range.
By far the most efficiant solution for this one is to make a new tree with only one bet size at this point and solve it. It will be much faster and more precise than node-locking on already solved tree and waiting till it converges again.

Quote:
nd i have this question... can anyone tell me what those numbers at the right of the flops mean?
They are weights (probabilities). Flops with bigger weight is counted more often for overall EV/strategy. Introducing weights makes it possible to have smaller subset which still approximates overall EV well.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-15-2018 , 12:50 AM
Used updater for 1.10.19. In the updater it shows my Licence Status as Registered. I have [x]open installation directory on exit. Now when I open PioViewer it's not connected. When I go to Solver>connect>PioSOLVER-edge. I get a pop-up that says: Activate PioSOLVER You're trying to connect to non activated Pio SOLVER Pleaes provide your activation code. When I do that I get another popup that says "Activation successful". When I click "ok" I get stuck in an endless loop of it asking for activation code. If I x out of that popup I get another that says "failed to connect: PioSOLVER not activated. Activate before connecting to pioViewer. If I select "ok"
I get another that says "Failed to connect: Couldnt connect so solver-probably blocked by some other program(e.g. anti-vir)
Try to run C:\Users\Administrator\Desktop\PioSOLVER\PioViewer .exe directly from system explorer and see if you will be prompted to add an exception to run the program. I did this and got stuck in same loop.

Any help would be greatly appreciated. Thank you

Last edited by The Apex; 09-15-2018 at 12:57 AM.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-15-2018 , 04:30 AM
Hi,

I have just run a script with 184 flops on Pio.

Now I have a file, but I can't access it from Pio.

Furthermore, it just contains all the raw data from the run. The flops aren't divided into separate files and I don't know what to do to use the data.

I expected the data to save as multiple flop files, so I could click one of them, and then run an aggregated report...
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-15-2018 , 07:09 AM
I just downloaded the free version and it doesn't work. I get an error message saying

"This application could not be started.

Do you want to view information about the issue?"

Then there is a yes and no box which don't do anything.

It pops up twice.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-15-2018 , 01:08 PM
Quote:
Try to run C:\Users\Administrator\Desktop\PioSOLVER\PioViewer .exe directly from system explorer and see if you will be prompted to add an exception to run the program. I did this and got stuck in same loop.
This is almost always caused by date, time or timezone being set incorrectly on your computer. Please make sure they match the location of the computer and try again. Full restart might be necessary for it to work.

Quote:
Furthermore, it just contains all the raw data from the run. The flops aren't divided into separate files and I don't know what to do to use the data.

I expected the data to save as multiple flop files, so I could click one of them, and then run an aggregated report...
Your expectations are correct. Separate saves are created in the directiory you have chosen in the script generation window. Are you sure the script finished? It will take a lot of hours to finish for 184 flops, maybe even days. The trees are created as the solver goes so you can check if they appear. In the console window you will see messages like "tree xxx finished, 1 out of 184 done" etc.

Quote:
I just downloaded the free version and it doesn't work. I get an error message saying

"This application could not be started.

Do you want to view information about the issue?"
The free version is distributed as a .zip file so make sure to extract it to an empty folder and run it from there. You need 64bit Windows and up to date Net Framework to run it (if the Windows is updated regularly there is no need to download Net Framework separately).
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-15-2018 , 01:44 PM
Quote:
Originally Posted by Rezzir
Your expectations are correct. Separate saves are created in the directiory you have chosen in the script generation window. Are you sure the script finished? It will take a lot of hours to finish for 184 flops, maybe even days. The trees are created as the solver goes so you can check if they appear. In the console window you will see messages like "tree xxx finished, 1 out of 184 done" etc.
I used the Amazon EC2 m4.4xlarge which has 16 CPUs and 64gb so it only took 45mins.
(It also cost $15 for about 2-3 hours of use).

It took 15sec per flop. But I don't see a file. Just the read out from the script run as I said before.

Last edited by Rezzir; 09-15-2018 at 02:03 PM.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-15-2018 , 05:28 PM
Hi,

When I use the option "create a subtree" to compare the EV at the root when using multiple sizing on a certain turn, sometimes the EV of having multiple sizing is lower than having one sizing. Is it normal ? That happens when one of the sizing is almost never picked.

Thanks
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-15-2018 , 06:09 PM
Quote:
Originally Posted by CodythePATRIOT
I have looked around for this in the FAQs and I didn't see it.

I am just trying to node lock one bet size for villain (IP). Basically I solved for 3 sizes (33,66,100) for each player. The solution said that villain should bet small with more or less his entire range, but he bet 66%. I want to node lock in the sub-optimal bet size and see how to exploit it with my range.
Quote:
Originally Posted by punter11235

By far the most efficient solution for this one is to make a new tree with only one bet size at this point and solve it. It will be much faster and more precise than node-locking on already solved tree and waiting till it converges again.

If this is the case would it just be better to always build the trees using villians exact bet sizing for each street?
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-16-2018 , 01:25 AM
Hi guys,

Having generated 100 flops in the cloud. Is there an effective way to get them back to your other Piosolver, that is on a slower computer, so that you can analyse them in a more cost-effective way?

I was trying to upload them to Amazon Drive, but I didn't even get one flop uploaded in over an hour.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-16-2018 , 01:27 AM
Quote:
Originally Posted by Rezzir
I used the Amazon EC2 m4.4xlarge which has 16 CPUs and 64gb so it only took 45mins.
(It also cost $15 for about 2-3 hours of use).

It took 15sec per flop. But I don't see a file. Just the read out from the script run as I said before.
I have since resolved this issue. It turns out I thought they were done after 45 mins, when in actual fact, the first flop was starting to be run. After that it took 10mins per flop.



The question of how to get them to a non-cloud Piosolver is still valid though. I would like to use cloud for the script running and a non-cloud Piosolver for analysis.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-16-2018 , 02:41 AM
Hey

I've use postflop tree to calculate 1 hand.
https://ibb.co/ndO6HK

As you can see it taken 2092 second to reach 1,64% exploitable.

My setup:
i7 7700k (4core 4,2Ghz)
32gb ddr4 ram
and m2.sata ssd

So my question is about the speed compared my computer versus a server. I thinking to make bigger calculations with the same postflop tree. I saw some server for 500$ (for just 1 month)

Processor: Intel® Xeon® Gold 6126
Speed: 12 Cores (HT) x 2.6 GHz (3.7 GHz Turbo Boost)
RAM: 192 GB DDR4 ECC
Hard-disk space: 1,000 GB (2 x 1,000 GB Intel P4510 NVMe SSD)
RAID: Hardware RAID 1

What do you think with this server and with my postflop tree, approxiametly how many second will be 1 hand to calulate till 0,5% exploitable ?

As i see it on CPU benchmark
Intel Core i7-7700K @ 4.20GHz 12,049 point
Intel Xeon Gold 6154 @ 3.00GHz 27,789 point

So the difference will be maybe just half time? Or the 192gb ram will help more?

Thank you
(and sorry if this question was already asked a lot of time)

Last edited by misirulez88; 09-16-2018 at 02:52 AM.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-16-2018 , 07:19 AM
sorry for repetition of the same questions, but, you think this configuration its ok? gpu its not important to run pio , right? thank you!!

https://www.pccomponentes.com/configurador/
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-16-2018 , 07:53 AM
.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-16-2018 , 09:42 AM
Quote:
Originally Posted by 7betpafold
.
thanks for advanced!!

https://gyazo.com/093a14d02a34fcc6ca625f5630ccddbd
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-16-2018 , 01:49 PM
Does anyone have a high performance laptop that they use for Pio?

I am looking at the cloud computing cost (Amazon EC2) for 16CPU and 64gb capacity and it seems it will be about $200 per month.

Will an i7quad core, 64gb laptop offer me similar computing power? They seem to be about $2,500, so I figure if they are around the same I could shell out for one of them.

It currently takes me 10min to run each 1gb script tree.
PioSOLVER - postflop equilibrium solver for Holdem Quote
09-17-2018 , 04:17 AM
Hey punter! Just wanted to say thanks for answering all my questions so far! I'm sure everybody here really appreciates it! Here's another quick one I'm hoping to get another pair of eyes to take a look at...

Currently solving a SB vs BB spot using the preflop solver, and I'm getting some strange results.

Here is the config:
Code:
#PreflopConfiguration
#PreflopRangeOOP#1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
#PreflopRangeIP#1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
#BB#20
#PreflopRake.Cap#0
#PreflopRake.Fraction#0
#PreflopRake.Enabled#False
#PreflopICM.Stacks#0
#PreflopICM.Payouts#0
#Pot#10 20 0
#Stack#2000
#Nodes
#0.0#Raise_70
#0.1#Limp
#0.2#Fold
#0.1.0#Raise_70
#0.1.1#CheckCall
#0.1.0.0#Raise_240
#0.1.0.1#CheckCall
#0.1.0.2#Fold
#0.1.0.0.0#Raise_620
#0.1.0.0.1#CheckCall
#0.1.0.0.2#Fold
#0.1.0.0.0.0#Raise_5000
#0.1.0.0.0.1#CheckCall
#0.1.0.0.0.2#Fold
#0.1.0.0.0.0.0#CheckCall
#0.1.0.0.0.0.1#Fold
#0.0.0#Raise_210
#0.0.1#CheckCall
#0.0.2#Fold
#0.0.0.0#Raise_600
#0.0.0.1#CheckCall
#0.0.0.2#Fold
#0.0.0.0.0#Raise_3000
#0.0.0.0.1#CheckCall
#0.0.0.0.2#Fold
#0.0.0.0.0.0#CheckCall
#0.0.0.0.0.1#Fold
#FlopConfigs
#Node#0.1.1
#TreeBuilding#V2
#AllinThreshold#67
#AddAllinOnlyIfLessThanThisTimesThePot#150
#CapEnabled#True
#Cap#4
#CapMode#NoLimit
#FlopConfig.BetSize#60
#FlopConfig.RaiseSize#60
#TurnConfig.BetSize#60
#TurnConfig.RaiseSize#60
#RiverConfig.BetSize#60
#RiverConfig.RaiseSize#60
#FlopConfigIP.BetSize#60
#FlopConfigIP.RaiseSize#60
#TurnConfigIP.BetSize#60
#TurnConfigIP.RaiseSize#60
#RiverConfigIP.BetSize#60
#RiverConfigIP.RaiseSize#60
#EndFlop
#Node#0.1.0.1
#TreeBuilding#V2
#AllinThreshold#67
#AddAllinOnlyIfLessThanThisTimesThePot#150
#CapEnabled#True
#Cap#4
#CapMode#NoLimit
#RemovedLines#check, check
#FlopConfig.RaiseSize#3.2x
#TurnConfig.BetSize#60
#TurnConfig.RaiseSize#3.2x
#RiverConfig.BetSize#66.66
#RiverConfig.RaiseSize#3.2x
#FlopConfigIP.BetSize#33.33
#FlopConfigIP.RaiseSize#3.2x
#TurnConfigIP.BetSize#60
#TurnConfigIP.RaiseSize#3.2x
#RiverConfigIP.BetSize#66.66
#RiverConfigIP.RaiseSize#3.2x
#EndFlop
#Node#0.1.0.0.1
#TreeBuilding#V2
#AllinThreshold#67
#AddAllinOnlyIfLessThanThisTimesThePot#150
#CapEnabled#True
#Cap#3
#CapMode#NoLimit
#RemovedLines#check
#FlopConfig.BetSize#33.33
#FlopConfig.RaiseSize#50
#TurnConfig.BetSize#50
#TurnConfig.RaiseSize#50
#RiverConfig.BetSize#60
#RiverConfig.RaiseSize#50
#RiverConfig.AddAllin#True
#FlopConfigIP.BetSize#33.33
#FlopConfigIP.RaiseSize#50
#TurnConfigIP.BetSize#50
#TurnConfigIP.RaiseSize#50
#RiverConfigIP.BetSize#60
#RiverConfigIP.RaiseSize#50
#RiverConfigIP.AddAllin#True
#EndFlop
#Node#0.1.0.0.0.1
#TreeBuilding#V2
#AllinThreshold#67
#AddAllinOnlyIfLessThanThisTimesThePot#150
#CapEnabled#True
#Cap#3
#CapMode#NoLimit
#RemovedLines#check, check
#FlopConfig.RaiseSize#50
#TurnConfig.BetSize#40
#TurnConfig.RaiseSize#50
#RiverConfig.BetSize#50
#RiverConfig.RaiseSize#50
#RiverConfig.AddAllin#True
#FlopConfigIP.BetSize#25
#FlopConfigIP.RaiseSize#50
#TurnConfigIP.BetSize#40
#TurnConfigIP.RaiseSize#50
#RiverConfigIP.BetSize#50
#RiverConfigIP.RaiseSize#50
#RiverConfigIP.AddAllin#True
#EndFlop
#Node#0.0.1
#TreeBuilding#V2
#AllinThreshold#67
#AddAllinOnlyIfLessThanThisTimesThePot#150
#CapEnabled#True
#Cap#4
#CapMode#NoLimit
#FlopConfig.BetSize#50
#FlopConfig.RaiseSize#3.2x
#TurnConfig.BetSize#60
#TurnConfig.RaiseSize#3.2x
#RiverConfig.BetSize#66.66
#RiverConfig.RaiseSize#3.2x
#FlopConfigIP.BetSize#50
#FlopConfigIP.RaiseSize#3.2x
#TurnConfigIP.BetSize#60
#TurnConfigIP.RaiseSize#3.2x
#RiverConfigIP.BetSize#66.66
#RiverConfigIP.RaiseSize#3.2x
#EndFlop
#Node#0.0.0.1
#TreeBuilding#V2
#AllinThreshold#67
#AddAllinOnlyIfLessThanThisTimesThePot#150
#CapEnabled#True
#Cap#3
#CapMode#NoLimit
#RemovedLines#check, check
#FlopConfig.RaiseSize#3.1x
#TurnConfig.BetSize#60
#TurnConfig.RaiseSize#3.1x
#RiverConfig.BetSize#66.66
#RiverConfig.RaiseSize#3.1x
#RiverConfig.AddAllin#True
#FlopConfigIP.BetSize#33.33
#FlopConfigIP.RaiseSize#3.1x
#TurnConfigIP.BetSize#50
#TurnConfigIP.RaiseSize#3.1x
#RiverConfigIP.BetSize#60
#RiverConfigIP.RaiseSize#3.1x
#RiverConfigIP.AddAllin#True
#EndFlop
#Node#0.0.0.0.1
#TreeBuilding#V2
#AllinThreshold#67
#AddAllinOnlyIfLessThanThisTimesThePot#150
#CapEnabled#True
#Cap#3
#CapMode#NoLimit
#RemovedLines#check
#FlopConfig.BetSize#25
#FlopConfig.RaiseSize#50
#TurnConfig.BetSize#40
#TurnConfig.RaiseSize#50
#RiverConfig.BetSize#50
#RiverConfig.RaiseSize#50
#RiverConfig.AddAllin#True
#FlopConfigIP.BetSize#25
#FlopConfigIP.RaiseSize#50
#TurnConfigIP.BetSize#40
#TurnConfigIP.RaiseSize#50
#RiverConfigIP.BetSize#50
#RiverConfigIP.RaiseSize#50
#RiverConfigIP.AddAllin#True
#EndFlop

Take a look at how the BB reacts to a limp from the SB. Pio has the BB raising some very questionable hands like J4o, T2o, etc. Here is a screenshot:




This was done over 50 flops, as any more flops would result in over 128gb of memory which is greater than my capacity. However, I feel that 50 flops should give me an accurate enough solution where the BB isn't raising junk hands over a SB limp...

Is there perhaps something wrong with my config, or am I lacking enough flops and therefore accuracy in my solution? Or is this actually close to the optimal solution others are getting for BB vs SB after a limp?
PioSOLVER - postflop equilibrium solver for Holdem Quote

      
m