Quote:
Does edge work out of the box with more than 12 threads? If I have two Xeon hexa-cores I would be able to use all 24 hardware threads, correct?
Yes, it's compiled to use 128 threads as of now.
Quote:
I looked at 45 minutes of another video, highlighting an aggregation report, and he seemed to also have no trouble. But he mentions having several files, done before, and "now I will go to what I have, to save time"
There are two types of aggregation reports:
1)simple aggregation report where you aggregate EVs/EQs/general frequencies on a simple tree (across all turns or rivers)
2)aggregation report across multiple files (so you aggregate say cbet frequency across many flops using the saves you create by script for that).
The simple report is described here:
https://www.youtube.com/watch?v=VhG_YsEvfwU (point 7, see the video description)
The multifile report is described here:
https://www.youtube.com/watch?v=5Ozjfnatwms (point 5)
You need saves created by a script first to run it, how to run a script is described here:
https://www.youtube.com/watch?v=VhG_YsEvfwU (point 6)
Quote:
I want to run a set of flops for a tree that is already up and solved for postflop analysis.
Scripts are used to create and solve trees (for example a config on many boards). You don't need a tree that is already solved for that, you need a config (see the link above). There is only one way to generate a script in our GUI that is clicking "generate tree" button.
Quote:
PS or could you point me to a video showcasing 'exactly' how to do it with newest version of Pro?
I think the videos above do just that. Let me know if you need more help.
Btw, many things done in aggregation reports are done by runout EV comparison feature (hotness). You can find it under Analysis in the top menu (or press ctrl + H to bring it up). Just go to some turn card and try it, you will see EVs/EQs/overall strategies on all possible cards in this runout, like here:
https://gyazo.com/e045b358cfb6cbc1b3ace7380ec57142
I realize it would be useful to have a written tutorial. Unfortunately we think it's not a very practical decision to have one. Creating it takes a lot of time and then maintaining it takes even more time. That means there would be less features (as every interface change or a new thing would require re-writing corresponding part of the tutorial) and/or the software would be more expensive. There is a reason the trend these days is that most software doesn't come with written detailed tutorial - the cost is just too much.