Thanks for response, but feels like I still misunderstand some points.

So, let's get full example.

UTG Open Raise 30$, 4 fold, BB calls 20$

Pot: 65$
Effective Stacks: 1000

We want to know: What kind of hands we should defence on BB against UTG OpenRaise 15%

Our algorithm:

• 1) Creating bet tree
  
  
  
  Click "Build Tree"
  
  
  
• 2) Generate script
  
  
  
  Ctrl + V - 184 flops set
  Tick - "micro saves (flops only)"
  Accuracy - 1% of pot
  
  Click "Generate script"
  
  Click "Script" -> "Run script"
  
  
  
  
  
• 3) Creating report
  
  
  
  Click "File" -> "Load Tree" -> ".../PioSolver/saves/XXX.cfr"
  
  Choose "Root" in tree (to get starting EV preflop hands on all possible postflops actions/runouts and etc., right?)
  
  Click "Plugins" -> "Aggregation" -> Multiple Files runouts "afa"
  

Results

So, handsEV.csv



On Preflop we've called 15$ in this pot.

Means, that in this Ranges BB defence JTo, QTo, KTo, QJo would be a bad idea, if we play GTO strategy vs GTO Player (EV < 15.00).

So we should search narrow range and for this we'll use our new EV order (oopPreflopOrder.txt) and do a new solve.


In the same time this spot for raiser (IP Range):



PFA invested 25$ in this pot, so against this kind of BB Range in GTO vs GTO game postflop from flop to river, PFA will always play with positive EV, cause all his hands EV > 25.00 postlop. Right?


If I get it right, then do a report in root - that's essential thing, cause in any another place of tree PioSolver will count a special case (with some actions), not the whole tree of postflop. Yes/No?

Where I'm wrong and how to do it properly?

*
UTG Open Raise 25$, 4 fold, BB calls 15$

This is almost surely a problem with Net Framework version. Please download the newest stable one from Microsoft, here:
https://www.microsoft.com/en-us/down....aspx?id=42642

Roachru: you are doing everything properly and you've written a nice tutorial of the process
Some comments:

It should be enough although some bias is still possible because the algorithm always ends with a step for IP (it goes OOP, IP 25 times, print results, repeat).
I feel this is very small bias but I didn't measure it. You may try running it to 0.5% on 2-3 flops and compare EVs.

If it's 25$ then the pot would be 55$, not 65$ (25$ from a raiser + 25$ from BB +5$ from SB) and your configs shows 65$.

Yeah but we've called 25$ in your first example (as the pot is 65$).

Again, it should be 30$. It's not surprising either because everyone but BB folding is already a good result for the opener (they didn't face a 3bet).

Yes, you can run the report in any place of the tree and you will get EVs for there. If you want overeall EVs make sure to choose Root as the starting point.

Other than making an example for raise to 30$ and a call and correcting that you meant 25$ and a call everything is correct. If you wanted 25$ + 4 folds + BB calls then you need to change the starting pot to 55$ and repeat the process.

I hope that helps

This worked, thanks

Is it possible to create an aggregation report analysis from a script?

No because this is a feature of the viewer. Flops can be run/saved from a script but to create the report itself you have to click through the option.

I had to restore windows but lost my piosolver download folder... how do I get it back?

EDIT:

also dont have piosolver on the pc anymore to auto update.. what do

NINJA EDIT:

searched thread and e-mailed support.

The license won't survive that so either deactivate beforehand or email us afterwards so we can reset (link how to deactivate/activate: http://piosolver.myshopify.com/pages/faq (point 5))

Should be solved by now

Is the only way to weight these flop results disparately is by having the pro version?

Yes because only pro version supports scripts.

any updates on the preflop solver, will we be seeing it in the next few weeks?

Yes. I was about to make an announcement so I can just as well make it answering this post.

News about preflop solver:

-first release is going to be next weekend
-the solver works locally, in RAM (for now)
-it works on subset of flops which you can choose
-minimum requirements: 32GB of RAM, requirements for comfortable usage 64GB of RAM
-it works on cloud instances/dedicated servers as well which are likely to be the best options to run it;
-because of many memory optimizations as well as good flop subset selection (subset of various sizes will be added to the solver) the solutions are close to perfect even on very small subsets; for example I've run it for 2 hours on i7 3770k with 32GB of RAM for 7bb preflop game which is became a benchmark of sorts (because Will Tipton used it in his books and it was the only publicly available semi-solution you can compare against so naturally other people solving preflop have chosen it) and I've got the following results:

1)SB opens:
http://i.imgur.com/SXc4ae0.png
2)BB responds to a shove:
http://i.imgur.com/R7i5FVx.png
3)SB limps and responds to a minraise:
http://i.imgur.com/ABdkrlR.png (notice that the viewer shows the raise size as 60 instead of 70 but this is a glitch in a viewer and the solution is for 70$ (7bb) all-in)
4)SB limps and responds to a shove:
http://i.imgur.com/7hSVryD.png

The evs (5$/10$ blinds):
EV OOP: -0.291
EV IP: 0.291
MES OOP: -0.270
MES IP: 0.309
Exploitable for: 0.020

So SB wins 0.029bb/hand

If you compare this solution to recently published solution on all 1755 flops you will notice that our solution on a subset is way better than the one Tipton got and is almost perfect combo-by-combo match and exact EV match even though it was run on a computer with 32GB of RAM (and using 25GB). The reason for results being as good are:

-memory optimizations, so we can keep more flops in RAM; it was run on 58 flop subset and took 25GB of RAM, it means the whole game would be just shy of 800GB;
-good flop subset selection (check out the blog post about it, the flops were improved since then and we have subsets of every size available)
-no postflop abstractions so EVs from them are exact

We tested it on 100bb games solved before by other people and again it's almost perfect combo-by-combo match. It means you will be able to experiment with preflop games and solve them using slight variations in bet sizings/locked ranges on a good home desktop (with 64GB of RAM and even toy with it with 32GB as I have) or on one cloud instance/dedicated server - no need for distributed solver and huge bills (although if there is demand we will likely provide it)


Pricing:
-The preflop solver is going to be a part of PioSOLVER-edge version; one activation of it is added there (and normal activations will be reduced to 2 to keep total at 3; it of course doesn't influence people who already bought the edge version or buy it before the announcement (they get 3 normal ones + 1 preflop solver))
-Additional activations will be purchased separately and the cost will be around 500$/activation

This means that for 1100$ and a not so big electricity bill you will be able to solve NLHE preflop in your home.

More details next weekend with the release. I am happy to answer not too specific questions for now.

If there are any experienced PIO users that would be willing to do a few hours of coaching for the program PM me (obv for $). *only looking for help with the program not general poker coaching.

punter11235, how much disk space required for like 20-25 bb solutions?

Make sure to post it on our Skype group as well, preferably at various times of the day. Many well known coaches/experienced players hang out there on regular basis so you are likely to get some help.

To solve: 0.
To save: almost 0 for preflop only, few MB for preflop + flops more for preflop + flops + turns, as much as they take in memory for the whole thing.

It seems though that the best course of action is to solve preflop using simple trees postflop and then using those ranges solve flop separately using better structure.

Tried searching the name of the skype group but didn't come up with anything. How do I join?

PM sent!

how much ram does it require to replicate will tiptons 20bb solutions with 25 and 49 flop subset? also will we be able to solve for blind vs blind solutions where the SB is out of position?

It took 25GB with 58 flops so it should be proportional (+/- slight variation in suitedness of the subuset).

Of course. You will also be able to solve stuff like BTN vs BB, CO vs BB 6max although that will require locking the stealing range.

Can we lock multi nodes like in post flop? Lets say we know vilain oR call 3bet and 4 bet ranges, so we can lock them and get explo solution vs his strategy?

And how much ram is needed to solve 100bb spots?

Node locking preflop is not implemented as of today but it's not rocket science and it's very likely to be there just working in the first release (and if not shortly after).
Unfortunately I have so much fun running various spots that I have trouble putting real work today. It is a top priority feature though because without it 6max spots are not solvable and we definitely want them there.

The spots with 3 exits (say 3bb - 10bb - 22bb - 100bb) can be decently approximated having only 32GB of RAM. Spots with more exits (so limp etc.) will require 64GB to get close. Of course that's assuming you are smart about postflop trees and cut as many meaningless (from EV standpoint) branches as possible.
I did 100bb actually last two days on my computer (i7 3770k, 32GB of RAM) and it takes about 3-4 hours per spot to converge to something good so it is doable.
It remains to be seen how close those solutions are but the tests run so far comparing to some thing people solved on more/all flops suggest they are almost a perfect match.
Just wait till the weekend and see

Hi Punter,

I would like to know if the preflop solver is to be added to the Pro version enventually ? If so, how long will it take ?

Thanks

Eventually is a difficult question. There are no immediate plans for it and it looks unlikely in foreseeable future.

Does this work with Windows XP?