Quote:
so confirm me that I have to set it as in the following picture?
As long as bb is 100 then yes.
Quote:
I wanted to ask you, can you stop a preflop calculation and resume it later?
You can stop it and restart it later as long as the tree is in memory it is however doing so is not recommended as the preflop solver doesn't remember the state of the computations exactly and you may get more fluctuations if you keep stopping/restarting it. It's recommended to do it in one go as of now.
Quote:
When I calculate a preflop tree, usually the CPU works at 90%, there is some option where you can decide whether to use all the cores / threads or not?
It's under Tools->Configuration->Behavior->Max number of threads
0 means OS default (so max to efficiently use the CPU) you experiment with different values there.
Quote:
Hey guys, when will you roll out a software that also accommodates PLO?
Estimating time of software development is a proven impossible task so we are not attempting to give any ETAs. We also don't make any promises as a rule as that is counterproductive and doesn't help with anything. It's the best to wait and see what's available.
Quote:
This may be a silly question but if I don't build the tree, how does the script know the details for the tree I want to build?
The architecture is this:
Graphical Interace (PioViewer) opens the solver (engine) in the background when you do stuff like building, solving and browsing trees. When you run a script PioViewer opens another instance of an engine and that instance runs the script leaving the main engine free to do other task in the graphical interface. That's why you can run the script and stil be able to do various stuff in the GUI.
In principle you don't need the GUI to run a script. You can open the solver itself (PioSOLVER-pro19.exe if you have a pro version) and type "load_script my_script_name.txt" there. The graphical interface just does it for you.
Quote:
I don't have to tell it my sizes for all streets because it just uses the ones that are in the viewer?
When you click "generate script" button the viewer looks at the current tree config and generates the script containing that information. Then when you run the script another engine (solver) is opened and the script is sent to it.
Quote:
But I might be ok if I don't have to build the tree in the viewer before generating and running the script.
You do need to fill in the config but you don't need to build the tree itself.