There is a bug when trying to remove some lines. Please send us an email to support@piosolver.com and I will send you a dev version with a fix.

Yes, our friend is running PioCloud service, here:
http://piocloud.******.com/

You won't find more comprehensive solutions in the price range anywhere else.

Is your 15 hour estimate for 1bb/100 or 2bb/100? I assume the time it would take to reach the two would be quite different?

Also, is there any way to estimate what Nash distance Pio is capable of reaching in preflop calculations? In particular, for calculating complex trees 25BB and lower.

Are micro saves sufficient for flop aggregation analysis?

I think I've already noticed that only very ballpark estimations are possible as every tree is different. There isn't much more I can tell you - you will need to test things and develop your own intuition. For the record I have never run a tree bigger than 160GB (although many other people did 500GB and bigger).

It should reach 1bb-1.5bb/100 if the tree is straightforward postflop (although it sometimes manages to get lower than that).
The main problem is that we are using very little memory for postflop play so it's hard to get it exactly. Fortunatley it doesn't matter as to get preflop ranges correctly you just need good estimation of EVs not to pin postflop stragies exactly.

Yes, they are even better than full saves because they are instant to load.

How much ram need to calculate preflop 6 max at 100bb stacks for big blind with calculate precision 0.05bb /100? What is the precision in the calculation(bb/100) preflop with 60 flop subset, 176 flop subset?

We currently don't ship faster/more precise solver which uses more RAM so once you are able to build the tree the RAM requirements end there.

It won't converge to it for several reasons:
-we save a lot of memory postflop and therefore postflop play is not very precise (still provides good enough estimations of EVs though which is all that is needed for precise preflop solutoi)
-we use a trick which is based on calculating all-in preflop on 1755 flops (instead of a subset) this is good for solutoins but it requires MES/EVs to be approximated a bit, at 0.05bb you are already within the range of that error (this is also the reason the solver won't work well on very small subsets like 2 flops)
-our algorithm in the first place rarely goes to 0 accuracy, again the reasons are: memory usage and behavior on bigger trees with many bet sizes; it's easy to make it converge to 0.01 or w/e, it's harder to make its behavior decent on the kind of trees most of our users want to solve in reasonable time to reasonable accuracy and on reasonable hardware.

We calculate max exploit on the subset (obviously we can't do it on all flops as we don't have solution there in the first place) so the subset size is not relevant (maybe very small subsets are problamatic).

The goal of the preflop solver is to get preflop ranges and maybe see some overall frequencies/behavior postflop without going into too much detail. If you want more precise postflop play - use the postflop one. Fortunately adding bet sizes postflop is pointless when it comes to getting good preflop ranges as is going to very low accuracy overall (as most of it is in postflop play and preflop play is already good enough).

I get this error: "the file doesn't exists, or isn't a valid save" when making a multiple file aggregation report for a couple of files - all created together with a script.

There shouldn't be any issue, as the files load fine outside of the report - to illustrate this, if I load the first file in the directory and start the report from there, it will run until the 50th file or so. But, if I load a different file into PioViewer, it will generate the error on the 1st file (because in this case is not already loaded into the solver) - so to me, it seems to be a problem with how the aggregate report loads files, perhaps?

Is there a known issue and a workaround here? Other than manually moving the offending files from the folder and generating a report for each separately.

The files were created, and the report run, in v1.9.2, with the same preflop solver connected.

Are they postflop solutions?

The known issue is that the viewer doesn't automatically switch to the postflop solver when you run postflop files. Then if they are calculated with the preflop one the saves are not compatible so the postflop solver (which you are likely to use for the aggregated reports) can't open them.
It will be fixed soon (that is the scripts will automatically switch to the postflop solver) but for now maybe try connecting to the preflop solver before running the aggregation report on them (I am still assuming those are postflop saves, multifile reports on preflop saves are not supported).

They are all supposed to be postflop solutions, from within the same script, but for some some reason there are a tiny number of the files saved as preflop trees. I guess I accidentally ran portions of the script from within the preflop solver.

Is there an easy way to identify which files might be pre and post flop solved?

You can try to load them and see which solver viewer connects to.
Preflop files are also 2x smaller.

The postflop/preflop saves not being compatible is a design flaw unfortunately but making the files readable by both solvers and future proof was a bit of too much work for the time we were releasing the preflop solver.
It's one of the things I would like to fix when I have more time for cleaning out the code.

Hi,

I installed pio solver on my PC, but it's not working.
(see screenshot below)

In the black window, I activated my license.

Then, I opened pio viewer and went to connect --> pio solver edge (and edge19).
I paste the code and it said activation succesful. I click ok and then I get a message (picture 3) where I have to fill it in. When I cancel, it says failed to connect.

Can you help me out please?

Thanks

https://gyazo.com/4fec20199c53363bcfaf1d5a6e4c449a

It looks like it works (if it says "registered to"...). If it keeps asking for the key every time you start it the reason is usually incorrect date/time or timezone settings. Please verify those are correct and try again. If it still doesn't work email support@piosolver.com with your key/registered email.

Hi punter, I just purchased an upgrade from basic to pro.

I get the following message when using the updater

Update FAILED
ERROR:
You have provided malformed PioSOLVER download link.
Please read carefully the email with registration code and follow the exact steps described there.

Make sure you are inputting correct download link (the one in the email called personal download link).
If it's not that, maybe try downloading the updater again from HERE

If that doesn't help drop us an email to support@piosolver.com and I will check what's going on.

Thanks for the quick reply - I have sent you an email.

On Th9h8c2h any J or 7 are shown as 8 out straight draw in range explorer but on Th9h8h2h the J and 7 are not 8 out straight draws but 4 out straight draws. On Th9h8h2h a Q isn't recognized as straight draw.
Using basic 1.9.2.0

It seems to be correct although it shows the needed for more finely grained hand categories.

Well, yeah there should be 6 outs. It's noted. Again it would be useful to not count outs on those boards.

Yes, in the code I am made a simplistic assumption that if number of outs <4 then it's not a straight draw and if the number of outs <8 but at least 4 then it's "4 out draw". It's a lazy design by me, thanks for reporting it.

It is not because of counting outs but because of knowing the % of bluffing ranges.

I explained why it works the way it does (it counts outs and then categorizes the hand).
I am not sure what's your use case here. Let's say you want to select a bluffing range so you can then select:

-nothing in made hand categories
-uncheck combo draw in draws

I am likely missing something, so maybe you can give me a specific problematic example?

It worked. Thanks a lot.

Think I've asked something like this before, but is there any chance of being able to quickly construct scripts which alter a single variable of choice every time?

We don't have a functionality like that right now. That being said it's always useful if you provide a use case. If it's convincing enough it may end up higher on the to-do list.
A good thing about scripts is that they can be generated/modified by outside software easily so if we are not implementing something (lack of time and myriad of feature requests is the primary reason) you can always try to find someone who would.

For instance, I might want to see which of a number of flop sizes yields the biggest EV for a single size strategy on a flop (cf turns and rivers). I have to manually make scripts for this atm.

Alternatively, I might want to investigate the impacts of changes in one player's range to see how assumption-sensitive a strat is.

Finally, I might want to see to what extent permitting flop, turn and river donks affects strategy.

When I connect to a dedicated server that I rent, are there settings I should change to optimize PioSOLVER's calculation speed, both on the server side and within PioSOLVER?

Another feature request: I'd like a popup notification when a tree has finished solving (i.e. reached my requested level of accuracy).