With MonkerViewer, is there a way to input custom ranges by hand? Only seeing the ones for purchase and exported from MonkerSolver

Has anyone purchased the NL 5-way solutions for $99? Worth it at all?

Hello OP, can you pm me? Been trying to get in contact with you.

Could someone explain how i can get a format of flop-turn-river 35%-50%-100% in an easier way than plugging each street on preflop solver?

It would be really helpful if you improve the way we input the bet sizes as I lose too much time atm for very basic setups. A similar way to pio would be the most optimal

select the bet size in the bottom right, then right click on one of the nodes and click apply to all postflop. it will apply it to that node and all nodes that branch off from it

Has anyone investigated the effects of different abstraction settings for PLO preflop sims? You need to make some major simplifications to get anything running on a reasonable amount of RAM (I am using 256GB)

I've read through this thread and all I could find was a post from the dev saying to keep the sizes of each street approx the same. From my fiddling around I think that would mean very few flop strength buckets, 'small' texture buckets on the turn and river.

I have also heard that for HU LHE you can run a sim with no turn or river texture buckets and it will come up with nearly identical preflop numbers as the full GTO solution (which has been determined for this variant). So maybe this works for PLO too. That's what I'm running now anyways. I'll let it go for a while and then compare it to the results from a smaller 3handed sim that uses less abstraction.

What VM software is a good fit for monker? I downloaded oracle virtual box but it seems clunky. Are the free VMs good enough for monker?

Why do you want to run Monker in a VM?

Any plans to get this software running on a server cloud? I would buy it right now if I didn't have to spend 2k+ on a computer to run it.

Also, It would be great to run it on practically any device just with an internet conection

How do multiple post flop bet sizes affect convergence for pre flop solving?

When solving pre flop with PioSOLVER, multiple sizes are not recommended since pre flop EVs won't change much, and the solver can struggle to converge when multiple size are used (especially the ALLIN).

Does the same apply for MonkerSolver? With default settings the AUTO tree building options insert multiple sizes in lots of places.

If I try to open it (either Monkersolverfree or Monkerviewer) nothing happens :_( . Using Windows 10 on both my notebook and main PC...

edit: fixed it. There were 3 different java versions active for some reason. Had to disable 2 of them

Jnandez in his course requeriments for working with monker solver. He says you should have a pc with at least 32gb ram or set up a virtual machine.

What does he mean by that? Maybe you can run monker solver in a ****ty pc with a virtual machine? I know little about this topic, excuse my ignorance

I was wondering the exact same thing atm. And I think i know the answer now. There are cloud supercomputer services which you could use do it for you if you dont want to setup your own computer. Checking out prices atm

Hi everyone.

Wanted to know some more about the system requirements for the solver.

Would a AMD ryzen 1700X or 1800X with 64gb RAM be solid for working on it?

Or would this be insuficient? Are there some more ideas or setups that work well?

Looking to upgrade my computer for working with the solver.

Budget between 1000-1500 dollar for:
processor, RAM, motherboard, graphic card, cpu cooler


Thanks!

Hey guys. Recently I work on HU PLOL mono boards and i found strange thing and don't know how to interpretate it or solve or wathever. Basically It's BU 90% open BB 3bets ~20%, BU flats (it drops ~10%, and 4b ~8% of 90% preflop opening range). When i type mono board for example Kc6c5c and i type in syntax for 3bettor 'cc' it shows ~50% of 3betting range. Whats wrong with it? It cannot be true that on mono with ~20% 3betting range we have flush 50% of the time, am i right? So the Q is how to examinate mono board with it or how to interpretate this? I don't know how to bite it cause Odds Oracle shows something different.

I'd go for 128GB but I know that eats up most of your budget...

post images of what you're seeing

https://ibb.co/cU0Zz5
here u have it.

I think it's because it groups all the offsuit combos together, you know what I mean?

Not really.

I'm not 100%, but I think it is showing up like that because for example 2c4c24 = [2c4c2h4h,2c4c2s4s,2c4c2d4d] and all the other 2424ds combos are all grouped together as 2424o

Hello,

HAve a few questions regarding the solver to get more of an idea about it:

- do multiple betsizes make the preflop sim more accurate? or doesnt it make a difference? since it is quite realistic ofcourse that we use 2 or 3 different betsizes in our postflop game. I made a 3 way sim btn sb bb with multiple postflop betsizes and raise sizes. quite a lot of work to put the tree together. i let it run untill 20 nodes and it is finally finished after 2 days. would you say nodes 20 is fine? or less is fine as well? or do we need more?


- Setting up the preflop tree it ask about the turn texture. How important are the differences between them? i set mine on medium for this but what is the reali difference between large or even perfect. Beside the size ofcourse.

What is recommended for this?

Thanks

Cheers glgl

Has anyone tried Ryzen chips for monkersolver? Any thoughts on this build/does anyone have something similar? The motherboard and chip supports adding another 64gb ram if I need it in the future.

https://gyazo.com/f76e3428685ef77f8cb1d50ba0aa0844

these questions feel a bit weird to me; you are using a solver that uses bucketing (along with some suit "concessions" for plo) to reduce the game size. while it is known that bucketing is lossy, it's tough to say how lossy it really is. the only (public) info on monkersolver is a (preflop chart) comparison with cepheus, which i don't think tells us a lot. so given this premise, why would you be interested in building more accurate postflop trees when solving for preflop?

additionally, while it is true that pio struggles to converge with multiple postflop sizes, it is simply a general thing that multiple postflop sizes don't affect average preflop evs much. ofc the abstraction loss is bigger for subtrees with larger sprs, but generally speaking if you use one of the unabstracted (nl) solvers and run simple trees vs complex trees over a lot of flops and average out the evs, there's not much of a difference to be seen. so if you have free ram for a sim, always allocate it towards reducing abstraction losses other than postflop bet sizes when solving for preflop.

I was mostly interested in hearing whether there was a reason for the AUTO tree builder to insert multiple sizings pretty much everywhere.

Fwiw, I have tested Monker's SB v BB equilibrium vs a benchmark Pio simulation (one geometrical bet size per street, 198 flops, 2bb/100 convergence) and found that {90 buckets, Perfect/Large/Large} and {30 buckets, Perfect/Perfect/Large} both reproduce the Pio results accurately. Frequencies same, and the shape of the ranges close to identical. In particular, the suited/offsuit polar regions in BB's 3B range are reproduced almost perfectly, which does not happen with default settings.

So we can verify that Monker reproduces accurate NLHE HU ranges when we push the accuracy settings up a bit.