Yep makes sense, but I just think it'd be more useful if you could see what percentage of combos your range has compared to the total combos on that street. Unless i'm missing some useful effect to gauge the effect of card removal, it seems like it'd be a more useful stat. It'd be great for HUPLO where you're often working with pf ranges that comprise of 100% of hands.

You can always turn on street-by-street calculations to get the combos for each street (although it makes calculations a bit slower).

Slice is on sale for the Christmas season Use coupon code XMAS20 to get 20% off of your purchase.

Also, ordered a new Mac laptop (17" MBP) which should arrive over the holdiays...Barring any unforeseen circumstances, you can expect a Mac version of Slice early-ish in the new year!

Range30%!15%)&(ak**,a8**,a4**)

Dead:kd8d4hadahqdqhjdtc

The enumerate function does not treat the dead cards as it should. At least the Ah,Qh and Tc get included in the possible hands enumeration.

Hi Tiki,

This is a semi-bug. The dead cards need to be comma separated so your dead input should be: kd, 8d, 4h, ad, ah, qd, qh, jd, tc

Hope that helps.

Thanks it does.

[A*]h** when enumerated incorrectly gives 6084 combos. 8892 is the correct no..

BTW, nice range-syntax.

It's correct! The square brackets cause quite a bit of confusion though and I'll maybe have to reconsider the way it is implemented.

The range [A*]h** means that the only two cards that are suited are an A and one other card and the other two cards are non-suited.

The 8892 count includes double suited hands like Ah2h9cTc.

The correct calculation is:

ncombos = (suited A*h combos)*(random two non-hearts) - double suited hands
ncombos = (12)*(39 choose 2)- (12 suited heart combos)*(3 non heart suits*(13 choose 2))
ncombos = 12*741 - 12*(3*(13 choose 2))
ncombos = 8892 - 2808
ncombos = 6084

If you want the full 8892 combos I'd suggest you use filters like so:

Ah*h** {ss|ds}

So that means generate all Ah*h** hands and then filter for all single suited or double suited hands (i.e. eliminate tri-suited and mono-suited hands).

I really like the program, it's very robust and has a lot of good features.

I had a small feature request. I do a lot of Omaha calcs, and the ranges I enter can get really long and become tough to read. This is just the nature of good Omaha analysis, and is somewhat unavoidable. However, I do think that coloring text based upon suit would make it slightly easier to read. Here's an example range and how it would look colored:

AA**, Ah*hBB, JcTc9s8s, RdRd**

How it would look colored:

AA**, Ah*hBB, JcTc9s8s, RdRh**

Having the program automatically color suited cards as they are entered would make things easier to read. It would also be helpful to use the same color system in the program wherever there is a textual representation of a suited card.

neko, because i dont want to waste time downloading this if im not gonna use it, whats the difference between this product and stoxev or flopzilla? i use those two a decent amount and am always looking for new toys.

Thanks!

I think this would be really nice to have and as long as it is possible with the GUI toolkit I used I will add it. Thanks for the good suggestion


Slice is more like Stove than it is like StoxEV or Flopzilla. StoxEV is a really nice tool for testing the ev of different lines (e.g. should I bet the turn or c/r the turn). Flopzilla is a tool for analyzing how hard your hand hit's a flop. I don't think Flopzilla does an equity calculation at all. Both of those tools are Holdem only as well whereas Slice does a wide range of games.

Slice will feel much more like Stove than those other tools except for it has lots of additional features including a more powerful syntax for defining hand ranges. I think it was Entity that described Slice as PokerStove on crack.

Slice can directly load marked hands from your HEM or PT3 databases:



You can also save hand ranges that are available in a drop down menu for each player like so:



You can define aliases for hand ranges that you use commonly so instead of saying a players range is:

Player 1: 22+,9T+,J9+
Player 2: AQ,99,JJ

you could define an alias #UTG_LAG that represents that range and then just say:

Player 1: #UTG_LAG
Player 2: AQ,99,JJ

Slice also can graph your equity distribution on the next street like so:




or chart your equity on the next turn (or river card) like so:



there is more stuff too...you can read about most of it here:

http://sliceeq.com/index.php/documentation/

awesome thanks neko. i heart stove so im sure ill like this.

how many computers can I use a license on? any discounts?

I get the following error after connecting to my HEM database and trying to retrieve marked ahnds:

DB error while retrieving marked hands. Please report to support@sliceeq.com
'ascii' codec can't decode byte 0xe2 in position 49" ordinal not in range(128)

One purchase entitles you to use Slice on two computers. Just email support@sliceeq.com if you need a second license.



Thanks. I think I know how to fix this. Any chance you could send me the hand history for this hand so I can test it?

What is the main idea/difference behind having aliases vs saved ranges? Also, how come you cannot manually select cards for the alias and have to type them in, while you can do that for saved ranges?

Also, can you calculate equity on all turn and river cards for 2 or more ranges? Or is it just 1 range vs 2 hole cards

Really they are two very similar features and may end up getting merged together somehow at some point in the future.

The saved ranges allow you to organize ranges into different groups which can be handy for keeping track of different similar ranges.

The aliases are a little more "dynamic" for lack of a better word. What I mean by that is that you can use combinations of aliases, or aliases within saved ranges. For example imagine you have a few aliases defined like:

#big_pairs = JJ+
#small_pairs = 66-
#mid_pairs = 77-TT

Than you could use those in a range like:

Player 1: #big_pairs,#mid_pairs,#small_pairs

This is obviously a silly example since you could just use 22+ instead, but hopefully you see what I mean.

I also just discovered a bug in that you should be able to define compound aliases like #all_pairs = #big_pairs, #mid_pairs, #small_pairs but that is generating an error right now. Will have that fixed in the next release.


That's a good idea. No reason you shouldn't be able to do the same for aliases.

You can do it for multiple ranges.

Does the free DL have all the features ?? cause at the moment its not running equities for me ?

Are you the one who emailed me? The free version does not have all of the features but it does have heads up equity sims. I'll respond to your email with a suggestion on what might be going wrong...

There is now a trial Mac version of Slice available here: http://sliceeq.com/downloads/Slice.dmg (direct link since website has not been updated yet).

I say trial because I have only tested it on my 64bit Intel SnowLeopard MacBook Pro but I hope it will work on other versions of OSX as well as 32 bit machines. If some Mac users are willing to download and test it out and report back to me what version of OSX they are using and whether it is a 64 or 32 bit system I would greatly appreciate it!

Thanks!

Hi,

I keep getting "problem loading setting file" when I start up slice. I have a paid for version.

I tried uninstalling it and reinstalling in and I get a a message saying deletefile failed, code 5. Abort retry ingnore ?

I have tried running as admin as well as installing into a new folder.

thanks

Dwayman,

Sounds like maybe a settings file got corrupted for some reason.

Please try to delete the settings.json file from the following directory:

C:\Documents and Settings\DWAYMAN\Local Settings\Application Data\Slice\=

if you are on XP, or

C:\Users\DWAYMAN\AppData\Local\Slice\

if you are on Vista or Win 7. (Where DWAYMAN is replaced by your windows user name).

Perfect thanks !

how long does it takes to send a serial code? sent $$$ yesterday.