Score estimator should be optional when defining a match

There have been previous discussions about whether the score estimator should be optional or not, but I couldn’t find this in users’ voice, so I added it. If you agree that the score estimator functionality should be optional when setting up a match, please vote. Thanks.

6 Likes

AndI wentthroughallthistrouble.

But I think if people want to put themselves at a disadvantage, they should remain free to estimate away.

2 Likes

thanks for linking the previous discussions. do you know whether the OGS team took a decision on the issue?

The short answer is no. I’m not aware of any decisions outside the status quo. I am aware that this discussion is at least 4 years old and I’m also aware of said status quo, which leads me to conclude that the decision is implied. But! I commend you for mentioning right off the bat that the discussion isn’t new. Even though it made the response [I had planned the second I saw the title] a little harder to sell.

That aside! While we’re at it. Scenario.

Suppose the estimation is largely correct:

  • if you’re ahead, you will now slack off so as not to jeopardize your lead, and tadaa, you have now lost focus
  • if you’re behind, you will now think something to the effect of “aw shit” and sure enough, you just lost focus

Suppose the estimation is incorrect:

  • if it says you’re ahead, you will now unduly slack off and lose even more points
  • if it says you’re behind, you will now unduly risk your lead

Best case, it’s correct and you’re behind, urging you to catch up. In all other cases, it’s detrimental. I’ve seen known streamers use it in the most absurd fashion and they’re adamant about it, and I wish they wouldn’t but I also don’t want to rob them of the moment of triumph once they realize for themselves and make the choice for themselves and start seeing SE as what it really is and what it really can’t be.

1 Like

Hello, since you asked directly - at the moment I am not aware of any plans to add an option to disable score estimation. However, if a lot of people really wanted the option, I am sure it can be discussed further :slight_smile:

I personally view it as a rather small “issue”, but it seems there really has been quite some discussions about it :smiley: So if it really is bothering some of you, cast your votes :smiley: not saying other things won’t get prioritized, but we will at least add it to the list.

index

3 Likes

You’re right it is not a big issue because national Go Associations can always use KGS or IGS for tournaments. If on the other hand you want OGS to be an option for serious competitive tournaments, this would probably by a relatively low cost change to make. I’m not sure about other countries but in Chile the official tournaments are on KGS and without the requested change I wouldn’t be able to recommend OGS as an alternative.

3 Likes

This sounds like that other person who requested static browser tab names so OGS could be used for streaming in European tournies.

I implemented it … nothing happened. And that was a far more concrete proposal than this one.

Here we have some random person who might recommend something to someone else in some country and as a result they might use OGS … doesn’t sound like much of an argument to implement a feature to me.

5 Likes

I’m not the same person, and I am not promising anything. I do understand that the experience you describe must have been frustrating and disillusioning, though.

Did you read what the proposal was? It seems pretty concrete to me: disable score estimator when analysis is disabled. What makes the OGS team think everyone wants the score estimator enabled by default, anyway? I don’t understand.

2 Likes

This is the proposal that I was referring to. The proposal that if we implement this, then it will increase the use of OGS in official tournaments.

The other proposal was “if you implement this feature, I (personally) will use this to stream in a competition”. It was more concrete because the person created the impression that they were in a position to implement this decision.

FWIW, I’m with you thinking that the score estimator should be disabled when analysis is disabled, and I think that should be the default.

The score estimator is not much use for estimating score (as smurph has pointed out) however I found that coming up through DDK, the picture that it draws can be quite useful for alerting me to where there are weaknesses on the board. I’ve definitely used it for benefit in that way.

I’m pretty sure that at the official tournament level, the kinds of things that it has helped me with would not be needed by those contestants though. By the time you are SDK you can probably see the cuts and effects I was missing. I’m not SDK yet, but I already use it a lot less this way than in mid-DDK range.

Unfortunately, it would be a back end change, so I can’t help with it.

My earlier post was not disagreeing with the idea “it should be disabled”. I was pointing out that the idea that doing so would in any way affect whether country level tournaments use OGS is spurious.

GaJ

2 Likes

Good evening.
I have not much to add to the idea, but to say that also me while reaching sdk, used to use a lot the stimator, 'cause gave me hints of weak groups and greater territlry to play. Withouth the stimator, i think i would have fall a lot in where to play.
And when we want some game to be considered official, we use KGS or IGS for that option that’s not on ogs.
Today i had a game in KGS for that itself.
And i understand what says alemitrani about the case in Chile (because i’m from Chile too) and we use KGS for tournaments and even just to reunite tuesdays.

So, i did my vote to the matter.

2 Likes

I’m not going to offer any arguements, just to say I am against the suggestion

I’d like to add that this is one of the few areas where KGS has clear advantages over OGS: KGS has a score estimator for use during review (good) but not during a match (good). On OGS the availability of the score estimator is exactly the wrong way around, it is available during the match (bad) and not during review (bad).

Reading this and the related threads that @smurph kindly linked, quite a few people seem to be in favour of the proposal but have not voted. If you are one of them, please vote here: https://ogs.uservoice.com/forums/277766-online-go-com-suggestions-and-feature-requests/suggestions/35350588-score-estimator-should-be-optional-when-defining-a

Thanks!

1 Like

I’m pretty sure it’s somewhere in the front end code. The score estimator project on GitHub reads:


As low level DDK, I use it in this way as well. I would like to keep it. (optional would be ok)

1 Like

It would be a back-end change to give a game an extra flag which is “scoring estimator disabled for this game”, which is what I had in mind when I wrote that.

It’s true that if we were to say that scoring estimator should be disabled with analysis is disabled, then a front-end change would suffice, and this is what the OP’s user-voice proposal asks for.

However, before we did that we’d have the have the argument from people who want the current behaviour (analysis disabled but estimator enabled).

1 Like

To be honest, i think OGS score estimator is so unreliable and incorrect, that using it while playing does not give any advantage at all. I highly recommend not using it in the first place.

Two things that SE is somewhat ok for:

  1. Opponent surprises you by resigning, and you want to make a quick check if the margin is really that wide. Because seriously, who really wants to use the effort to actually count when the game is already over.
  2. You’re messing with analysis and want to see how the score changes with different variations. This doesn’t work well until the game is near yose, since the SE is so inaccurate, but it might help you to choose between few end-game variations.
    Of course if the anal. tool is disabled, this isn’t possible.

I guess it wouldn’t be that bad, if SE would be turned off when analysis and conditional moves are also disabled.

ps
3. you are a spectator, so who cares

1 Like

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.