I have one last hand range request, as well as an interface suggestion and a filter suggestion.

(1) The term "baby" is used to refer to a wheel card that is not an ace. If there were a single letter, say "Y" for instance, that would include baby cards, then Y = 2, 3, 4 or 5. This would be very helpful for Hi/Lo and Low games, and also for looking at Ace-rag type hands in Hold'Em, or wheel hands or hands with low danglers in Omaha High. This "baby" range designator would prove particularly useful in Razz and would be helpful too in deuce-to-seven.

(2) When I use the web interface for the odds calculator, I usually have in mind the initial hand to compare with other hands. So far, no problem. But when I have to compare that hand to two or more other hands, I run into a situation where I either have to use my mouse to move from the field for one hand to the field for the next hand, OR I must hit the tab key *several times* to move from one field to the next. Furthermore, the number of times I must hit the tab key to move to the next field varies by game type and also varies depending on the previous search, which inserts links to hand ranges, etc. It would be very convenient if I only had to hit the tab key *once* to move to the next hand field, no matter the game or previous search results.

(3) In Omaha it would be convenient to be able to simply specify that a hand is once-suited, without being particular. For example in Omaha High, the set of unpaired big cards that are once-suited in any way (2, 3, or 4 cards are suited together, but the hand is NOT double-suited) can currently be specified by:

BBBB{np} : mt | ts | ss

It would be nice if it were possible to shorten this to just:

BBBB{np} : s

or maybe use {os} to mean once-suited, which would be:

BBBB{np} : os

which would NOT included double-suited hands. Of course, the set of unpaired big cards that are suited in any way possible would be:

BBBB{np} : mt | ts | ss | ds

or equivalently:

BBBB{np} : !rb

1) Should be no problem

2) This is something I had noticed myself and already have planned. I use the keyboard a lot so this was already annoying me. I also want to allow you to hit enter to submit a calculation instead of having to hit the "full calculation link"

3) I like it and it's easy to implement.

It will likely be 24 hours before I can get to this but thanks for the great suggestions!

1) done
2) done
3) done

You stole my simulator

mine :




yours :

maven, I think we disagree on the definition of "thief".

You were clearly the first person to implement an online multiplayer variance simulator and yes I had seen yours before I made mine. You were not the first person to come up with the idea though, here is a variance simulator post from back in 2007 http://forumserver.twoplustwo.com/36...ariance-73786/

I had also seen pokerstove and ProPokerTools and a dozen other equity calculators before I created mine. I used ideas from all of them when I implemented mine. Same for the RoR, Bankroll, hand converter and winrate confidence calculators.

I am sorry that you feel I have wronged you in some way but I hope you can see my point.

^^^ name-calling deleted by _dave_ - no need! ^^^

OP has taken the concept and sigificantly improved on it. If someone took one of my free tools and improved on it I would be (a) flattered (b) glad a better tool now existed.

Neko you've made some great tools, thanks for all the work! I just made a blog post about it

WAT? significantly ?

look my simulator :

http://www.pokervariancesimulator.fr/

Don't need the link, I've used your simulator for ages. It's been very useful, thanks.

Question is, have you looked at OPs? Because the differences are huge. Not that it matters at all.

Now neko has come along and improved on your work. It fixes some of the issues of yours (like slow java installation, no negative marks on the Y axis), and improves on it in a multitude of ways. Off the top of my head - nicer looking graph, image that can be linked to and saved, Y axis in BBs, not $, only show min/max, and 3 additional types of graphs (probabilities of biggest downswing, longest breakeven stretch, and winrate distribution).

Plotting simulated winrates on a graph is hardly a unique concept. This is a nice implementation. What exactly is the problem?

this is not good to appropriate the work of people without asking their opinion.

you can say what you want, I feel robbed

maven,

What exactly do you believe I stole or appropriated from you?

The idea of plotting a random walk has been around for at least 100 years. The wikipedia page (http://en.wikipedia.org/wiki/Random_walk) on random walks even specifically mentions using them to model "the financial status of a gambler". It also includes an image that looks a lot like our variance simulators


Do you honestly think you should be the only person allowed to create an online variance simulator?

TY for your support Hood

you can feel what you want, but you weren't.

lots of trash talk deleted

_maven_ - if you have reason to believe Neko actually stole your code and is claiming it at his own, then you have a right to compensation and should seek legal advice for protecting your property.

An "idea" - such as "variance simulator" is not something to which one may claim ownership of even if you are the first person to ever think of such a thing (obv. you are not, those excel sheets are much older than when you set your website) - and I can't imagine those were the first studies on this topic either.

In software development (and no doubt in all manner of areas), such copying of ideas goes on all the time. OpenOffice "stole" the idea to make Calc from Microsoft Excel, who "stole" the idea from Lotus 1-2-3 who "Stole" it from VisiCalc and so on.

TableNinja "stole" my idea for a BetPot hotkey (I "stole" it from Roland's TableNavigator ), Holdem Manager "stole" the idea for parsing hands in to a database to track results and improve your game from PokerTracker, and so on.

Ideas are not something that may be protected - unless you keep them to yourself. A specific implementation of an idea e.g. software code is what is covered by copyright, and that implementation is what you'd be right to have a beef with if in fact your code has been copied.

P.S. Recruiting trolls from another forum to help bash someone is very poor form imo.

sorry for that but i was on tilt (and I still am)

Is there a some sort of limit to the number of characters that can be displayed and/or used in a single expression in the hand range tool?

I have run into a situation where concatenation of around seven or eight individual hand ranges using the or operator ("|") causes the window for the expression to scroll back to the front of the expression, making it hard or impossible to edit the end of the expression.

For example,

http://www.evplusplus.com/poker_tool...ertools&page=1

Try editing that expression toward the middle or end.

oh that is really annoying isn't it. I will check what is causing that problem. Thanks.

should be fixed now.

Neko, are you NEKOYAN on FTP ?

We might have played 7game 100/200 - 400/800 together.

I wish

Using the odds calculator for O8, I get this inexplicable error, even though the syntax of my hand ranges is correct:

Error: poker-eval: pyenum returned error code 1004

This has happened more than once, but doesn't happen often.

*edit* scratch that I can see the problem now.

Looks like for some reason a process was interrupted while storing a value in the cache and an empty range was being retrieved (in this case it should have retrieved your hand As8sKh4h).

It is fixed now but I'm going to rework some things to provide a little more fault tolerance.

I occasionally, not frequently (but not rarely, either), attempt a calculation and ... the progress bar gets to the halfway mark or so, and then ... the page just hangs. At this point, the progress bar stops showing any further progress, and the calculation never finishes.

I think this may happen when a calculation doesn't finish within ~ 30s (usually because someone other people are doing calcs at the same time) so the web server just gives up waiting. I'll see if I can figure something out.

Well, you seem to have solved the problem of no result being returned. However, now I experience the progress bar jumping to 100% briefly, followed by an immediate interim result, then the progress bar jumps back to the middle. Then, when the progress bar is about 90% or more, there are two or three interim results posted, eventually followed by the progress bar staying at 100% and the final result being shown.

I *guess* this behaviour is preferable to a failure.

Maybe I complain too much.