On Saturday, September 24, 2022 at 8:25:47 AM UTC+1, Axel Reichert wrote:
....
>
> Would you agree that
>
> 50 exceeds 60 by at most 10
>
> is a true statement? If not, would you agree that
>
> 50 - 60 <= 10
>
> is a true inequality?
>
....

(In my opinion), it's worth noting that confusion between the use of inequalities in ordinary English
and mathematical English is quite widespread.

As a beginning maths undergraduate student in the mid-eighties in one of my first lectures, the class was
given various very simple inequalities and asked to assess their truth.
I can't remember the exact examples but it was something like:
3 > 5
3 >= 5
3 < 3
3 <= 3
5 > 3.

Most of these are easy for any adult who is paying attention, and doesn't have serious educational problems.
However, a large number of people in the class (I'd estimate maybe 8 out of around 25 attending) thought
that 3 <= 3 is a false statement because "3 can never be less than 3".
[These were pre-google days so such ignorance had to be exposed.]

Paul

"ah...Clem" <ah_clem@ymail.com> writes:

[Trice and Isight]

> I need to figure things out for myself sometimes. The first question
> that comes to mind is how often does it actually make a difference? So,
> I'm addressing that first. Bear with me...

Sure. It is just the scientific method to validate and reproduce other's
research. For Tom Keith's database about 11 % of the double decisions
and about 3 % of the take decisions differ. But you lose about 35 % more
equity.

> def ISightVerdict(LC,TC):
> POLT = LC + LC/6 -2
> if POLT <= TC + 4 and POLT >= TC:
> return("D/T")
> if POLT < TC + 2:
> return(("D/P"))
> return("ND/T")

Wrong.

if POLT < TC:
return("D/P")

Also, I find this hard to read because you start with D/T, then D/P,
then ND/T. This jumping around regarding the winning chances is asking
for future trouble when you read the code a year from now. But no
further programming lessons from my side. Figure things out for
yourself.

Best regards

Axel

"peps...@gmail.com" <pepstein5@gmail.com> writes:

> "Axel exceeded the speed limit by less than
> 10 miles per hour"
> certainly does _not_ include the possibility that you didn't exceed
> the speed limit at all!
>
> You really think it does??

No, nice example, point taken.

Axel

On September 23, 2022 at 6:22:14 AM UTC-6, Tim Chow wrote:

> On 9/23/2022 3:52 AM, MK wrote:

>> Ha ha..! Tim, Paul, Clem, Frank, folks, I was just joking. :)

> A rare case of R. B. Sahi admitting he's wrong!

You seem to be likening me to someone that I have no idea
about but I wouldn't deny being wrong about something false,
especiall if I fabricated it to begin with. You are an idiot!

> What next, claiming he knew that "corpi" wasn't a real word?

You just can't get that out of you, can you...? :) One more time,
I apologize for causing you so much psychological trauma. :(

MK

On 9/26/2022 4:32 AM, MK wrote:
> You just can't get that out of you, can you...? :) One more time,
> I apologize for causing you so much psychological trauma. :(

No, no...please cause me more of the same kind of psychological
trauma. I love it!

---
Tim Chow

On 9/25/2022 2:42 PM, Axel Reichert wrote:
> "ah...Clem" <ah_clem@ymail.com> writes:
>
> [Trice and Isight]
>
>> I need to figure things out for myself sometimes. The first question
>> that comes to mind is how often does it actually make a difference? So,
>> I'm addressing that first. Bear with me...
>
> Sure. It is just the scientific method to validate and reproduce other's
> research. For Tom Keith's database about 11 % of the double decisions
> and about 3 % of the take decisions differ. But you lose about 35 % more
> equity.
>
>> def ISightVerdict(LC,TC):
>> POLT = LC + LC/6 -2
>> if POLT <= TC + 4 and POLT >= TC:
>> return("D/T")
>> if POLT < TC + 2:
>> return(("D/P"))
>> return("ND/T")
>
> Wrong.
>
> if POLT < TC:
> return("D/P")

Yep. Good catch. Thanks.

>
> Also, I find this hard to read because you start with D/T, then D/P,
> then ND/T. This jumping around regarding the winning chances is asking
> for future trouble when you read the code a year from now. But no
> further programming lessons from my side. Figure things out for
> yourself.

The way I think about this is first I ask whether we're in the doubling
window. If so, it's D/T. If not, see if it's a pass. If neither then
ND/T. TG/P rarely occurs in race cubes.

It probably makes more sense to some to do the casess in numerical order
(ND/T, D/T, D/P).

On September 26, 2022 at 2:20:33 PM UTC+2, Tim Chow wrote:

> No, no...please cause me more of the same
> kind of psychological trauma. I love it!

Don't worry, I don't intend to stop. I am
satisfying my sadism while you satisfy
your masochism. It's a win-win. ;)

MK

"ah...Clem" <ah_clem@ymail.com> writes:

> It probably makes more sense to some to do the casess in numerical order
> (ND/T, D/T, D/P).

Yes, that was my point.

Axel