Not rake, but ante) sorry, I'll replace it on the site

Will be done today. Working on it.

Hello everyone!

We are glad to say that we've released the new version of Simple Postflop v1.09. All users are encouraged to install update automatically when they launch the program.

So, the major changes in new version are:
1. For convenience “Merge Same Trees” and “Generate Boards” buttons are now placed out of “Apply Situation” button.

2. The new solution view was added in the interface - by combinations. It is available for every Show Mode (Played, EV, Strategy, Equity). Combinations view allows to filter matrix hands according to the chosen combinations.
It is worth mentioning that in the table which contains info by actions, equity is displayed according to the selected combinations.

3. There is a new button for solving all runouts for Turn and for River - “Calculate All”. It is placed in the drop-down list of “Runouts” button. To make button active you need to chose any node of a strategy tree.

After the button is clicked and all runouts are solved, it is possible to view runouts report.

4. Jobs functionality now added to preflop. The functionality is the same as it is on postflop. To run preflop jobs go to Standalone -> Preflop Jobs menu.

5. Now it is possible to merge preflop solutions with solved flops. To manage it you need to do following steps:
a. Open solved preflop tree;
b. Choose "Merge Flops" button which is in the drop-down list of the “Send” button.
c. Choose the folder where solved flops are stored.

6. Flops runout report added. To view it you need to follow steps:
a. Choose one of the Flop branches. Notice that you need to do it with already merged flop;
b. Click on the "Flop runouts button" which is placed in the drop-down list of “Merge Same Tree” button;
c. View the results of solved flops Also filter by cards is available in this report.

7. For the calculation of preflop with dead money, new building preflop mode added. It is called “Dead Money” mode (Mode -> Dead Money). When you switch from "Ante" mode to "Dead Money" mode or vice versa, the effective stack is automatically recalculated and the tree of bets rebuilds too according to the mode.

8. Now it is possible to add up to 6 actions per node of a strategy tree.

9. Suites filter is available in the main window of the program.

10. Now, you couldn't launch Simple Postflop while 888 poker or iPoker is running.

That is all stuff for today. We are keep on working further

Sick update and great description - keep up the good work!

Hello,

I have done the update today and I have an error message: "connection timeout error" when I am trying to log in.

Normal ?

I have sent you a message on Skype. Please check.

It is working now.

This weekend I was on a business trip, so I had limited access on Skype. Nevertheless, I tried as much as possible to maintain the stable operation of the program

Hey, after I have ran ''run outs - calculate all'', there is no runout-report (aggregation) opening - where can I find the report?
Is the report transferable to excel?

Regards,
Zrebna

Hi!

To open runouts report you need to click the button 'Runouts'.

You'll be able to export data from the report by right-clicking on the table with runouts data.

Thank you!^^

Hi!

One more concern:

I know that you can kinda explore the range-distribution by clicking ''edit strat'' or with the recent update now even also directly in the overview - there you can see how often certain handtypes do occur in %-tage.
Can you also somewhere see how the situation is combinatoric-wise -> for example how many combinations of sets player's 1 range has?

If so, where?
If not, I would like to request as a feedback to make it possible to also examine the combinatoric situation.

Hi. Just click mouse left + mouse right (at the same time) on the % in combinations view if I correctly understand your request.

Hi!

Thanks a lot - works

Would be also good when you can examine the aggregation for both payers' entire ranges and not only for subsets of them (check-range or bet-range) in order to be able to examine deeply RangevsRange-interactions.


edit:
Hint for other readers/user - the upper aspect you can do also now by lock-nodding for instance the check-range for both players' ranges to a 100% frequency and then it is effectively the entire range from both players...

Final question/request for now:
Is there a possibility for now or the future to check out not only nash EV of both players' ranges but also the hot/cold-Equity - so the EQ of player 1 range and the eq of the whole player's 2 range?

Best Regards,
Zrebna

This seems odd that spf wanna fold this high_EV-hand in little %?
Must be a crazy Nash-Equilibrium there...?

http://imgur.com/a/UWQXK

I'm pretty sure it's because of the high nash-distance... if solved more accurate I bet it won't be like this

Downloaded the software yest; first time using a gto program, is there any good tutorial videos out there? I watched the one on the main site but I don't really know wtf I'm doing

Yeah, might be true - Nash-dist. was 0.498.
Where can I set the the nash-dist. shall be lower?

check maybe out some vids on YT of Alex Sutherland.

Zrebna, thank you for your questions and sorry us for the late answer.

1) Could you please elaborate your idea about “hot/cold equity”? Example could be very useful for us.
Maybe the following information would be useful. In 1.09 you can select multiple rows in the upper table with hands. The equity, shown in the table below, is calculated for selected rows. So, if you are going to calculate all range against range you should select all rows.

2) Kooort gave you right answer. The Nash distance is very high. It looks like the calculation was interrupted or stopped.
What algorithm was used for your calculation? The best one for narrow ranges is A2.

jonmon101, for English speaking audience we could recommend GTORangeBuilder Youtube channel.

There, you can find a lot of useful information about GTO in general and about SPF in particular.

Alright I will give those a shot; thanks boys

Hi!

@1.)
I will elaborate on this by a screenshot from a Equity-tool which is not a competitor from you:

https://gyazo.com/cad6472a7c8e214963c13d84f45a3087

It shows basically the EQ for player's 1 entire range versus the equity of player's 2 entire range on the given texture JT4s.
So far I only can see that simple can offer here the NashEV-comparison of both player's ranges.
I could not select by the way rows, or do not know how to do it...

@ 2.)
I have used indeed A3 with low accuracy for flop - I will retry it with A2 with as well low accuracy for flop and if I do not adress it here again, then consider the case to be solved.

What is strange is, that if i run calculations with simplepostflop which do take more than 2 seconds, my computer heats up to about 100 degrees celsius, whereas it is usually at around 40-45 degrees due to a tool with the name ''coretemp''.
When I process calculations with other tools, of course the temperature also goes up, but not into critical areas (more like to 65 degrees).
I have already changed my internal paste, cleaned up my hardware and have let check my coolingsystem - all seems fine...

In the worst case, I will need to get a water-cooling-fan (which is though also not undangerous for the computer), but it kinda sucks that I only have the issue with simple-calcs.

Do you have any ideas for that?

Zrebna,

Thank you for the questions.

1) According to the screenshot, you would like to specify range for equity calculation. Am I right?
In the latest version, you can do the following:
- Select several rows in the hand table (with pressed Ctrl or Shift)
- Select all range by Ctrl+A
Equity in the table would be calculated for selected range.



Does it help?

2) It is very strange. What’s your PC specification? Could you check how many cores are involved in calculations with SPF and other tools? What about memory usage?
You can reduce number of CPU cores in “Settings of Calculation” (Standalone->Settings) or in the similar settings for Jobs (if you use them).

Can Nash distances be translated into a maximum % error bound for the strategy of any given combo? If you know of no rigorous way of doing this, do you have any way of estimating this that, in your experience, generally seems good?