Registered: Mar 2014
Location:
Posts: 7

So based on the new rules we now measure the distance to the button differently.
The final number is the distance of the center of the stone to the button. If the stone does not cover the button it is easy since we only add 14.2cm to the measured distance. The calculation gets a bit more complicated when the stone is over the button.
From the document of Toyo Ogawa explaining the math behind the new calculation I created a simple web app that can do this.

If the new calculation method is used the app expects distances from the edge of the 4ft circle at 3 an 6 o'clock positions.

http://tomymmx.github.io/LSDCalculator

Comments appreciated.

Report this post to a moderator | IP: Logged

Registered: Jan 2015
Location:
Posts: 234

Link to the document you referenced?

Report this post to a moderator | IP: Logged

Registered: Mar 2014
Location:
Posts: 7

https://www.dropbox.com/s/plfcba5ls...vised.pptx?dl=0

That is the document/presentation that was circulated/used at the WCF General Assembly.

Report this post to a moderator | IP: Logged

Registered: Feb 2011
Location:
Posts: 272

The app would be improved with a diagram to demonstrate exactly what measurements are to be taken.

(A great but difficult feature would be to take the measurements and create a diagram showing the position of the stone and the lengths being measured to allow the user to self-correct.)

The app appears to have default values of:

0,0

So you have a locale issue. Most of the world uses "." as the decimal separator and will be confused and suspicious of this European way of doing things. What's next? 8 weeks of vacation? Communism! But your answers are given with "." as the separator.

But even worse is that these default values aren't actually used as default values. For example, the first thing I did when I saw 0,0 in each box was press "Calculate", giving me an answer of "NaN cm". I happen to know what NaN means but most of the world does not. But when I explicitly put 0 in each box then I get 14.2.

You don't do any error checking on the entries. It lets me put "Cow" and "Dog" in without a complaint.

The app only works once. If I change one of the numbers the calculation doesn't change, which is probably the way it should work. The should also be a "reset" button to clear the entries.

Report this post to a moderator | IP: Logged

Registered: Mar 2014
Location:
Posts: 7

So two things.
The thing was written in less then an hour so people have something to do the calculation if they need and don't have the official app.

I will think about some of the suggestions but will discard one... the idea that I should check if you input nonsense like "Cow" and "Dog". The think does not break and every user should know that measurements are done in numbers

But do keep the suggestions coming... in time I will improve the app so we get a nice tool. For now this was always meant to be a MVP and if nobody finds faults in the calculations I am happy

p.s.
I know this is a user experience problem for now, but if there is a number in the first box... the other two are not used... so the new calculation is only done if you leave the first box empty.

Report this post to a moderator | IP: Logged

Registered: Oct 2013
Location:
Posts: 559

I don't think that you can assume that every stone is 14.2mm radius. The WCF rules don't specify the diameter of the stones. I feel like this needs to be accounted for.

Is there a desire to make this calculator actually log and show previous distances, and have a running total for the team number?

Report this post to a moderator | IP: Logged

Registered: Mar 2014
Location:
Posts: 7

quote:

---

Originally posted by curlky
I don't think that you can assume that every stone is 14.2mm radius. The WCF rules don't specify the diameter of the stones. I feel like this needs to be accounted for.

Is there a desire to make this calculator actually log and show previous distances, and have a running total for the team number?

---

Report this post to a moderator | IP: Logged

Registered: Mar 2014
Location:
Posts: 7

quote:

---

Originally posted by ngm

(A great but difficult feature would be to take the measurements and create a diagram showing the position of the stone and the lengths being measured to allow the user to self-correct.)

---

Report this post to a moderator | IP: Logged

Registered: Oct 2015
Location:
Posts: 1

I have question about 14.2cm that is given as the radius. WCF rule R2. states:

A curling stone is of circular shape, having a circumference no
greater than 91.44 cm. (36 in.)

Plugging 91.44 in the formula r = c / 2π, yields radius of
14.55 not 14.2.

So why was 14.2cm chosen as the radius? There was no explanation
given in the Ogawa presentation.

__________________
Tom

Report this post to a moderator | IP: Logged

Registered: Mar 2014
Location:
Posts: 7

So at this point I have no answer for this.
I know that the maximum distance for an LSD is in the rules as the old distance + 14.2cm. Why was it chosen like this I don't know.
But at this point I am not sure how exactly the LSD measurements are to be handled. Will the value of 14.2 be used which in most cases gives a result that is a bit off or should the stones at a specific venue all be measured so the calculation can be as accurate as possible.

Looking at the provided document it seams to me that measuring errors (or in this case stone differences) of up to 5mm are small enough to not be cared about. Which makes some sense since this would only come to play in a really small number of cases. I think that this is the most likely way that it will be handled.
We will probably never be at the point that two teams can throw two stones and be at a combined difference that is less than a cm... and with that this becomes a non issue.

Report this post to a moderator | IP: Logged

Registered: Oct 2013
Location:
Posts: 559

quote:

---

Originally posted by TML*2
I have question about 14.2cm that is given as the radius. WCF rule R2. states:

A curling stone is of circular shape, having a circumference no
greater than 91.44 cm. (36 in.)

Plugging 91.44 in the formula r = c / 2π, yields radius of
14.55 not 14.2.

So why was 14.2cm chosen as the radius? There was no explanation
given in the Ogawa presentation.

---

Report this post to a moderator | IP: Logged

Registered: Feb 2011
Location:
Posts: 272

quote:

---

Originally posted by TomyMMX


What do you think about the way it works now?

---

Report this post to a moderator | IP: Logged

Registered: Jul 2022
Location:
Posts: 30

The Delta Faucet Leland series features a stunning Arctic Stainless finish that complements a range of kitchen settings. Its pull-down sprayer offers a variety of functions, including a powerful spray for heavy-duty cleaning and a gentle stream for everyday tasks. https://faucetspoint.com/best-brass-kitchen-faucets/

Report this post to a moderator | IP: Logged