Replying out of order because I've missed the post #3491
Quote:
1. I want to see only the hands where i have "nothing", and look how many of them I bet. I can go to "range explorer" and check FDs for instance, but it won't show me how many of them I bet or check, as we can see in the main window of the browser. But in this main window, I can't just see only the FDs but the whole range together.
If you are using 1.10 version you can do the following:
1)Open Range Explorer
2)Select "nothing" and "no_draw" as well as "all" in the top right
It will now show you hands which are nothing and no_draw. It also shows how many combos are selected and what is combined strategy for those hands. For example here:
https://gyazo.com/0845e4e3d0c3fd31b7ace9c319ec0635
There is 15.9 combos of nothing and no_draw out of which you check 15.9 and bet 0.
Trying a cbet in the same tree:
https://gyazo.com/97b5a3b6117cfb233adb84c8475c8a51
There are 19.3 combos of nothing and no_draw out of which 15.9combos bet and 3.4 combos check.
Quote:
2. How many sizes per Street would you máximum reccommend to use and which ones?
(no rake)
It's a hard question I don't have answer to. Some smart people like a lot of sizes. Some smart people like to make the tree minimalistic to get results faster. It's very hard to answer in general.
Quote:
3. Can I round a tree, but keeping the same (aprox) percentages of folds and raises and calls? Because it changes the percentages a lot when you round it.
Right now it rounds per combo basis so if you round heavily (say to 0-50%-100%) the percentages may change a lot. It's unlikely to change as doing it in a way to preserve percentages isn't straightforward (once you round in one place the range everywhere else further down the tree is affected.
Quote:
4. if you save the tree as an small tree save instead of the complete one, should I calculate the whole tree again in order to use node locking and round functions? Because it tells "tree is incomplete"
Yes. You can rebuild the tree from a small save (this require executing solver command to do so) but it's recommended to just build the tree from scratch. It's faster and you get a memory check in case the tree is very big.