Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

core error - bus dumped


devel / comp.theory / Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ computational dependence ]

SubjectAuthor
* How do we know H(P,P)==0 is the correct halt status for the input toolcott
+- How do we know H(P,P)==0 is the correct halt status for the inputolcott
+* How do we know H(P,P)==0 is the correct halt status for the inputwij
|`* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| +* How do we know H(P,P)==0 is the correct halt status for the inputwij
| |`* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | +* How do we know H(P,P)==0 is the correct halt status for the inputwij
| | |`* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | | `* How do we know H(P,P)==0 is the correct halt status for the inputwij
| | |  `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |   `* How do we know H(P,P)==0 is the correct halt status for the inputwij
| | |    `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |     +- How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |     `* How do we know H(P,P)==0 is the correct halt status for the inputwij
| | |      `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       +* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |`* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       | `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |  `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       |   `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |    `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |     `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |      `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |       `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |        `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       |         `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |          `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |           `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |            `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       |             `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |              `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |               `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |                `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |                 `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |                  `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |                   `* How do we know H(P,P)==0 is the correct halt status for the input to H?Richard Damon
| | |       |                    `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       |                     `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |                      `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |                       `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |                        `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       |                         +* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |                         |+* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       |                         ||`* How do we know H(P,P)==0 is the correct halt status for the input to H?Richard Damon
| | |       |                         || `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |                         ||  `- How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |                         |`* How do we know H(P,P)==0 is the correct halt status for the inputMalcolm McLean
| | |       |                         | +- How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |                         | `* How do we know H(P,P)==0 is the correct halt status for the inputMalcolm McLean
| | |       |                         |  +* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       |                         |  |`* How do we know H(P,P)==0 is the correct halt status for the inputAndré G. Isaak
| | |       |                         |  | `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       |                         |  |  `* How do we know H(P,P)==0 is the correct halt status for the inputAndré G. Isaak
| | |       |                         |  |   `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |                         |  |    `* How do we know H(P,P)==0 is the correct halt status for the inputAndré G. Isaak
| | |       |                         |  |     `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       |                         |  |      `* How do we know H(P,P)==0 is the correct halt status for the inputAndré G. Isaak
| | |       |                         |  |       `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |                         |  |        `* How do we know H(P,P)==0 is the correct halt status for the inputAndré G. Isaak
| | |       |                         |  |         `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |                         |  |          `* How do we know H(P,P)==0 is the correct halt status for the inputAndré G. Isaak
| | |       |                         |  |           `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |                         |  |            `* How do we know H(P,P)==0 is the correct halt status for the inputAndré G. Isaak
| | |       |                         |  |             `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       |                         |  |              `* How do we know H(P,P)==0 is the correct halt status for the inputAndré G. Isaak
| | |       |                         |  |               `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       |                         |  |                `- How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |                         |  `* How do we know H(P,P)==0 is the correct halt status for the inputMalcolm McLean
| | |       |                         |   `- How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |       |                         `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |                          +* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       |                          |`* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |                          | `* How do we know H(P,P)==0 is the correct halt status for the input to H? [ key axolcott
| | |       |                          |  `- How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |       |                          `* How do we know H(P,P)==0 is the correct halt status for the inputwij
| | |       |                           `- How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |       `* How do we know H(P,P)==0 is the correct halt status for the inputwij
| | |        `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |         `* How do we know H(P,P)==0 is the correct halt status for the inputwij
| | |          +* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |          |`* How do we know H(P,P)==0 is the correct halt status for the inputwij
| | |          | +- How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |          | `* How do we know H(P,P)==0 is the correct halt status for the inputdklei...@gmail.com
| | |          |  `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |          |   `* How do we know H(P,P)==0 is the correct halt status for the input to H?Richard Damon
| | |          |    `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |          |     `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |          |      `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| | |          |       `- How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |          `* How do we know H(P,P)==0 is the correct halt status for the inputChris M. Thomasson
| | |           `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| | |            `* How do we know H(P,P)==0 is the correct halt status for the inputChris M. Thomasson
| | |             `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |              `* How do we know H(P,P)==0 is the correct halt status for the inputChris M. Thomasson
| | |               `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |                `* How do we know H(P,P)==0 is the correct halt status for the inputChris M. Thomasson
| | |                 `* How do we know H(P,P)==0 is the correct halt status for the input to H?olcott
| | |                  `- How do we know H(P,P)==0 is the correct halt status for the input to H?Ben Bacarisse
| | `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| |  `* How do we know H(P,P)==0 is the correct halt status for the inputolcott
| |   `- How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
| `* How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
+- How do we know H(P,P)==0 is the correct halt status for the inputRichard Damon
`* How do we know H(P,P)==0 is the correct halt status for the input to H?Ben Bacarisse

Pages:12345678910111213141516171819
Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<Z2BVI.1293$F26.792@fx44.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20231&group=comp.theory#20231

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!feeder1.feed.usenet.farm!feed.usenet.farm!newsreader4.netcologne.de!news.netcologne.de!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx44.iad.POSTED!not-for-mail
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<87r1elihh9.fsf@bsb.me.uk> <c9ydnS0MB5tqG7_8nZ2dnUU7-R_NnZ2d@giganews.com>
<87czq5i9u0.fsf@bsb.me.uk> <srednU_7RdGxPr_8nZ2dnUU7-eHNnZ2d@giganews.com>
<87y28tgt3w.fsf@bsb.me.uk> <xamdnei4F5CzM7_8nZ2dnUU7-KPNnZ2d@giganews.com>
<87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com>
<87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com>
<5zqVI.10579$kQ4.10540@fx13.iad>
<Ea2dndkCwo0bzbv8nZ2dnUU7-dHNnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <Ea2dndkCwo0bzbv8nZ2dnUU7-dHNnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Lines: 174
Message-ID: <Z2BVI.1293$F26.792@fx44.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Wed, 25 Aug 2021 20:15:52 -0400
X-Received-Bytes: 8635
 by: Richard Damon - Thu, 26 Aug 2021 00:15 UTC

On 8/25/21 10:15 AM, olcott wrote:
> On 8/25/2021 7:19 AM, Richard Damon wrote:
>> On 8/24/21 11:53 PM, olcott wrote:
>>> On 8/24/2021 7:35 PM, Ben Bacarisse wrote:
>>>> olcott <NoOne@NoWhere.com> writes:
>>>>
>>>>> On 8/24/2021 9:09 AM, Ben Bacarisse wrote:
>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>
>>>>>>> On 8/23/2021 10:09 PM, Ben Bacarisse wrote:
>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>>
>>>>>>>>> On 8/23/2021 6:26 PM, Ben Bacarisse wrote:
>>>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>>>>
>>>>>>>>>>> On 8/23/2021 2:30 PM, Ben Bacarisse wrote:
>>>>>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>>>>
>>>>>>>>>>> I ignore dishonest dodges away from the point at hand.
>>>>>>>>>> OK, let's do that:
>>>>>>>>>>        "⟨Ĥ⟩ ⟨Ĥ⟩ is not a string that encodes a halting
>>>>>>>>>> computation"
>>>>>>>>>> is wrong.  You wrote that immediately after a line showing that Ĥ
>>>>>>>>>> applied to ⟨Ĥ⟩ halts.  Everything since then has just been
>>>>>>>>>> dodging this
>>>>>>>>>> error.
>>>>>>>>>>
>>>>>>>>>>> When we define Ĵ to be exactly like Ĥ except that it has a UTM
>>>>>>>>>>> at Ĵ.qx
>>>>>>>>>>> instead of a simulating halt decider then we can see that Ĵ
>>>>>>>>>>> applied to
>>>>>>>>>>> ⟨Ĵ⟩ never halts.
>>>>>>>>>> The details are mess, but basically, yes.  Detail errors (that
>>>>>>>>>> would get
>>>>>>>>>> your paper rejected out of hand) available if you ask really
>>>>>>>>>> nicely.
>>>>>>>>>
>>>>>>>>> Which details do you think are incorrect?
>>>>>>>>
>>>>>>>> A UTM is not a decider so the hat construction can't be applied to
>>>>>>>> it.
>>>>>>>> And if we make a "UTM-decider" (a TM that is a pure simulator
>>>>>>>> except
>>>>>>>> that is accepts those computations whose simulations terminate) we
>>>>>>>> still
>>>>>>>> can't apply the hat construction because it won't have a rejecting
>>>>>>>> state.  Thus your use of "exactly like Ĥ except..." is, at best,
>>>>>>>> disingenuous.  The differences must be greater than the "except..."
>>>>>>>> clause suggests.
>>>>>>>
>>>>>>> My whole purpose was to simply show what happens when the simulating
>>>>>>> halt decide at Ĥ.qx only simulates its input.
>>>>>> I know, but you wanted to know what details you'd got wrong.
>>>>>>
>>>>>
>>>>> If my plan was to swap the simulating halt decider at Ĥ.qx with a UTM
>>>>> and then rename this machine to Ĵ and I did swap swap the simulating
>>>>> halt decider at Ĥ.qx with a UTM and rename this machine to Ĵ then it
>>>>> is a God damned lie that I got anything wrong.
>>>>
>>>> No.  You won't get it unless you really try.
>>>>
>>>>>>> We can still have the same final states, except now that are
>>>>>>> unreachable dead code.
>>>>>> Except you show below this unreachable state being reached:
>>>>>
>>>>> No I do frigging not.
>>>>
>>>> Yes you did.  I quoted you: Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn.
>>>>
>>>>> The code is still there but the infinite cycle
>>>>> from Ĵ.qx to Ĵ.q0 prevents it from ever being reached.
>>>>
>>>> No.  You are totally at sea.  I did my best to explain but you'd
>>>> have to
>>>> want to learn to make any progress.
>>>>
>>>>>>      Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn
>>>>>> The TM at Ĵ.qx is your "UTM-decider" with an unreachable reject
>>>>>> state.
>>>>>> Do you see why I don't think you know what you are saying?
>>>>>
>>>>> The you imagine what I mean to say instead of examining what I
>>>>> actually say is your mistake.
>>>>>
>>>>> This machine
>>>>> Ĥ.q0 ⟨Ĥ1⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ ⊢* Ĥ.qn
>>>>>
>>>>> is transformed into this machine:
>>>>> Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn // a machine stuck in
>>>>> infinitely nested simulation
>>>>
>>>> You don't know what this notation means.  I don't think I can help you
>>>> with this.
>>>>
>>>>>>>>>>> There is an infinite cycle from Ĵ.qx to Ĵ.q0.
>>>>>>>>>> No, but that's just because you've never written a UTM so you
>>>>>>>>>> don't know
>>>>>>>>>> how such a TM would work.  Ĵ applied to ⟨Ĵ⟩ is non-halting but
>>>>>>>>>> there
>>>>>>>>>> will not be a cycle from Ĵ.q0 -> Ĵ.qx -> Ĵ.q0...[1]
>>>>>>>>>>
>>>>>>>>>>> Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn
>>>>>>>>>>
>>>>>>>>>> Eh?  You've just said that Ĵ applied to ⟨Ĵ⟩ is non-halting.
>>>>>> This needs to be addressed.
>>>>>
>>>>> That you don't believe that there is a cycle from Ĵ.qx to Ĵ.q0 is
>>>>> flatly wrong.
>>>>
>>>> No, I'm right about that.
>>>
>>> Try and exaplain how you are right about that.
>>
>> The fact that the code for J (or P) has absolutely no path to go from
>> the state qx to the state q0 OF THE SAME EXECUTION (which is what the
>> diagram is showing).
>>
>> Yes, there is a 'virtual' connection from qx of one invocation to a q0
>> of a simulated embedded invocation, but that state is NOT the outer q0.
>>
>> Turing Machine P or J NEVER go back to their own q0 state.
>>
>> You could perhaps say we have a nesting of
>>
>> P0.q0 -> P0.qx -> P1.q0 -> P1.qx ...
>>
>> But that is a NESTING, not a LOOP.
>>
>> They are different.
>
> None-the-less we have infinitely nested simulation that would never halt
> unless the simulating halt decider aborts its simulation of its input.

You HAVE to decide what your H is doing.

Either

1) H NEVER aborts the simulation, at which point Hn(<Hn^>, <Hn^>) never
returns an answer as is thus a failed decider

2) H Does abort the simulation so it can answer and then it turns out
that Ha^(<Ha^>) is a Halting computation.

The only way to have it both ways is for H to not be a computation,
(Which actually seems to be the case) in which case it also fails to be
a valid Halt Decider because it isn't the comptational equivalent of a
Turing Machine to be the Turing Machine H.

I think your problem is you just don't understand that last statement.

>
> This conclusively proves that the simulating halt decider at Ĥ.qx ⟨Ĥ1⟩
> ⟨Ĥ2⟩ must abort the simulation of this input which conclusively proves
> that this input never halts.
>

Nope. Just shows you don't know what you are talking about.

>>
>>>
>>>
>>>> But you are piling errors on errors now so
>>>> responding is getting harder.  What you are not responding to is the
>>>> contraction.  Even though there is no cycle from Ĵ.qx to Ĵ.q0, Ĵ
>>>> applied
>>>> to ⟨Ĵ⟩ is indeed non-halting you keep showing that it halts.  Even if
>>>> there were a cycle from Ĵ.qx to Ĵ.q0 you would still be contradicting
>>>> yourself.
>>>
>>
>
>


Click here to read the complete article
Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ conversation has ended? ]

<4fqdnePjhJAvQ7v8nZ2dnUU7-e3NnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20232&group=comp.theory#20232

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!feeder1.feed.usenet.farm!feed.usenet.farm!tr2.eu1.usenetexpress.com!feeder.usenetexpress.com!tr2.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 25 Aug 2021 19:22:10 -0500
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ conversation has ended? ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com> <xamdnei4F5CzM7_8nZ2dnUU7-KPNnZ2d@giganews.com> <87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com> <87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com> <87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com> <87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com> <87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com> <87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com> <87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com> <87zgt69xah.fsf@bsb.me.uk> <tqadndv0qJ8vOLj8nZ2dnUU7-R_NnZ2d@giganews.com> <1LCdnZZtHK3SK7j8nZ2dnUU7-R_NnZ2d@giganews.com> <87lf4pa56n.fsf@bsb.me.uk> <feudnRmpetF2G7v8nZ2dnUU7-VfNnZ2d@giganews.com> <87czq19wx0.fsf@bsb.me.uk> <Y7adnS3RyacCCbv8nZ2dnUU7-UWdnZ2d@giganews.com> <p_AVI.9$tG6.3@fx39.iad>
From: NoO...@NoWhere.com (olcott)
Date: Wed, 25 Aug 2021 19:22:09 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <p_AVI.9$tG6.3@fx39.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <4fqdnePjhJAvQ7v8nZ2dnUU7-e3NnZ2d@giganews.com>
Lines: 88
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-QfOZyJav55wunt0r8Xl2YS0AySC7PiZdhtgVUdpuv6KJDRNsEnUWObVjY9khzQST6FqY1mEwRHWaFi8!SK6iLMOoZR2MG6e8kW7cGKPIv+o3egg/jJ/HmZrMVDL3zbDkk8OeDDqjS02EpqIZW9QActKB0U7/!T9A=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 5694
 by: olcott - Thu, 26 Aug 2021 00:22 UTC

On 8/25/2021 7:11 PM, Richard Damon wrote:
> On 8/25/21 3:06 PM, olcott wrote:
>> On 8/25/2021 1:55 PM, Ben Bacarisse wrote:
>>> olcott <NoOne@NoWhere.com> writes:
>>>
>>>> On 8/25/2021 10:56 AM, Ben Bacarisse wrote:
>>>
>>>>> The halting problem is about the existence of a TM that accept those
>>>>> string pairs (and only those string pairs) that encode halting
>>>>> computations.  All other strings are to be rejected.  The halting
>>>>> theorem states that no TM is a such a decider -- every TM fails to
>>>>> correctly classify at least one string pair.
>>>>>
>>>>> You claim to have a TM, unfortunately called H, which is a halt
>>>>> decider.
>>>>> (Yes, you sometimes deny it is a general halt decider but you keep
>>>>> quoting me saying your algorithm is one, so I presume you agree that it
>>>>> must be one.)
>>>
>>> So you are indeed claiming to have a general halt decider!  That's a
>>> grand boast!  (You need to say "no" if you don't want this to be taken
>>> as your real position.)
>>>
>>>>> You tell us, again and again, that the computation of Ĥ applied to the
>>>>> encoding of Ĥ (written ⟨Ĥ⟩) is a halting computation.  You are quick to
>>>>> jump in and say that it "only halts because... reason", but it's a
>>>>> halting computation whatever the reason.
>>>>>   That halting computation is encoded as the string pair ⟨Ĥ⟩ ⟨Ĥ⟩.  (I
>>>>> prefer a notation that makes the pairing of an encoded TM and some
>>>>> input
>>>>> explicit, but that boat sailed years ago.)
>>>>>   You also tell is that H rejects the string pair ⟨Ĥ⟩ ⟨Ĥ⟩.  I.e. you
>>>>> tell
>>>>> us everything we need to know to be sure that H is wrong about at least
>>>>> this one halting problem instance.
>>>>
>>>> Ĥ.q0 ⟨Ĥ1⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ ⊢* Ĥ.qn
>>>>
>>>> Until you understand that the input to Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ is not a halting
>>>> computation there is no sense continuing this one way dialogue.
>>>
>>> Until you understand that ⟨Ĥ1⟩ ⟨Ĥ2⟩ equals ⟨Ĥ⟩ ⟨Ĥ⟩ and that ⟨Ĥ⟩ ⟨Ĥ⟩ is a
>>> string that should be accepted you are just blowing smoke.
>>>
>>
>> (a) While the simulating halt decider at Ĥ.qx remains in pure simulation
>> mode its input ⟨Ĥ1⟩ ⟨Ĥ2⟩ never halts.
>
> Because H happens to stop the simulation too soon.
>

Ĵ.q0 ⟨Ĥ1⟩ ⊢* Ĵ.qx ⟨Ĵ1⟩ ⟨Ĵ2⟩ ...

You are pretty intelligent to be able to catch the subtle nuance of how
Ĵ applied to ⟨Ĵ⟩ is not exactly a cycle from Ĵ.qx to Ĵ.q0 because these
are two different instances.

That is why it seems to me that you could only be playing head games
when you fail to acknowledge that Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ specifies infinitely
nested simulation that never stops unless the simulating halt decider at
Ĥ.qx aborts its simulation.

> Put that exact same input into a compatible UTM, and it will run to a Halt.
>
> THEREFORE, H WAS WRONG to abort the simulation and declair non-halting.
>
>
>>
>> (b) Every computation that never halts while its simulating halt decider
>> remains in pure simulation mode is a computation that never halts.
>
> FALSE STATEMENT. PERIOD>
>
>
>>
>> Too disingenuous to continue. You utterly refuse to directly examine my
>> proof provided immediately above that is not the sign of an honest
>> dialogue.
>>
>

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<_8BVI.106$GD7.95@fx23.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20233&group=comp.theory#20233

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!news-out.netnews.com!news.alt.net!fdc2.netnews.com!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx23.iad.POSTED!not-for-mail
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<87czq5i9u0.fsf@bsb.me.uk> <srednU_7RdGxPr_8nZ2dnUU7-eHNnZ2d@giganews.com>
<87y28tgt3w.fsf@bsb.me.uk> <xamdnei4F5CzM7_8nZ2dnUU7-KPNnZ2d@giganews.com>
<87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com>
<87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com>
<87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Lines: 147
Message-ID: <_8BVI.106$GD7.95@fx23.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Wed, 25 Aug 2021 20:22:17 -0400
X-Received-Bytes: 6945
 by: Richard Damon - Thu, 26 Aug 2021 00:22 UTC

On 8/25/21 1:11 PM, olcott wrote:
> On 8/25/2021 10:19 AM, Ben Bacarisse wrote:
>> olcott <NoOne@NoWhere.com> writes:
>>
>>> On 8/24/2021 7:35 PM, Ben Bacarisse wrote:
>>>> olcott <NoOne@NoWhere.com> writes:
>>>>
>>>>> On 8/24/2021 9:09 AM, Ben Bacarisse wrote:
>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>
>>>>>>> On 8/23/2021 10:09 PM, Ben Bacarisse wrote:
>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>>
>>>>>>>>> On 8/23/2021 6:26 PM, Ben Bacarisse wrote:
>>>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>
>>>>>>>>>>> There is an infinite cycle from Ĵ.qx to Ĵ.q0.
>>>>>>>>>>
>>>>>>>>>> No, but that's just because you've never written a UTM so you
>>>>>>>>>> don't know
>>>>>>>>>> how such a TM would work.  Ĵ applied to ⟨Ĵ⟩ is non-halting but
>>>>>>>>>> there
>>>>>>>>>> will not be a cycle from Ĵ.q0 -> Ĵ.qx -> Ĵ.q0...[1]
>>>>>>>>>>
>>>>>>>>>>> Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn
>>>>>>>>>>
>>>>>>>>>> Eh?  You've just said that Ĵ applied to ⟨Ĵ⟩ is non-halting.
>>>>>>
>>>>>> This needs to be addressed.
>>>>>
>>>>> That you don't believe that there is a cycle from Ĵ.qx to Ĵ.q0 is
>>>>> flatly wrong.
>>>>
>>>> No, I'm right about that.
>>>
>>> Try and exaplain how you are right about that.
>>
>> It follows directly from the "hat" construction.  The TM "at" Ĵ.qx is
>> (in effect) J.  None of entries in J's state transition function can
>> refer to state Ĵ.q0 because that is a new stated added (along with a few
>> others) with the sole purpose of doing the copy of the input.  There is
>> simply no path from Ĵ.qx to Ĵ.q0.
>>
>
> There is a path from Ĵ.qx to the Ĵ.q0 of another instance.
> infinitely nested simulation with copying is a little less like infinite
> recursion than infinitely nested simulation without copying,
> none-the-less it is still obviously infinite.

Except that notation is of a SINGLE instance.

>
>> And, similarly, since J is a UTM with only an accepting state (qy) the
>> line you keep writing
>>
>>    Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn
>>
>> is bogus. 
>
> Like I said before it is not bogus. A machine can possibly be defined
> with unreachable states. When Ĥ is converted to Ĵ by a single change to
> Ĥ this new Ĵ has unreachable states.
>
> I wanted to make a single change to Ĥ to derive Ĵ to make the single
> point that Ĥ never stops running unless its aborts the simulation of its
> input at Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ thus conclusively proving that this input never
> halts according to this criteria:
>
> Simulating Halt Decider Theorem (Olcott 2020):
> A simulating halt decider correctly decides that any input that never
> halts unless the simulating halt decider aborts its simulation of this
> input is an input that never halts.
>

A FALSE Theorem.

> Although I call it a theorem it is actually a little stronger than that
> because it is self-evidently true.

Nope. It VIOLATES the definition of Halting.

Maybe YOU are the UNSOUND piece.

It is only a Peter Olcott evident 'truth', but it is actually false.

>
> the·o·rem
> /ˈTHēərəm,ˈTHirəm/
> a general proposition not self-evident but proved by a chain of
> reasoning; a truth established by means of accepted truths.
>
>> You can add states to a TM at will, so J or Ĵ can be
>> (pointlessly) given a rejecting state qn, but there can't be any
>> configuration sequences that end in it.
>>
>
> Of course it is the case that any states following infinitely nested
> simulation will never be reached. I knew that when I derived the
> specification for Ĵ by making a single change to Ĥ.
>

Except that it isn't infinitely nested, at least if H does return the
non-halting answer. Your 'analysis' uses flawed logic, and is thus UNSOUND.

> You seems to have trouble with more than one step so I limited my change
> to a single step.

You seem to have a problem accepting actual truth.

>
>> And the line is bogus for another reason.  You are correct that Ĵ
>> applied to ⟨Ĵ⟩ is non-halting (thought not because of the cycle you
>> imagine was there) and this line directly contradicts that fact.  You
>> need to write
>>
>
> There is a cycle following Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ to another instance of Ĵ.q0.
> It is a cycle within the Ĵ template.

No, it is NOT withing the 'template'

Yes, J^ will be an infinite computation. But J^ isn't H^ so the answer
doesn't transfer.

Maybe only in your broken logic system where you have introduced false
truths so nothing works right.

>
> Ĵ copies its input ⟨Ĵ1⟩ to ⟨Ĵ2⟩ then
> simulates this input Ĵ1 with its input ⟨Ĵ2⟩
>
> which copies its input ⟨Ĵ2⟩ to ⟨Ĵ3⟩ then
> simulates this input Ĵ2 with its input ⟨Ĵ3⟩
>
> which copies its input ⟨Ĵ3⟩ to ⟨Ĵ4⟩ then...
>
>
>>    Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* ∞
>>
>> or, if you don't need to show the one and only literal string copying
>> step, just Ĵ.q0 ⟨Ĵ⟩ ⊢* ∞.
>>
>
>

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<Y7udnRjYJLheQrv8nZ2dnUU7-avNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20234&group=comp.theory#20234

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!tr3.eu1.usenetexpress.com!feeder.usenetexpress.com!tr3.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 25 Aug 2021 19:26:43 -0500
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com> <87r1elihh9.fsf@bsb.me.uk> <c9ydnS0MB5tqG7_8nZ2dnUU7-R_NnZ2d@giganews.com> <87czq5i9u0.fsf@bsb.me.uk> <srednU_7RdGxPr_8nZ2dnUU7-eHNnZ2d@giganews.com> <87y28tgt3w.fsf@bsb.me.uk> <xamdnei4F5CzM7_8nZ2dnUU7-KPNnZ2d@giganews.com> <87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com> <87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com> <87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com> <87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com> <87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com> <87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com> <87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com> <87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com> <5zqVI.10579$kQ4.10540@fx13.iad> <Ea2dndkCwo0bzbv8nZ2dnUU7-dHNnZ2d@giganews.com> <Z2BVI.1293$F26.792@fx44.iad>
From: NoO...@NoWhere.com (olcott)
Date: Wed, 25 Aug 2021 19:26:42 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <Z2BVI.1293$F26.792@fx44.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <Y7udnRjYJLheQrv8nZ2dnUU7-avNnZ2d@giganews.com>
Lines: 169
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-qxfTstJEmTUlVllZNydflEv4auIBp4FN3+GmCk5gy8uLTFCf/ef3pBXGlSeLWzIiz6e46//3pPws+qA!NG1YKjq5o/kSGykgXvngsK1n1RLJez7ZfvqV1WlLAhfMhsPV5xkv2vu0gvc/Avioz0luTtZN9x7u!DAw=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 9005
 by: olcott - Thu, 26 Aug 2021 00:26 UTC

On 8/25/2021 7:15 PM, Richard Damon wrote:
> On 8/25/21 10:15 AM, olcott wrote:
>> On 8/25/2021 7:19 AM, Richard Damon wrote:
>>> On 8/24/21 11:53 PM, olcott wrote:
>>>> On 8/24/2021 7:35 PM, Ben Bacarisse wrote:
>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>
>>>>>> On 8/24/2021 9:09 AM, Ben Bacarisse wrote:
>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>
>>>>>>>> On 8/23/2021 10:09 PM, Ben Bacarisse wrote:
>>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>>>
>>>>>>>>>> On 8/23/2021 6:26 PM, Ben Bacarisse wrote:
>>>>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>>>>>
>>>>>>>>>>>> On 8/23/2021 2:30 PM, Ben Bacarisse wrote:
>>>>>>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>>>>>
>>>>>>>>>>>> I ignore dishonest dodges away from the point at hand.
>>>>>>>>>>> OK, let's do that:
>>>>>>>>>>>        "⟨Ĥ⟩ ⟨Ĥ⟩ is not a string that encodes a halting
>>>>>>>>>>> computation"
>>>>>>>>>>> is wrong.  You wrote that immediately after a line showing that Ĥ
>>>>>>>>>>> applied to ⟨Ĥ⟩ halts.  Everything since then has just been
>>>>>>>>>>> dodging this
>>>>>>>>>>> error.
>>>>>>>>>>>
>>>>>>>>>>>> When we define Ĵ to be exactly like Ĥ except that it has a UTM
>>>>>>>>>>>> at Ĵ.qx
>>>>>>>>>>>> instead of a simulating halt decider then we can see that Ĵ
>>>>>>>>>>>> applied to
>>>>>>>>>>>> ⟨Ĵ⟩ never halts.
>>>>>>>>>>> The details are mess, but basically, yes.  Detail errors (that
>>>>>>>>>>> would get
>>>>>>>>>>> your paper rejected out of hand) available if you ask really
>>>>>>>>>>> nicely.
>>>>>>>>>>
>>>>>>>>>> Which details do you think are incorrect?
>>>>>>>>>
>>>>>>>>> A UTM is not a decider so the hat construction can't be applied to
>>>>>>>>> it.
>>>>>>>>> And if we make a "UTM-decider" (a TM that is a pure simulator
>>>>>>>>> except
>>>>>>>>> that is accepts those computations whose simulations terminate) we
>>>>>>>>> still
>>>>>>>>> can't apply the hat construction because it won't have a rejecting
>>>>>>>>> state.  Thus your use of "exactly like Ĥ except..." is, at best,
>>>>>>>>> disingenuous.  The differences must be greater than the "except..."
>>>>>>>>> clause suggests.
>>>>>>>>
>>>>>>>> My whole purpose was to simply show what happens when the simulating
>>>>>>>> halt decide at Ĥ.qx only simulates its input.
>>>>>>> I know, but you wanted to know what details you'd got wrong.
>>>>>>>
>>>>>>
>>>>>> If my plan was to swap the simulating halt decider at Ĥ.qx with a UTM
>>>>>> and then rename this machine to Ĵ and I did swap swap the simulating
>>>>>> halt decider at Ĥ.qx with a UTM and rename this machine to Ĵ then it
>>>>>> is a God damned lie that I got anything wrong.
>>>>>
>>>>> No.  You won't get it unless you really try.
>>>>>
>>>>>>>> We can still have the same final states, except now that are
>>>>>>>> unreachable dead code.
>>>>>>> Except you show below this unreachable state being reached:
>>>>>>
>>>>>> No I do frigging not.
>>>>>
>>>>> Yes you did.  I quoted you: Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn.
>>>>>
>>>>>> The code is still there but the infinite cycle
>>>>>> from Ĵ.qx to Ĵ.q0 prevents it from ever being reached.
>>>>>
>>>>> No.  You are totally at sea.  I did my best to explain but you'd
>>>>> have to
>>>>> want to learn to make any progress.
>>>>>
>>>>>>>      Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn
>>>>>>> The TM at Ĵ.qx is your "UTM-decider" with an unreachable reject
>>>>>>> state.
>>>>>>> Do you see why I don't think you know what you are saying?
>>>>>>
>>>>>> The you imagine what I mean to say instead of examining what I
>>>>>> actually say is your mistake.
>>>>>>
>>>>>> This machine
>>>>>> Ĥ.q0 ⟨Ĥ1⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ ⊢* Ĥ.qn
>>>>>>
>>>>>> is transformed into this machine:
>>>>>> Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn // a machine stuck in
>>>>>> infinitely nested simulation
>>>>>
>>>>> You don't know what this notation means.  I don't think I can help you
>>>>> with this.
>>>>>
>>>>>>>>>>>> There is an infinite cycle from Ĵ.qx to Ĵ.q0.
>>>>>>>>>>> No, but that's just because you've never written a UTM so you
>>>>>>>>>>> don't know
>>>>>>>>>>> how such a TM would work.  Ĵ applied to ⟨Ĵ⟩ is non-halting but
>>>>>>>>>>> there
>>>>>>>>>>> will not be a cycle from Ĵ.q0 -> Ĵ.qx -> Ĵ.q0...[1]
>>>>>>>>>>>
>>>>>>>>>>>> Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn
>>>>>>>>>>>
>>>>>>>>>>> Eh?  You've just said that Ĵ applied to ⟨Ĵ⟩ is non-halting.
>>>>>>> This needs to be addressed.
>>>>>>
>>>>>> That you don't believe that there is a cycle from Ĵ.qx to Ĵ.q0 is
>>>>>> flatly wrong.
>>>>>
>>>>> No, I'm right about that.
>>>>
>>>> Try and exaplain how you are right about that.
>>>
>>> The fact that the code for J (or P) has absolutely no path to go from
>>> the state qx to the state q0 OF THE SAME EXECUTION (which is what the
>>> diagram is showing).
>>>
>>> Yes, there is a 'virtual' connection from qx of one invocation to a q0
>>> of a simulated embedded invocation, but that state is NOT the outer q0.
>>>
>>> Turing Machine P or J NEVER go back to their own q0 state.
>>>
>>> You could perhaps say we have a nesting of
>>>
>>> P0.q0 -> P0.qx -> P1.q0 -> P1.qx ...
>>>
>>> But that is a NESTING, not a LOOP.
>>>
>>> They are different.
>>
>> None-the-less we have infinitely nested simulation that would never halt
>> unless the simulating halt decider aborts its simulation of its input.
>
> You HAVE to decide what your H is doing.
>

When we define Ĵ to be exactly like Ĥ except that it has a UTM at Ĵ.qx
instead of a simulating halt decider then we can see that Ĵ applied to
⟨Ĵ⟩ never halts.

Ĵ copies its input ⟨Ĵ1⟩ to ⟨Ĵ2⟩ then simulates this input Ĵ1 with its
input ⟨Ĵ2⟩
which copies its input ⟨Ĵ2⟩ to ⟨Ĵ3⟩ then simulates this input Ĵ2 with
its input ⟨Ĵ3⟩
which copies its input ⟨Ĵ3⟩ to ⟨Ĵ4⟩ then simulates this input Ĵ3 with
its input ⟨Ĵ4⟩ ...

With the Peter Linz Ĥ we have exactly the same thing while the
simulating halt decider at Ĥ.qx remains in simulation mode.

Ĥ.q0 ⟨Ĥ1⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ ⊢* Ĥ.qy ∞
if the simulated ⟨Ĥ1⟩ applied to ⟨Ĥ2⟩ halts, and


Click here to read the complete article
Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20235&group=comp.theory#20235

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 25 Aug 2021 19:41:25 -0500
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<87czq5i9u0.fsf@bsb.me.uk> <srednU_7RdGxPr_8nZ2dnUU7-eHNnZ2d@giganews.com>
<87y28tgt3w.fsf@bsb.me.uk> <xamdnei4F5CzM7_8nZ2dnUU7-KPNnZ2d@giganews.com>
<87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com>
<87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com>
<87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com>
<_8BVI.106$GD7.95@fx23.iad>
From: NoO...@NoWhere.com (olcott)
Date: Wed, 25 Aug 2021 19:41:24 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <_8BVI.106$GD7.95@fx23.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com>
Lines: 94
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-FWgvZNELRfqkueZTPaS38bE+1UW4RzUJuD55lJ3neY9GsH6xni8vgV0cBPhQVDINVY1yuzQAJZpIhpT!vXBLbeJ4koMRWYFeQE/ESf+anBI5rHtkX6Pcn2lrNei6JliRm0v6m0EpwYHzS+FIYOFJeKPkY9J0!maU=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 5615
 by: olcott - Thu, 26 Aug 2021 00:41 UTC

On 8/25/2021 7:22 PM, Richard Damon wrote:
> On 8/25/21 1:11 PM, olcott wrote:
>> On 8/25/2021 10:19 AM, Ben Bacarisse wrote:
>>> olcott <NoOne@NoWhere.com> writes:
>>>
>>>> On 8/24/2021 7:35 PM, Ben Bacarisse wrote:
>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>
>>>>>> On 8/24/2021 9:09 AM, Ben Bacarisse wrote:
>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>
>>>>>>>> On 8/23/2021 10:09 PM, Ben Bacarisse wrote:
>>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>>>
>>>>>>>>>> On 8/23/2021 6:26 PM, Ben Bacarisse wrote:
>>>>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>
>>>>>>>>>>>> There is an infinite cycle from Ĵ.qx to Ĵ.q0.
>>>>>>>>>>>
>>>>>>>>>>> No, but that's just because you've never written a UTM so you
>>>>>>>>>>> don't know
>>>>>>>>>>> how such a TM would work.  Ĵ applied to ⟨Ĵ⟩ is non-halting but
>>>>>>>>>>> there
>>>>>>>>>>> will not be a cycle from Ĵ.q0 -> Ĵ.qx -> Ĵ.q0...[1]
>>>>>>>>>>>
>>>>>>>>>>>> Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn
>>>>>>>>>>>
>>>>>>>>>>> Eh?  You've just said that Ĵ applied to ⟨Ĵ⟩ is non-halting.
>>>>>>>
>>>>>>> This needs to be addressed.
>>>>>>
>>>>>> That you don't believe that there is a cycle from Ĵ.qx to Ĵ.q0 is
>>>>>> flatly wrong.
>>>>>
>>>>> No, I'm right about that.
>>>>
>>>> Try and exaplain how you are right about that.
>>>
>>> It follows directly from the "hat" construction.  The TM "at" Ĵ.qx is
>>> (in effect) J.  None of entries in J's state transition function can
>>> refer to state Ĵ.q0 because that is a new stated added (along with a few
>>> others) with the sole purpose of doing the copy of the input.  There is
>>> simply no path from Ĵ.qx to Ĵ.q0.
>>>
>>
>> There is a path from Ĵ.qx to the Ĵ.q0 of another instance.
>> infinitely nested simulation with copying is a little less like infinite
>> recursion than infinitely nested simulation without copying,
>> none-the-less it is still obviously infinite.
>
> Except that notation is of a SINGLE instance.
>
>>
>>> And, similarly, since J is a UTM with only an accepting state (qy) the
>>> line you keep writing
>>>
>>>    Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn
>>>
>>> is bogus.
>>
>> Like I said before it is not bogus. A machine can possibly be defined
>> with unreachable states. When Ĥ is converted to Ĵ by a single change to
>> Ĥ this new Ĵ has unreachable states.
>>
>> I wanted to make a single change to Ĥ to derive Ĵ to make the single
>> point that Ĥ never stops running unless its aborts the simulation of its
>> input at Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ thus conclusively proving that this input never
>> halts according to this criteria:
>>
>> Simulating Halt Decider Theorem (Olcott 2020):
>> A simulating halt decider correctly decides that any input that never
>> halts unless the simulating halt decider aborts its simulation of this
>> input is an input that never halts.
>>
>
>
> A FALSE Theorem.
>
>> Although I call it a theorem it is actually a little stronger than that
>> because it is self-evidently true.
>
> Nope. It VIOLATES the definition of Halting.

It correctly decides conventional halting and conventional never halting
inputs on the basis of the definition of a UTM.

Do you understand this much or should I give up on you too?

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ conversation has ended? ]

<f0CVI.4087$rl3.2008@fx45.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20236&group=comp.theory#20236

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.dns-netz.com!news.freedyn.net!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!news-out.netnews.com!news.alt.net!fdc3.netnews.com!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx45.iad.POSTED!not-for-mail
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ conversation has ended? ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<xamdnei4F5CzM7_8nZ2dnUU7-KPNnZ2d@giganews.com> <87h7fhgpjm.fsf@bsb.me.uk>
<cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com> <87o89pf5zi.fsf@bsb.me.uk>
<R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com> <87k0kce1yk.fsf@bsb.me.uk>
<edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com> <87bl5oc62l.fsf@bsb.me.uk>
<INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com> <87tujfbv4y.fsf@bsb.me.uk>
<5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com> <87lf4rbksk.fsf@bsb.me.uk>
<Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com> <87fsuzaq8t.fsf@bsb.me.uk>
<__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com> <87zgt69xah.fsf@bsb.me.uk>
<tqadndv0qJ8vOLj8nZ2dnUU7-R_NnZ2d@giganews.com>
<1LCdnZZtHK3SK7j8nZ2dnUU7-R_NnZ2d@giganews.com> <87lf4pa56n.fsf@bsb.me.uk>
<feudnRmpetF2G7v8nZ2dnUU7-VfNnZ2d@giganews.com> <87czq19wx0.fsf@bsb.me.uk>
<Y7adnS3RyacCCbv8nZ2dnUU7-UWdnZ2d@giganews.com> <p_AVI.9$tG6.3@fx39.iad>
<4fqdnePjhJAvQ7v8nZ2dnUU7-e3NnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <4fqdnePjhJAvQ7v8nZ2dnUU7-e3NnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Lines: 119
Message-ID: <f0CVI.4087$rl3.2008@fx45.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Wed, 25 Aug 2021 21:21:14 -0400
X-Received-Bytes: 6817
 by: Richard Damon - Thu, 26 Aug 2021 01:21 UTC

On 8/25/21 8:22 PM, olcott wrote:
> On 8/25/2021 7:11 PM, Richard Damon wrote:
>> On 8/25/21 3:06 PM, olcott wrote:
>>> On 8/25/2021 1:55 PM, Ben Bacarisse wrote:
>>>> olcott <NoOne@NoWhere.com> writes:
>>>>
>>>>> On 8/25/2021 10:56 AM, Ben Bacarisse wrote:
>>>>
>>>>>> The halting problem is about the existence of a TM that accept those
>>>>>> string pairs (and only those string pairs) that encode halting
>>>>>> computations.  All other strings are to be rejected.  The halting
>>>>>> theorem states that no TM is a such a decider -- every TM fails to
>>>>>> correctly classify at least one string pair.
>>>>>>
>>>>>> You claim to have a TM, unfortunately called H, which is a halt
>>>>>> decider.
>>>>>> (Yes, you sometimes deny it is a general halt decider but you keep
>>>>>> quoting me saying your algorithm is one, so I presume you agree
>>>>>> that it
>>>>>> must be one.)
>>>>
>>>> So you are indeed claiming to have a general halt decider!  That's a
>>>> grand boast!  (You need to say "no" if you don't want this to be taken
>>>> as your real position.)
>>>>
>>>>>> You tell us, again and again, that the computation of Ĥ applied to
>>>>>> the
>>>>>> encoding of Ĥ (written ⟨Ĥ⟩) is a halting computation.  You are
>>>>>> quick to
>>>>>> jump in and say that it "only halts because... reason", but it's a
>>>>>> halting computation whatever the reason.
>>>>>>    That halting computation is encoded as the string pair ⟨Ĥ⟩
>>>>>> ⟨Ĥ⟩.  (I
>>>>>> prefer a notation that makes the pairing of an encoded TM and some
>>>>>> input
>>>>>> explicit, but that boat sailed years ago.)
>>>>>>    You also tell is that H rejects the string pair ⟨Ĥ⟩ ⟨Ĥ⟩.  I.e. you
>>>>>> tell
>>>>>> us everything we need to know to be sure that H is wrong about at
>>>>>> least
>>>>>> this one halting problem instance.
>>>>>
>>>>> Ĥ.q0 ⟨Ĥ1⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ ⊢* Ĥ.qn
>>>>>
>>>>> Until you understand that the input to Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ is not a halting
>>>>> computation there is no sense continuing this one way dialogue.
>>>>
>>>> Until you understand that ⟨Ĥ1⟩ ⟨Ĥ2⟩ equals ⟨Ĥ⟩ ⟨Ĥ⟩ and that ⟨Ĥ⟩ ⟨Ĥ⟩
>>>> is a
>>>> string that should be accepted you are just blowing smoke.
>>>>
>>>
>>> (a) While the simulating halt decider at Ĥ.qx remains in pure simulation
>>> mode its input ⟨Ĥ1⟩ ⟨Ĥ2⟩ never halts.
>>
>> Because H happens to stop the simulation too soon.
>>
>
> Ĵ.q0 ⟨Ĥ1⟩ ⊢* Ĵ.qx ⟨Ĵ1⟩ ⟨Ĵ2⟩ ...
>
> You are pretty intelligent to be able to catch the subtle nuance of how
> Ĵ applied to ⟨Ĵ⟩ is not exactly a cycle from Ĵ.qx to Ĵ.q0 because these
> are two different instances.
>
> That is why it seems to me that you could only be playing head games
> when you fail to acknowledge that Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ specifies infinitely
> nested simulation that never stops unless the simulating halt decider at
> Ĥ.qx aborts its simulation.

You keep using that phrase, which doesn't really mean what you think it
does. 'unless' isn't really applicable here, it REALLY generates some
distinct cases.

H DOESN'T abort the simulation, in which case Hn(<Hn^>,<Hn^>) never
returns an answer, so Hn isn't a correct halt decider because it didn't
decide the case.

H DOES abort the simulation, and return Non-Halting, in which case your
logic fails as you assume in your simulation that your Ha won't abort
it's simulation, and thus you used UNSOUND logic. It is also easy to
prove by just running it or using a REAL UTM, that Ha^(<Ha^>) is a
Halting computation, thus Ha is also WRONG.

The last possibility is that H just isn't a computation, and thus it
fails to be a computation equivalent of the H of the proof, so nothing
after that means anything.

Remember, to even START the claim of having a decider that refutes these
proofs, your H must be algorithmically defined so as to be a real
Computation per the definion of Computation Theory. It seems that your H
doesn't meet that requrement, as you keep on trying to make proofs based
on trying different ones. This is really just like the proof that you
are trying to disprove, and the fact that your H gets the wrong answer
just reinforces those proofs.

>
>
>> Put that exact same input into a compatible UTM, and it will run to a
>> Halt.
>>
>> THEREFORE, H WAS WRONG to abort the simulation and declair non-halting.
>>
>>
>>>
>>> (b) Every computation that never halts while its simulating halt decider
>>> remains in pure simulation mode is a computation that never halts.
>>
>> FALSE STATEMENT. PERIOD>
>>
>>
>>>
>>> Too disingenuous to continue. You utterly refuse to directly examine my
>>> proof provided immediately above that is not the sign of an honest
>>> dialogue.
>>>
>>
>
>

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<i7CVI.13$jl2.7@fx34.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20237&group=comp.theory#20237

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!newsreader4.netcologne.de!news.netcologne.de!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx34.iad.POSTED!not-for-mail
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<87czq5i9u0.fsf@bsb.me.uk> <srednU_7RdGxPr_8nZ2dnUU7-eHNnZ2d@giganews.com>
<87y28tgt3w.fsf@bsb.me.uk> <xamdnei4F5CzM7_8nZ2dnUU7-KPNnZ2d@giganews.com>
<87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com>
<87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com>
<87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com>
<_8BVI.106$GD7.95@fx23.iad> <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Lines: 109
Message-ID: <i7CVI.13$jl2.7@fx34.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Wed, 25 Aug 2021 21:28:44 -0400
X-Received-Bytes: 6168
 by: Richard Damon - Thu, 26 Aug 2021 01:28 UTC

On 8/25/21 8:41 PM, olcott wrote:
> On 8/25/2021 7:22 PM, Richard Damon wrote:
>> On 8/25/21 1:11 PM, olcott wrote:
>>> On 8/25/2021 10:19 AM, Ben Bacarisse wrote:
>>>> olcott <NoOne@NoWhere.com> writes:
>>>>
>>>>> On 8/24/2021 7:35 PM, Ben Bacarisse wrote:
>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>
>>>>>>> On 8/24/2021 9:09 AM, Ben Bacarisse wrote:
>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>>
>>>>>>>>> On 8/23/2021 10:09 PM, Ben Bacarisse wrote:
>>>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>>>>
>>>>>>>>>>> On 8/23/2021 6:26 PM, Ben Bacarisse wrote:
>>>>>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>
>>>>>>>>>>>>> There is an infinite cycle from Ĵ.qx to Ĵ.q0.
>>>>>>>>>>>>
>>>>>>>>>>>> No, but that's just because you've never written a UTM so you
>>>>>>>>>>>> don't know
>>>>>>>>>>>> how such a TM would work.  Ĵ applied to ⟨Ĵ⟩ is non-halting but
>>>>>>>>>>>> there
>>>>>>>>>>>> will not be a cycle from Ĵ.q0 -> Ĵ.qx -> Ĵ.q0...[1]
>>>>>>>>>>>>
>>>>>>>>>>>>> Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn
>>>>>>>>>>>>
>>>>>>>>>>>> Eh?  You've just said that Ĵ applied to ⟨Ĵ⟩ is non-halting.
>>>>>>>>
>>>>>>>> This needs to be addressed.
>>>>>>>
>>>>>>> That you don't believe that there is a cycle from Ĵ.qx to Ĵ.q0 is
>>>>>>> flatly wrong.
>>>>>>
>>>>>> No, I'm right about that.
>>>>>
>>>>> Try and exaplain how you are right about that.
>>>>
>>>> It follows directly from the "hat" construction.  The TM "at" Ĵ.qx is
>>>> (in effect) J.  None of entries in J's state transition function can
>>>> refer to state Ĵ.q0 because that is a new stated added (along with a
>>>> few
>>>> others) with the sole purpose of doing the copy of the input.  There is
>>>> simply no path from Ĵ.qx to Ĵ.q0.
>>>>
>>>
>>> There is a path from Ĵ.qx to the Ĵ.q0 of another instance.
>>> infinitely nested simulation with copying is a little less like infinite
>>> recursion than infinitely nested simulation without copying,
>>> none-the-less it is still obviously infinite.
>>
>> Except that notation is of a SINGLE instance.
>>
>>>
>>>> And, similarly, since J is a UTM with only an accepting state (qy) the
>>>> line you keep writing
>>>>
>>>>     Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn
>>>>
>>>> is bogus.
>>>
>>> Like I said before it is not bogus. A machine can possibly be defined
>>> with unreachable states. When Ĥ is converted to Ĵ by a single change to
>>> Ĥ this new Ĵ has unreachable states.
>>>
>>> I wanted to make a single change to Ĥ to derive Ĵ to make the single
>>> point that Ĥ never stops running unless its aborts the simulation of its
>>> input at Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ thus conclusively proving that this input never
>>> halts according to this criteria:
>>>
>>> Simulating Halt Decider Theorem (Olcott 2020):
>>> A simulating halt decider correctly decides that any input that never
>>> halts unless the simulating halt decider aborts its simulation of this
>>> input is an input that never halts.
>>>
>>
>>
>> A FALSE Theorem.
>>
>>> Although I call it a theorem it is actually a little stronger than that
>>> because it is self-evidently true.
>>
>> Nope. It VIOLATES the definition of Halting.
>
> It correctly decides conventional halting and conventional never halting
> inputs on the basis of the definition of a UTM.
>
> Do you understand this much or should I give up on you too?
>
>
No, becuase UTM(<H^>, <H^>) Halts, thus showing that since H(<H^>,<H^>)
says non-halting it was wrong.

Remember, your 'acts like a UTM until it decides and the it aborts it
simulation' means that H is NOT a UTM.

If you act like a student until your complete your course of study, then
you are a Graduate.
If you act like a student until you give up, you are not, you are just a
drop-out.

If a simulator completes its work when its simulation reaches a halting
state, then it is a UTM,
A simulator that stops earlier isn't a UTM, it is just a drop-out.

In that later context 'Pure' isn't really an applicable adjective, as it
is an absolute qualifier. That is like calling someone who is currently
living as being 'like an immortal'. It just isn't true.

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ conversation has ended? ]

<5Y6dndlJqqh4c7v8nZ2dnUU7-RXNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20238&group=comp.theory#20238

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!feeder1.feed.usenet.farm!feed.usenet.farm!tr1.eu1.usenetexpress.com!feeder.usenetexpress.com!tr1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 25 Aug 2021 20:31:17 -0500
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ conversation has ended? ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com> <87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com> <87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com> <87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com> <87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com> <87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com> <87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com> <87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com> <87zgt69xah.fsf@bsb.me.uk> <tqadndv0qJ8vOLj8nZ2dnUU7-R_NnZ2d@giganews.com> <1LCdnZZtHK3SK7j8nZ2dnUU7-R_NnZ2d@giganews.com> <87lf4pa56n.fsf@bsb.me.uk> <feudnRmpetF2G7v8nZ2dnUU7-VfNnZ2d@giganews.com> <87czq19wx0.fsf@bsb.me.uk> <Y7adnS3RyacCCbv8nZ2dnUU7-UWdnZ2d@giganews.com> <p_AVI.9$tG6.3@fx39.iad> <4fqdnePjhJAvQ7v8nZ2dnUU7-e3NnZ2d@giganews.com> <f0CVI.4087$rl3.2008@fx45.iad>
From: NoO...@NoWhere.com (olcott)
Date: Wed, 25 Aug 2021 20:31:16 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <f0CVI.4087$rl3.2008@fx45.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <5Y6dndlJqqh4c7v8nZ2dnUU7-RXNnZ2d@giganews.com>
Lines: 90
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-pruvPsv5losrHrZTODRIhVGT6+uhvI30Uxj/geO2ib0fORJBtb78QzRlmgMrNiiDQAx8s3WDZqjXqvi!Znbwzu4D4wRaVn+2As+bkl3iQ4gleOhoKnSrtMWYpf1skZsr9e7WLt8+Ct+LunQn7AWT8PArulp3!GWs=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 6073
 by: olcott - Thu, 26 Aug 2021 01:31 UTC

On 8/25/2021 8:21 PM, Richard Damon wrote:
> On 8/25/21 8:22 PM, olcott wrote:
>> On 8/25/2021 7:11 PM, Richard Damon wrote:
>>> On 8/25/21 3:06 PM, olcott wrote:
>>>> On 8/25/2021 1:55 PM, Ben Bacarisse wrote:
>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>
>>>>>> On 8/25/2021 10:56 AM, Ben Bacarisse wrote:
>>>>>
>>>>>>> The halting problem is about the existence of a TM that accept those
>>>>>>> string pairs (and only those string pairs) that encode halting
>>>>>>> computations.  All other strings are to be rejected.  The halting
>>>>>>> theorem states that no TM is a such a decider -- every TM fails to
>>>>>>> correctly classify at least one string pair.
>>>>>>>
>>>>>>> You claim to have a TM, unfortunately called H, which is a halt
>>>>>>> decider.
>>>>>>> (Yes, you sometimes deny it is a general halt decider but you keep
>>>>>>> quoting me saying your algorithm is one, so I presume you agree
>>>>>>> that it
>>>>>>> must be one.)
>>>>>
>>>>> So you are indeed claiming to have a general halt decider!  That's a
>>>>> grand boast!  (You need to say "no" if you don't want this to be taken
>>>>> as your real position.)
>>>>>
>>>>>>> You tell us, again and again, that the computation of Ĥ applied to
>>>>>>> the
>>>>>>> encoding of Ĥ (written ⟨Ĥ⟩) is a halting computation.  You are
>>>>>>> quick to
>>>>>>> jump in and say that it "only halts because... reason", but it's a
>>>>>>> halting computation whatever the reason.
>>>>>>>    That halting computation is encoded as the string pair ⟨Ĥ⟩
>>>>>>> ⟨Ĥ⟩.  (I
>>>>>>> prefer a notation that makes the pairing of an encoded TM and some
>>>>>>> input
>>>>>>> explicit, but that boat sailed years ago.)
>>>>>>>    You also tell is that H rejects the string pair ⟨Ĥ⟩ ⟨Ĥ⟩.  I.e. you
>>>>>>> tell
>>>>>>> us everything we need to know to be sure that H is wrong about at
>>>>>>> least
>>>>>>> this one halting problem instance.
>>>>>>
>>>>>> Ĥ.q0 ⟨Ĥ1⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ ⊢* Ĥ.qn
>>>>>>
>>>>>> Until you understand that the input to Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ is not a halting
>>>>>> computation there is no sense continuing this one way dialogue.
>>>>>
>>>>> Until you understand that ⟨Ĥ1⟩ ⟨Ĥ2⟩ equals ⟨Ĥ⟩ ⟨Ĥ⟩ and that ⟨Ĥ⟩ ⟨Ĥ⟩
>>>>> is a
>>>>> string that should be accepted you are just blowing smoke.
>>>>>
>>>>
>>>> (a) While the simulating halt decider at Ĥ.qx remains in pure simulation
>>>> mode its input ⟨Ĥ1⟩ ⟨Ĥ2⟩ never halts.
>>>
>>> Because H happens to stop the simulation too soon.
>>>
>>
>> Ĵ.q0 ⟨Ĥ1⟩ ⊢* Ĵ.qx ⟨Ĵ1⟩ ⟨Ĵ2⟩ ...
>>
>> You are pretty intelligent to be able to catch the subtle nuance of how
>> Ĵ applied to ⟨Ĵ⟩ is not exactly a cycle from Ĵ.qx to Ĵ.q0 because these
>> are two different instances.
>>
>> That is why it seems to me that you could only be playing head games
>> when you fail to acknowledge that Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ specifies infinitely
>> nested simulation that never stops unless the simulating halt decider at
>> Ĥ.qx aborts its simulation.
>
> You keep using that phrase, which doesn't really mean what you think it
> does. 'unless' isn't really applicable here, it REALLY generates some
> distinct cases.
This is what I really think that you are playing head games.

It is not that hard to imagine distinct cases:
(1) Ĥ.q0 ⟨Ĥ1⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩... never aborts the simulation of its
input.

(2) Ĥ.q0 ⟨Ĥ1⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩... aborts the simulation of its input at
some point.

You go around and around and around as if the difference between the two
cases is unfathomably difficult to comprehend.

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20239&group=comp.theory#20239

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!feeder1.feed.usenet.farm!feed.usenet.farm!tr3.eu1.usenetexpress.com!feeder.usenetexpress.com!tr2.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 25 Aug 2021 20:34:19 -0500
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com> <87czq5i9u0.fsf@bsb.me.uk> <srednU_7RdGxPr_8nZ2dnUU7-eHNnZ2d@giganews.com> <87y28tgt3w.fsf@bsb.me.uk> <xamdnei4F5CzM7_8nZ2dnUU7-KPNnZ2d@giganews.com> <87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com> <87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com> <87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com> <87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com> <87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com> <87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com> <87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com> <87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com> <87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com> <_8BVI.106$GD7.95@fx23.iad> <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com> <i7CVI.13$jl2.7@fx34.iad>
From: NoO...@NoWhere.com (olcott)
Date: Wed, 25 Aug 2021 20:34:18 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <i7CVI.13$jl2.7@fx34.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID: <5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com>
Lines: 122
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-3LMyD+MkvqeG1friYb72+8xQd44ZCfw/Oqjq/0Ets6HagMHQxjLYxQyGzeCG2mKUmzfGcy7EcXVIT1y!dIJtgQUA5NbS44Mpc2DfTwoJakiJuvle5pmXAJUVZ5K7FHJJvEGVlHuf72TNiC9D7Nj/3HDs71JK!oFo=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 6808
 by: olcott - Thu, 26 Aug 2021 01:34 UTC

On 8/25/2021 8:28 PM, Richard Damon wrote:
> On 8/25/21 8:41 PM, olcott wrote:
>> On 8/25/2021 7:22 PM, Richard Damon wrote:
>>> On 8/25/21 1:11 PM, olcott wrote:
>>>> On 8/25/2021 10:19 AM, Ben Bacarisse wrote:
>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>
>>>>>> On 8/24/2021 7:35 PM, Ben Bacarisse wrote:
>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>
>>>>>>>> On 8/24/2021 9:09 AM, Ben Bacarisse wrote:
>>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>>>
>>>>>>>>>> On 8/23/2021 10:09 PM, Ben Bacarisse wrote:
>>>>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>>>>>>
>>>>>>>>>>>> On 8/23/2021 6:26 PM, Ben Bacarisse wrote:
>>>>>>>>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>
>>>>>>>>>>>>>> There is an infinite cycle from Ĵ.qx to Ĵ.q0.
>>>>>>>>>>>>>
>>>>>>>>>>>>> No, but that's just because you've never written a UTM so you
>>>>>>>>>>>>> don't know
>>>>>>>>>>>>> how such a TM would work.  Ĵ applied to ⟨Ĵ⟩ is non-halting but
>>>>>>>>>>>>> there
>>>>>>>>>>>>> will not be a cycle from Ĵ.q0 -> Ĵ.qx -> Ĵ.q0...[1]
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn
>>>>>>>>>>>>>
>>>>>>>>>>>>> Eh?  You've just said that Ĵ applied to ⟨Ĵ⟩ is non-halting.
>>>>>>>>>
>>>>>>>>> This needs to be addressed.
>>>>>>>>
>>>>>>>> That you don't believe that there is a cycle from Ĵ.qx to Ĵ.q0 is
>>>>>>>> flatly wrong.
>>>>>>>
>>>>>>> No, I'm right about that.
>>>>>>
>>>>>> Try and exaplain how you are right about that.
>>>>>
>>>>> It follows directly from the "hat" construction.  The TM "at" Ĵ.qx is
>>>>> (in effect) J.  None of entries in J's state transition function can
>>>>> refer to state Ĵ.q0 because that is a new stated added (along with a
>>>>> few
>>>>> others) with the sole purpose of doing the copy of the input.  There is
>>>>> simply no path from Ĵ.qx to Ĵ.q0.
>>>>>
>>>>
>>>> There is a path from Ĵ.qx to the Ĵ.q0 of another instance.
>>>> infinitely nested simulation with copying is a little less like infinite
>>>> recursion than infinitely nested simulation without copying,
>>>> none-the-less it is still obviously infinite.
>>>
>>> Except that notation is of a SINGLE instance.
>>>
>>>>
>>>>> And, similarly, since J is a UTM with only an accepting state (qy) the
>>>>> line you keep writing
>>>>>
>>>>>     Ĵ.q0 ⟨Ĵ⟩ ⊢* Ĵ.qx ⟨Ĵ⟩ ⟨Ĵ⟩ ⊢* Ĵ.qn
>>>>>
>>>>> is bogus.
>>>>
>>>> Like I said before it is not bogus. A machine can possibly be defined
>>>> with unreachable states. When Ĥ is converted to Ĵ by a single change to
>>>> Ĥ this new Ĵ has unreachable states.
>>>>
>>>> I wanted to make a single change to Ĥ to derive Ĵ to make the single
>>>> point that Ĥ never stops running unless its aborts the simulation of its
>>>> input at Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ thus conclusively proving that this input never
>>>> halts according to this criteria:
>>>>
>>>> Simulating Halt Decider Theorem (Olcott 2020):
>>>> A simulating halt decider correctly decides that any input that never
>>>> halts unless the simulating halt decider aborts its simulation of this
>>>> input is an input that never halts.
>>>>
>>>
>>>
>>> A FALSE Theorem.
>>>
>>>> Although I call it a theorem it is actually a little stronger than that
>>>> because it is self-evidently true.
>>>
>>> Nope. It VIOLATES the definition of Halting.
>>
>> It correctly decides conventional halting and conventional never halting
>> inputs on the basis of the definition of a UTM.
>>
>> Do you understand this much or should I give up on you too?
>>
>>
> No, becuase UTM(<H^>, <H^>) Halts, thus showing that since H(<H^>,<H^>)
> says non-halting it was wrong.

That was your last chance.

>
> Remember, your 'acts like a UTM until it decides and the it aborts it
> simulation' means that H is NOT a UTM.
>
> If you act like a student until your complete your course of study, then
> you are a Graduate.
> If you act like a student until you give up, you are not, you are just a
> drop-out.
>
> If a simulator completes its work when its simulation reaches a halting
> state, then it is a UTM,
> A simulator that stops earlier isn't a UTM, it is just a drop-out.
>
> In that later context 'Pure' isn't really an applicable adjective, as it
> is an absolute qualifier. That is like calling someone who is currently
> living as being 'like an immortal'. It just isn't true.
>

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ conversation has ended? ]

<RdCVI.185$2B4.17@fx04.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20240&group=comp.theory#20240

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!newsreader4.netcologne.de!news.netcologne.de!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx04.iad.POSTED!not-for-mail
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ conversation has ended? ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com> <87o89pf5zi.fsf@bsb.me.uk>
<R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com> <87k0kce1yk.fsf@bsb.me.uk>
<edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com> <87bl5oc62l.fsf@bsb.me.uk>
<INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com> <87tujfbv4y.fsf@bsb.me.uk>
<5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com> <87lf4rbksk.fsf@bsb.me.uk>
<Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com> <87fsuzaq8t.fsf@bsb.me.uk>
<__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com> <87zgt69xah.fsf@bsb.me.uk>
<tqadndv0qJ8vOLj8nZ2dnUU7-R_NnZ2d@giganews.com>
<1LCdnZZtHK3SK7j8nZ2dnUU7-R_NnZ2d@giganews.com> <87lf4pa56n.fsf@bsb.me.uk>
<feudnRmpetF2G7v8nZ2dnUU7-VfNnZ2d@giganews.com> <87czq19wx0.fsf@bsb.me.uk>
<Y7adnS3RyacCCbv8nZ2dnUU7-UWdnZ2d@giganews.com> <p_AVI.9$tG6.3@fx39.iad>
<4fqdnePjhJAvQ7v8nZ2dnUU7-e3NnZ2d@giganews.com>
<f0CVI.4087$rl3.2008@fx45.iad>
<5Y6dndlJqqh4c7v8nZ2dnUU7-RXNnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <5Y6dndlJqqh4c7v8nZ2dnUU7-RXNnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Lines: 106
Message-ID: <RdCVI.185$2B4.17@fx04.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Wed, 25 Aug 2021 21:35:44 -0400
X-Received-Bytes: 6349
 by: Richard Damon - Thu, 26 Aug 2021 01:35 UTC

On 8/25/21 9:31 PM, olcott wrote:
> On 8/25/2021 8:21 PM, Richard Damon wrote:
>> On 8/25/21 8:22 PM, olcott wrote:
>>> On 8/25/2021 7:11 PM, Richard Damon wrote:
>>>> On 8/25/21 3:06 PM, olcott wrote:
>>>>> On 8/25/2021 1:55 PM, Ben Bacarisse wrote:
>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>
>>>>>>> On 8/25/2021 10:56 AM, Ben Bacarisse wrote:
>>>>>>
>>>>>>>> The halting problem is about the existence of a TM that accept
>>>>>>>> those
>>>>>>>> string pairs (and only those string pairs) that encode halting
>>>>>>>> computations.  All other strings are to be rejected.  The halting
>>>>>>>> theorem states that no TM is a such a decider -- every TM fails to
>>>>>>>> correctly classify at least one string pair.
>>>>>>>>
>>>>>>>> You claim to have a TM, unfortunately called H, which is a halt
>>>>>>>> decider.
>>>>>>>> (Yes, you sometimes deny it is a general halt decider but you keep
>>>>>>>> quoting me saying your algorithm is one, so I presume you agree
>>>>>>>> that it
>>>>>>>> must be one.)
>>>>>>
>>>>>> So you are indeed claiming to have a general halt decider!  That's a
>>>>>> grand boast!  (You need to say "no" if you don't want this to be
>>>>>> taken
>>>>>> as your real position.)
>>>>>>
>>>>>>>> You tell us, again and again, that the computation of Ĥ applied to
>>>>>>>> the
>>>>>>>> encoding of Ĥ (written ⟨Ĥ⟩) is a halting computation.  You are
>>>>>>>> quick to
>>>>>>>> jump in and say that it "only halts because... reason", but it's a
>>>>>>>> halting computation whatever the reason.
>>>>>>>>     That halting computation is encoded as the string pair ⟨Ĥ⟩
>>>>>>>> ⟨Ĥ⟩.  (I
>>>>>>>> prefer a notation that makes the pairing of an encoded TM and some
>>>>>>>> input
>>>>>>>> explicit, but that boat sailed years ago.)
>>>>>>>>     You also tell is that H rejects the string pair ⟨Ĥ⟩ ⟨Ĥ⟩. 
>>>>>>>> I.e. you
>>>>>>>> tell
>>>>>>>> us everything we need to know to be sure that H is wrong about at
>>>>>>>> least
>>>>>>>> this one halting problem instance.
>>>>>>>
>>>>>>> Ĥ.q0 ⟨Ĥ1⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ ⊢* Ĥ.qn
>>>>>>>
>>>>>>> Until you understand that the input to Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ is not a
>>>>>>> halting
>>>>>>> computation there is no sense continuing this one way dialogue.
>>>>>>
>>>>>> Until you understand that ⟨Ĥ1⟩ ⟨Ĥ2⟩ equals ⟨Ĥ⟩ ⟨Ĥ⟩ and that ⟨Ĥ⟩ ⟨Ĥ⟩
>>>>>> is a
>>>>>> string that should be accepted you are just blowing smoke.
>>>>>>
>>>>>
>>>>> (a) While the simulating halt decider at Ĥ.qx remains in pure
>>>>> simulation
>>>>> mode its input ⟨Ĥ1⟩ ⟨Ĥ2⟩ never halts.
>>>>
>>>> Because H happens to stop the simulation too soon.
>>>>
>>>
>>> Ĵ.q0 ⟨Ĥ1⟩ ⊢* Ĵ.qx ⟨Ĵ1⟩ ⟨Ĵ2⟩ ...
>>>
>>> You are pretty intelligent to be able to catch the subtle nuance of how
>>> Ĵ applied to ⟨Ĵ⟩ is not exactly a cycle from Ĵ.qx to Ĵ.q0 because these
>>> are two different instances.
>>>
>>> That is why it seems to me that you could only be playing head games
>>> when you fail to acknowledge that Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ specifies infinitely
>>> nested simulation that never stops unless the simulating halt decider at
>>> Ĥ.qx aborts its simulation.
>>
>> You keep using that phrase, which doesn't really mean what you think it
>> does. 'unless' isn't really applicable here, it REALLY generates some
>> distinct cases.
> This is what I really think that you are playing head games.
>
> It is not that hard to imagine distinct cases:

Right, and they are DISTINCT.

> (1) Ĥ.q0 ⟨Ĥ1⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩... never aborts the simulation of its
> input.
>
> (2) Ĥ.q0 ⟨Ĥ1⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩... aborts the simulation of its input at
> some point.
>
> You go around and around and around as if the difference between the two
> cases is unfathomably difficult to comprehend.
>

(1) never answers Hn(Hn^,Hn^) so is wrong
(2) Ha^(Ha^) does halt, so Ha(Ha^,Ha^) saying not halting is wrong.

Since we have DIFFERENT H^s in the two distinct cases, you can't use
your 'proof' from case (1) to try to prove that H^ in case (2) is
non-halting.

THAT is your fundamental error.

Remember, H^ includes within its algorithm, a copy of the algorithm of
H, so changing H changes H^. You keep on trying to ignore that FACT.

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<ihCVI.186$2B4.3@fx04.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20241&group=comp.theory#20241

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!news-out.netnews.com!news.alt.net!fdc3.netnews.com!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx04.iad.POSTED!not-for-mail
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<87y28tgt3w.fsf@bsb.me.uk> <xamdnei4F5CzM7_8nZ2dnUU7-KPNnZ2d@giganews.com>
<87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com>
<87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com>
<87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com>
<_8BVI.106$GD7.95@fx23.iad> <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com>
<i7CVI.13$jl2.7@fx34.iad> <5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Lines: 10
Message-ID: <ihCVI.186$2B4.3@fx04.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Wed, 25 Aug 2021 21:39:26 -0400
X-Received-Bytes: 2151
 by: Richard Damon - Thu, 26 Aug 2021 01:39 UTC

On 8/25/21 9:34 PM, olcott wrote:
> On 8/25/2021 8:28 PM, Richard Damon wrote:

>> No, becuase UTM(<H^>, <H^>) Halts, thus showing that since H(<H^>,<H^>)
>> says non-halting it was wrong.
>
>
> That was your last chance.

You admit defeat?

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<CeidnS_08apsaLv8nZ2dnUU7-RmdnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20242&group=comp.theory#20242

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!rocksolid2!news.neodome.net!weretis.net!feeder8.news.weretis.net!news.uzoreto.com!tr2.eu1.usenetexpress.com!feeder.usenetexpress.com!tr1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 25 Aug 2021 21:01:21 -0500
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com> <87y28tgt3w.fsf@bsb.me.uk> <xamdnei4F5CzM7_8nZ2dnUU7-KPNnZ2d@giganews.com> <87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com> <87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com> <87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com> <87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com> <87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com> <87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com> <87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com> <87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com> <87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com> <_8BVI.106$GD7.95@fx23.iad> <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com> <i7CVI.13$jl2.7@fx34.iad> <5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com> <ihCVI.186$2B4.3@fx04.iad>
From: NoO...@NoWhere.com (olcott)
Date: Wed, 25 Aug 2021 21:01:20 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <ihCVI.186$2B4.3@fx04.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Message-ID: <CeidnS_08apsaLv8nZ2dnUU7-RmdnZ2d@giganews.com>
Lines: 21
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-0UlS0C0J2j6w2sJwSTmh8IAkBn7VNfLMm5GtVCE4PRSMtUGxLw1lkxRRVh9G3Ei2j8szFT7RxOfqMgT!aOgLoASCca3ngwE7E3H7v6uvZodVq9XbgSVBZDEza2w7lsLLKX8LXBzI6GsIUKt2qX1h/3oCT093!HWA=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 2738
 by: olcott - Thu, 26 Aug 2021 02:01 UTC

On 8/25/2021 8:39 PM, Richard Damon wrote:
> On 8/25/21 9:34 PM, olcott wrote:
>> On 8/25/2021 8:28 PM, Richard Damon wrote:
>
>>> No, becuase UTM(<H^>, <H^>) Halts, thus showing that since H(<H^>,<H^>)
>>> says non-halting it was wrong.
>>
>>
>> That was your last chance.
>
> You admit defeat?
>

I acknowledge that you are an incorrigible jackass.
The review process moves to phase two.

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<sg6ss9$o8n$1@dont-email.me>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20243&group=comp.theory#20243

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: news.x.r...@xoxy.net (Richard Damon)
Newsgroups: comp.theory
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ distinct computations ]
Date: Wed, 25 Aug 2021 22:04:56 -0400
Organization: A noiseless patient Spider
Lines: 26
Message-ID: <sg6ss9$o8n$1@dont-email.me>
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com>
<87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com>
<87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com>
<_8BVI.106$GD7.95@fx23.iad> <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com>
<i7CVI.13$jl2.7@fx34.iad> <5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com>
<ihCVI.186$2B4.3@fx04.iad> <CeidnS_08apsaLv8nZ2dnUU7-RmdnZ2d@giganews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 26 Aug 2021 02:04:57 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="5af249c5cd4a147c1d09324a1f9de765";
logging-data="24855"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18MO2SaNBriBjl988dsd63D3bq6f5pJXZw="
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.13.0
Cancel-Lock: sha1:kMsyiiUGfzucXro5BrNV5LdJtAA=
In-Reply-To: <CeidnS_08apsaLv8nZ2dnUU7-RmdnZ2d@giganews.com>
Content-Language: en-US
 by: Richard Damon - Thu, 26 Aug 2021 02:04 UTC

On 8/25/21 10:01 PM, olcott wrote:
> On 8/25/2021 8:39 PM, Richard Damon wrote:
>> On 8/25/21 9:34 PM, olcott wrote:
>>> On 8/25/2021 8:28 PM, Richard Damon wrote:
>>
>>>> No, becuase UTM(<H^>, <H^>) Halts, thus showing that since H(<H^>,<H^>)
>>>> says non-halting it was wrong.
>>>
>>>
>>> That was your last chance.
>>
>> You admit defeat?
>>
>
> I acknowledge that you are an incorrigible jackass.
> The review process moves to phase two.
>

What does that mean? You going to write the paper to submit to get your
rejection?

You have yet to show anywhere whre my basic objections are incorrect.

Your 'theorems' have been proved to be groundless and totally unsound.

You totally don't understand what you are righting about.

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<SZ-dncSHQLR3Z7v8nZ2dnUU7-W2dnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20244&group=comp.theory#20244

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!news.swapon.de!news.uzoreto.com!tr2.eu1.usenetexpress.com!feeder.usenetexpress.com!tr3.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 25 Aug 2021 21:22:34 -0500
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com> <87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com> <87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com> <87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com> <87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com> <87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com> <87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com> <87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com> <87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com> <87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com> <_8BVI.106$GD7.95@fx23.iad> <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com> <i7CVI.13$jl2.7@fx34.iad> <5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com> <ihCVI.186$2B4.3@fx04.iad> <CeidnS_08apsaLv8nZ2dnUU7-RmdnZ2d@giganews.com> <sg6ss9$o8n$1@dont-email.me>
From: NoO...@NoWhere.com (olcott)
Date: Wed, 25 Aug 2021 21:22:33 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <sg6ss9$o8n$1@dont-email.me>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Message-ID: <SZ-dncSHQLR3Z7v8nZ2dnUU7-W2dnZ2d@giganews.com>
Lines: 38
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-1XkrUyA0K3wXrrqgVoTGIDPP55EHIoXyrDMHOVtXMXfAPAog5RsEIeBkDhQGsAYK/dxB+NSTgynEJUj!mbHA4i+Y44OkyP305DqodD5ajzqSYwMZ/8ovW8+j3SyWwIPtXa4JQfvRoziGYXSvu0WodWryAb1b!tkc=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 3241
 by: olcott - Thu, 26 Aug 2021 02:22 UTC

On 8/25/2021 9:04 PM, Richard Damon wrote:
> On 8/25/21 10:01 PM, olcott wrote:
>> On 8/25/2021 8:39 PM, Richard Damon wrote:
>>> On 8/25/21 9:34 PM, olcott wrote:
>>>> On 8/25/2021 8:28 PM, Richard Damon wrote:
>>>
>>>>> No, becuase UTM(<H^>, <H^>) Halts, thus showing that since H(<H^>,<H^>)
>>>>> says non-halting it was wrong.
>>>>
>>>>
>>>> That was your last chance.
>>>
>>> You admit defeat?
>>>
>>
>> I acknowledge that you are an incorrigible jackass.
>> The review process moves to phase two.
>>
>
> What does that mean? You going to write the paper to submit to get your
> rejection?
>
> You have yet to show anywhere whre my basic objections are incorrect.
>

You know full well that your "objections" are pure drivel.

> Your 'theorems' have been proved to be groundless and totally unsound.
>
> You totally don't understand what you are righting about.
>

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<GfGdnRdNdsTdYbv8nZ2dnUU7-KHNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20245&group=comp.theory#20245

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!tr2.eu1.usenetexpress.com!feeder.usenetexpress.com!tr2.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 25 Aug 2021 21:28:16 -0500
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com> <87y28tgt3w.fsf@bsb.me.uk> <xamdnei4F5CzM7_8nZ2dnUU7-KPNnZ2d@giganews.com> <87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com> <87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com> <87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com> <87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com> <87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com> <87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com> <87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com> <87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com> <87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com> <_8BVI.106$GD7.95@fx23.iad> <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com> <i7CVI.13$jl2.7@fx34.iad> <5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com> <ihCVI.186$2B4.3@fx04.iad>
From: NoO...@NoWhere.com (olcott)
Date: Wed, 25 Aug 2021 21:28:15 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <ihCVI.186$2B4.3@fx04.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Message-ID: <GfGdnRdNdsTdYbv8nZ2dnUU7-KHNnZ2d@giganews.com>
Lines: 21
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-JKqY4pxXLOBZQhvcIin+o6a6oShXO/EqgeCpQQTG+k+XXm+9pXS+V98eJg9/L7l0hHys3fXDOksPUSD!vovKOU3c2ihGyTtPTNkQ98fONj/PSF9qepnG09H6HFg6SyrtU5i06SarmH/DyTyIuk9B36DI7uMy!XYA=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 2759
 by: olcott - Thu, 26 Aug 2021 02:28 UTC

On 8/25/2021 8:39 PM, Richard Damon wrote:
> On 8/25/21 9:34 PM, olcott wrote:
>> On 8/25/2021 8:28 PM, Richard Damon wrote:
>
>>> No, becuase UTM(<H^>, <H^>) Halts, thus showing that since H(<H^>,<H^>)
>>> says non-halting it was wrong.
>>
>>
>> That was your last chance.
>
> You admit defeat?
>

This sort of response provides substantial additional evidence that you
never had any honest dialogue in mind.

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<VdDVI.486$lC6.43@fx41.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20246&group=comp.theory#20246

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!news-out.netnews.com!news.alt.net!fdc2.netnews.com!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx41.iad.POSTED!not-for-mail
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com>
<87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com>
<_8BVI.106$GD7.95@fx23.iad> <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com>
<i7CVI.13$jl2.7@fx34.iad> <5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com>
<ihCVI.186$2B4.3@fx04.iad> <CeidnS_08apsaLv8nZ2dnUU7-RmdnZ2d@giganews.com>
<sg6ss9$o8n$1@dont-email.me> <SZ-dncSHQLR3Z7v8nZ2dnUU7-W2dnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <SZ-dncSHQLR3Z7v8nZ2dnUU7-W2dnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Lines: 78
Message-ID: <VdDVI.486$lC6.43@fx41.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Wed, 25 Aug 2021 22:44:04 -0400
X-Received-Bytes: 4853
 by: Richard Damon - Thu, 26 Aug 2021 02:44 UTC

On 8/25/21 10:22 PM, olcott wrote:
> On 8/25/2021 9:04 PM, Richard Damon wrote:
>> On 8/25/21 10:01 PM, olcott wrote:
>>> On 8/25/2021 8:39 PM, Richard Damon wrote:
>>>> On 8/25/21 9:34 PM, olcott wrote:
>>>>> On 8/25/2021 8:28 PM, Richard Damon wrote:
>>>>
>>>>>> No, becuase UTM(<H^>, <H^>) Halts, thus showing that since
>>>>>> H(<H^>,<H^>)
>>>>>> says non-halting it was wrong.
>>>>>
>>>>>
>>>>> That was your last chance.
>>>>
>>>> You admit defeat?
>>>>
>>>
>>> I acknowledge that you are an incorrigible jackass.
>>> The review process moves to phase two.
>>>
>>
>> What does that mean? You going to write the paper to submit to get your
>> rejection?
>>
>> You have yet to show anywhere whre my basic objections are incorrect.
>>
>
> You know full well that your "objections" are pure drivel.

No, I, and everyone else who is reading this will see that what I say
makes sense.

YOUR statements are the 'pure drivel'.

Please note that basically no one belives your statements and everyone
thinks you are wrong. While it is possible that you have discovered some
hidden secret, it is very unlikely. One key thing to ask yourself, what
grounds do I have to actually expect that I could come up with some
insite like that that no one else beleives.

Then you need to ask yourself, If I am right and everyone else is wrong,
what it the path to show that. That path is NOT being argumentative.
That just solidifies the opposition. Remember, if you are right and fail
to convince others, it is as good as you being wrong, as the idea will
die with you.

If you really don't have the skill to persuade others, what makes you
think you actually have the skill to have come up with something that novel.

Yes, there HAVE been people who came up with ideas that others thought
were crazy, but later they were convinced. The key here is that the
people that came up with them actually understood the fields they
created in, and were able to break down their ideas inot simpler pieces
and show people they were right.

This does NOT apply to you. You keep on showing that you don't
understand the basics of the field you claim to have had your great idea
in, this would tend to indicate that what you have isn't some great new
idea, but some mistake, and likely one that has been made before.

One other big thing to remember, is that when/if you do submit your
paper for review, there is a good chance that some review will do a
search on the subject, and bring up these discussions. EVERY point that
has been brought up and not answered will be seen as an error in your
paper, so you really do need to handle them.

Since you have yet to really answer ANY of the fundamental objections,
you have a lot of work before you.

>
>> Your 'theorems' have been proved to be groundless and totally unsound.
>>
>> You totally don't understand what you are righting about.
>>
>
>

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<ujDVI.7$YW.3@fx05.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20247&group=comp.theory#20247

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.dns-netz.com!news.freedyn.net!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!fdc2.netnews.com!news-out.netnews.com!news.alt.net!fdc3.netnews.com!peer02.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx05.iad.POSTED!not-for-mail
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com>
<87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com>
<87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com>
<_8BVI.106$GD7.95@fx23.iad> <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com>
<i7CVI.13$jl2.7@fx34.iad> <5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com>
<ihCVI.186$2B4.3@fx04.iad> <GfGdnRdNdsTdYbv8nZ2dnUU7-KHNnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <GfGdnRdNdsTdYbv8nZ2dnUU7-KHNnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Lines: 38
Message-ID: <ujDVI.7$YW.3@fx05.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Wed, 25 Aug 2021 22:50:02 -0400
X-Received-Bytes: 3220
 by: Richard Damon - Thu, 26 Aug 2021 02:50 UTC

On 8/25/21 10:28 PM, olcott wrote:
> On 8/25/2021 8:39 PM, Richard Damon wrote:
>> On 8/25/21 9:34 PM, olcott wrote:
>>> On 8/25/2021 8:28 PM, Richard Damon wrote:
>>
>>>> No, becuase UTM(<H^>, <H^>) Halts, thus showing that since H(<H^>,<H^>)
>>>> says non-halting it was wrong.
>>>
>>>
>>> That was your last chance.
>>
>> You admit defeat?
>>
>
> This sort of response provides substantial additional evidence that you
> never had any honest dialogue in mind.
>

What, that I give an non-answer to your non-answer. That is just a good
way to show that you aren't answering.

ANYONE looking at the group will see that you basically NEVER come up
with an error in the statement of other correcting you, but just repeat
your statement that was proven wrong. Others on the other hand present
reasoned arguements reference actual established theory, showing you are
wrong.

You just claim stuff is obvious by the meaning of the words, but you
then show that you don't even know what the real meaning of the words are.

It sounds like you have spent YEARS at this arguement, and it seems like
you haven't even gotten anyone to accept any of your basic points.

That sounds like a failed idea.

You post a crazy idea, and people point out that your don't even have
the right definitions.

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<LfednRsEJtD1mbr8nZ2dnUU7-bHNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20248&group=comp.theory#20248

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 25 Aug 2021 22:03:04 -0500
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com>
<87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com>
<_8BVI.106$GD7.95@fx23.iad> <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com>
<i7CVI.13$jl2.7@fx34.iad> <5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com>
<ihCVI.186$2B4.3@fx04.iad> <CeidnS_08apsaLv8nZ2dnUU7-RmdnZ2d@giganews.com>
<sg6ss9$o8n$1@dont-email.me> <SZ-dncSHQLR3Z7v8nZ2dnUU7-W2dnZ2d@giganews.com>
<VdDVI.486$lC6.43@fx41.iad>
From: NoO...@NoWhere.com (olcott)
Date: Wed, 25 Aug 2021 22:03:03 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <VdDVI.486$lC6.43@fx41.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Message-ID: <LfednRsEJtD1mbr8nZ2dnUU7-bHNnZ2d@giganews.com>
Lines: 53
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-myY3xxjbpsUw4JXi3Nn7Y/qPzNTEb0d/LSEGALhQ5NsWrgCmFEVuJISs1lzCtHSk5X/Gj1RbzRsINBB!V9b2X2HFiImRqdzRC2vg4nBKtKl4bZxt0lwaJA6iL+ZbdyH/jiWKR6c6DNq6CrCyA3XKAh9PBQKC!vAw=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 4006
 by: olcott - Thu, 26 Aug 2021 03:03 UTC

On 8/25/2021 9:44 PM, Richard Damon wrote:
> On 8/25/21 10:22 PM, olcott wrote:
>> On 8/25/2021 9:04 PM, Richard Damon wrote:
>>> On 8/25/21 10:01 PM, olcott wrote:
>>>> On 8/25/2021 8:39 PM, Richard Damon wrote:
>>>>> On 8/25/21 9:34 PM, olcott wrote:
>>>>>> On 8/25/2021 8:28 PM, Richard Damon wrote:
>>>>>
>>>>>>> No, becuase UTM(<H^>, <H^>) Halts, thus showing that since
>>>>>>> H(<H^>,<H^>)
>>>>>>> says non-halting it was wrong.
>>>>>>
>>>>>>
>>>>>> That was your last chance.
>>>>>
>>>>> You admit defeat?
>>>>>
>>>>
>>>> I acknowledge that you are an incorrigible jackass.
>>>> The review process moves to phase two.
>>>>
>>>
>>> What does that mean? You going to write the paper to submit to get your
>>> rejection?
>>>
>>> You have yet to show anywhere whre my basic objections are incorrect.
>>>
>>
>> You know full well that your "objections" are pure drivel.
>
> No, I, and everyone else who is reading this will see that what I say
> makes sense.
>
> YOUR statements are the 'pure drivel'.
>
> Please note that basically no one belives your statements and everyone
> thinks you are wrong. While it is possible that you have discovered some
> hidden secret, it is very unlikely. One key thing to ask yourself, what
> grounds do I have to actually expect that I could come up with some
> insite like that that no one else beleives.
Because of this my work is not getting an honest review. It is obvious
that my work is not getting an honest review to anyone knowing the
material very well that all of the "rebuttals" simply dodge directly
assessing my points and change to subject to some other points.

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<LfednRoEJtA_mbr8nZ2dnUU7-bFQAAAA@giganews.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20249&group=comp.theory#20249

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!feeder1.feed.usenet.farm!feed.usenet.farm!tr2.eu1.usenetexpress.com!feeder.usenetexpress.com!tr1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!buffer1.nntp.dca1.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 25 Aug 2021 22:04:02 -0500
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com> <87h7fhgpjm.fsf@bsb.me.uk> <cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com> <87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com> <87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com> <87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com> <87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com> <87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com> <87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com> <87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com> <87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com> <_8BVI.106$GD7.95@fx23.iad> <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com> <i7CVI.13$jl2.7@fx34.iad> <5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com> <ihCVI.186$2B4.3@fx04.iad> <GfGdnRdNdsTdYbv8nZ2dnUU7-KHNnZ2d@giganews.com> <ujDVI.7$YW.3@fx05.iad>
From: NoO...@NoWhere.com (olcott)
Date: Wed, 25 Aug 2021 22:04:01 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <ujDVI.7$YW.3@fx05.iad>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Message-ID: <LfednRoEJtA_mbr8nZ2dnUU7-bFQAAAA@giganews.com>
Lines: 34
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-dZWg7XMnI5efHRZ/w8VKWTVxLN3TKyvAExGVNV0HjAGJxQF6yXjwiJpICtJopkC3wg331WTkHtVudXn!j/higem6eV0I+ua9rnh5e83SLgb2MgD6J1K3DMuM4Yl0G04oqmpf+aqYmV+DnvWd/oizwUQ3AXED!zAw=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 3211
 by: olcott - Thu, 26 Aug 2021 03:04 UTC

On 8/25/2021 9:50 PM, Richard Damon wrote:
> On 8/25/21 10:28 PM, olcott wrote:
>> On 8/25/2021 8:39 PM, Richard Damon wrote:
>>> On 8/25/21 9:34 PM, olcott wrote:
>>>> On 8/25/2021 8:28 PM, Richard Damon wrote:
>>>
>>>>> No, becuase UTM(<H^>, <H^>) Halts, thus showing that since H(<H^>,<H^>)
>>>>> says non-halting it was wrong.
>>>>
>>>>
>>>> That was your last chance.
>>>
>>> You admit defeat?
>>>
>>
>> This sort of response provides substantial additional evidence that you
>> never had any honest dialogue in mind.
>>
>
> What, that I give an non-answer to your non-answer. That is just a good
> way to show that you aren't answering.
>
> ANYONE looking at the group will see that you basically NEVER come up
> with an error in the statement of other correcting you,

Because these "corrections" simply change the subject to a different
subject.

--
Copyright 2021 Pete Olcott

"Great spirits have always encountered violent opposition from mediocre
minds." Einstein

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ conversation has ended? ]

<874kbcaojh.fsf@bsb.me.uk>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20250&group=comp.theory#20250

  copy link   Newsgroups: comp.theory
Followup: comp.theory
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: ben.use...@bsb.me.uk (Ben Bacarisse)
Newsgroups: comp.theory
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ conversation has ended? ]
Followup-To: comp.theory
Date: Thu, 26 Aug 2021 04:10:58 +0100
Organization: A noiseless patient Spider
Lines: 59
Message-ID: <874kbcaojh.fsf@bsb.me.uk>
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com>
<87o89pf5zi.fsf@bsb.me.uk>
<R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk>
<edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk>
<INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk>
<5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk>
<Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk>
<__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk>
<tqadndv0qJ8vOLj8nZ2dnUU7-R_NnZ2d@giganews.com>
<1LCdnZZtHK3SK7j8nZ2dnUU7-R_NnZ2d@giganews.com>
<87lf4pa56n.fsf@bsb.me.uk>
<feudnRmpetF2G7v8nZ2dnUU7-VfNnZ2d@giganews.com>
<87czq19wx0.fsf@bsb.me.uk>
<Y7adnS3RyacCCbv8nZ2dnUU7-UWdnZ2d@giganews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: reader02.eternal-september.org; posting-host="d5c8a507b35e31b8ca7c2c91251dd7bc";
logging-data="12981"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19l2JB2FLYK15/NeF4YGsGsxORb30YoB2k="
Cancel-Lock: sha1:0HsmbzZQpmIYBWKXjsxU5v9mixU=
sha1:kqz8SrqtIZgHjjQJFNW7br6f6bs=
X-BSB-Auth: 1.9c6757d7bd96da6e7819.20210826041058BST.874kbcaojh.fsf@bsb.me.uk
 by: Ben Bacarisse - Thu, 26 Aug 2021 03:10 UTC

olcott <NoOne@NoWhere.com> writes:

> On 8/25/2021 1:55 PM, Ben Bacarisse wrote:
>> olcott <NoOne@NoWhere.com> writes:
>>
>>> On 8/25/2021 10:56 AM, Ben Bacarisse wrote:
>>
>>>> The halting problem is about the existence of a TM that accept those
>>>> string pairs (and only those string pairs) that encode halting
>>>> computations. All other strings are to be rejected. The halting
>>>> theorem states that no TM is a such a decider -- every TM fails to
>>>> correctly classify at least one string pair.
>>>>
>>>> You claim to have a TM, unfortunately called H, which is a halt decider.
>>>> (Yes, you sometimes deny it is a general halt decider but you keep
>>>> quoting me saying your algorithm is one, so I presume you agree that it
>>>> must be one.)
>> So you are indeed claiming to have a general halt decider! That's a
>> grand boast! (You need to say "no" if you don't want this to be taken
>> as your real position.)
>>
>>>> You tell us, again and again, that the computation of Ĥ applied to the
>>>> encoding of Ĥ (written ⟨Ĥ⟩) is a halting computation. You are quick to
>>>> jump in and say that it "only halts because... reason", but it's a
>>>> halting computation whatever the reason.
>>>> That halting computation is encoded as the string pair ⟨Ĥ⟩ ⟨Ĥ⟩. (I
>>>> prefer a notation that makes the pairing of an encoded TM and some input
>>>> explicit, but that boat sailed years ago.)
>>>> You also tell is that H rejects the string pair ⟨Ĥ⟩ ⟨Ĥ⟩. I.e. you tell
>>>> us everything we need to know to be sure that H is wrong about at least
>>>> this one halting problem instance.
>>>
>>> Ĥ.q0 ⟨Ĥ1⟩ ⊢* Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ ⊢* Ĥ.qn
>>>
>>> Until you understand that the input to Ĥ.qx ⟨Ĥ1⟩ ⟨Ĥ2⟩ is not a halting
>>> computation there is no sense continuing this one way dialogue.
>> Until you understand that ⟨Ĥ1⟩ ⟨Ĥ2⟩ equals ⟨Ĥ⟩ ⟨Ĥ⟩ and that ⟨Ĥ⟩ ⟨Ĥ⟩ is a
>> string that should be accepted you are just blowing smoke.
>
> (a) While the simulating halt decider at Ĥ.qx remains in pure
> simulation mode its input ⟨Ĥ1⟩ ⟨Ĥ2⟩ never halts.

Yes, though the language is disingenuous.

> (b) Every computation that never halts while its simulating halt
> decider remains in pure simulation mode is a computation that never
> halts.

No, only computations that don't halt are halting computations. The
others, like the one encoded in the string ⟨Ĥ⟩ ⟨Ĥ⟩, are halting
computation and those strings should be accepted by a halt decider.

> Too disingenuous to continue.

Excellent! Mind you, you've said you won't talk go to me many times
before and I always end up disappointed.

--
Ben.

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<9DDVI.705$rsCb.634@fx01.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20251&group=comp.theory#20251

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!news-out.netnews.com!news.alt.net!fdc3.netnews.com!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx01.iad.POSTED!not-for-mail
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<87o89pf5zi.fsf@bsb.me.uk> <R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com>
<87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com>
<_8BVI.106$GD7.95@fx23.iad> <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com>
<i7CVI.13$jl2.7@fx34.iad> <5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com>
<ihCVI.186$2B4.3@fx04.iad> <GfGdnRdNdsTdYbv8nZ2dnUU7-KHNnZ2d@giganews.com>
<ujDVI.7$YW.3@fx05.iad> <LfednRoEJtA_mbr8nZ2dnUU7-bFQAAAA@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <LfednRoEJtA_mbr8nZ2dnUU7-bFQAAAA@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Lines: 43
Message-ID: <9DDVI.705$rsCb.634@fx01.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Wed, 25 Aug 2021 23:10:55 -0400
X-Received-Bytes: 3321
 by: Richard Damon - Thu, 26 Aug 2021 03:10 UTC

On 8/25/21 11:04 PM, olcott wrote:
> On 8/25/2021 9:50 PM, Richard Damon wrote:
>> On 8/25/21 10:28 PM, olcott wrote:
>>> On 8/25/2021 8:39 PM, Richard Damon wrote:
>>>> On 8/25/21 9:34 PM, olcott wrote:
>>>>> On 8/25/2021 8:28 PM, Richard Damon wrote:
>>>>
>>>>>> No, becuase UTM(<H^>, <H^>) Halts, thus showing that since
>>>>>> H(<H^>,<H^>)
>>>>>> says non-halting it was wrong.
>>>>>
>>>>>
>>>>> That was your last chance.
>>>>
>>>> You admit defeat?
>>>>
>>>
>>> This sort of response provides substantial additional evidence that you
>>> never had any honest dialogue in mind.
>>>
>>
>> What, that I give an non-answer to your non-answer. That is just a good
>> way to show that you aren't answering.
>>
>> ANYONE looking at the group will see that you basically NEVER come up
>> with an error in the statement of other correcting you,
>
> Because these "corrections" simply change the subject to a different
> subject.
>

No, the corrections show that the whole foundation of your argument are
flawed.

Maybe your problem is that you can't see what the foundation of your
arguement actually IS and that you are building on something rotten.

YOU are the one asking questions like have you stopped beating your
wife? and then you object that I, and others, point out that this
question isn't really important, because it is based on some totally
incorrect foundations.

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<WIDVI.5960$Kv2.3004@fx47.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20252&group=comp.theory#20252

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!news-out.netnews.com!news.alt.net!fdc3.netnews.com!peer02.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx47.iad.POSTED!not-for-mail
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ distinct computations ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk> <edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk> <INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk> <5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk> <Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk> <__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk> <pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com>
<87r1eha6x8.fsf@bsb.me.uk> <yK2dnZkA2Nsu5Lv8nZ2dnUU7-THNnZ2d@giganews.com>
<_8BVI.106$GD7.95@fx23.iad> <FaydnfJTMNyofrv8nZ2dnUU7-e3NnZ2d@giganews.com>
<i7CVI.13$jl2.7@fx34.iad> <5Y6dndhJqqgGcrv8nZ2dnUU7-RWdnZ2d@giganews.com>
<ihCVI.186$2B4.3@fx04.iad> <CeidnS_08apsaLv8nZ2dnUU7-RmdnZ2d@giganews.com>
<sg6ss9$o8n$1@dont-email.me> <SZ-dncSHQLR3Z7v8nZ2dnUU7-W2dnZ2d@giganews.com>
<VdDVI.486$lC6.43@fx41.iad> <LfednRsEJtD1mbr8nZ2dnUU7-bHNnZ2d@giganews.com>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <LfednRsEJtD1mbr8nZ2dnUU7-bHNnZ2d@giganews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Lines: 68
Message-ID: <WIDVI.5960$Kv2.3004@fx47.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Wed, 25 Aug 2021 23:17:10 -0400
X-Received-Bytes: 4431
 by: Richard Damon - Thu, 26 Aug 2021 03:17 UTC

On 8/25/21 11:03 PM, olcott wrote:
> On 8/25/2021 9:44 PM, Richard Damon wrote:
>> On 8/25/21 10:22 PM, olcott wrote:
>>> On 8/25/2021 9:04 PM, Richard Damon wrote:
>>>> On 8/25/21 10:01 PM, olcott wrote:
>>>>> On 8/25/2021 8:39 PM, Richard Damon wrote:
>>>>>> On 8/25/21 9:34 PM, olcott wrote:
>>>>>>> On 8/25/2021 8:28 PM, Richard Damon wrote:
>>>>>>
>>>>>>>> No, becuase UTM(<H^>, <H^>) Halts, thus showing that since
>>>>>>>> H(<H^>,<H^>)
>>>>>>>> says non-halting it was wrong.
>>>>>>>
>>>>>>>
>>>>>>> That was your last chance.
>>>>>>
>>>>>> You admit defeat?
>>>>>>
>>>>>
>>>>> I acknowledge that you are an incorrigible jackass.
>>>>> The review process moves to phase two.
>>>>>
>>>>
>>>> What does that mean? You going to write the paper to submit to get your
>>>> rejection?
>>>>
>>>> You have yet to show anywhere whre my basic objections are incorrect.
>>>>
>>>
>>> You know full well that your "objections" are pure drivel.
>>
>> No, I, and everyone else who is reading this will see that what I say
>> makes sense.
>>
>> YOUR statements are the 'pure drivel'.
>>
>> Please note that basically no one belives your statements and everyone
>> thinks you are wrong. While it is possible that you have discovered some
>> hidden secret, it is very unlikely. One key thing to ask yourself, what
>> grounds do I have to actually expect that I could come up with some
>> insite like that that no one else beleives.
> Because of this my work is not getting an honest review. It is obvious
> that my work is not getting an honest review to anyone knowing the
> material very well that all of the "rebuttals" simply dodge directly
> assessing my points and change to subject to some other points.
>

No, it HAS gotten an Honest review, and you just don't want to accept
it, because it shows how BAD your logic is.

Since YOU have shown that you don't understand even the basics of the
material you are working on.

YOU are the one specializing in diversions, and don't deal with the
fundamentals.

Things like, the definition of Halting is based on the behavior of the
ACTUAL machine. Aborted simulations don't actually prove anything.

Things like that a Computation will ALWAYS give the same answer for a
gien input, BY DEFINITION. If it doesn't, it isn't a Computation. PERIOD.

You make nonsense claims about arcs on Turing Machine Diagrams that just
don't exist. (Like back from H^.qx to H^.q0, maybe you now understand
that, but I am not sure).

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ conversation has ended? ]

<CMDVI.3286$nR3.588@fx38.iad>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20253&group=comp.theory#20253

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!4.us.feeder.erje.net!2.eu.feeder.erje.net!feeder.erje.net!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!feeder1.feed.usenet.farm!feed.usenet.farm!peer01.ams4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx38.iad.POSTED!not-for-mail
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input
to H? [ conversation has ended? ]
Newsgroups: comp.theory
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com> <87o89pf5zi.fsf@bsb.me.uk>
<R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com> <87k0kce1yk.fsf@bsb.me.uk>
<edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com> <87bl5oc62l.fsf@bsb.me.uk>
<INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com> <87tujfbv4y.fsf@bsb.me.uk>
<5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com> <87lf4rbksk.fsf@bsb.me.uk>
<Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com> <87fsuzaq8t.fsf@bsb.me.uk>
<__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com> <87zgt69xah.fsf@bsb.me.uk>
<tqadndv0qJ8vOLj8nZ2dnUU7-R_NnZ2d@giganews.com>
<1LCdnZZtHK3SK7j8nZ2dnUU7-R_NnZ2d@giganews.com> <87lf4pa56n.fsf@bsb.me.uk>
<feudnRmpetF2G7v8nZ2dnUU7-VfNnZ2d@giganews.com> <87czq19wx0.fsf@bsb.me.uk>
<Y7adnS3RyacCCbv8nZ2dnUU7-UWdnZ2d@giganews.com> <874kbcaojh.fsf@bsb.me.uk>
From: Rich...@Damon-Family.org (Richard Damon)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <874kbcaojh.fsf@bsb.me.uk>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Lines: 19
Message-ID: <CMDVI.3286$nR3.588@fx38.iad>
X-Complaints-To: abuse@easynews.com
Organization: Forte - www.forteinc.com
X-Complaints-Info: Please be sure to forward a copy of ALL headers otherwise we will be unable to process your complaint properly.
Date: Wed, 25 Aug 2021 23:21:05 -0400
X-Received-Bytes: 2495
 by: Richard Damon - Thu, 26 Aug 2021 03:21 UTC

On 8/25/21 11:10 PM, Ben Bacarisse wrote:
> olcott <NoOne@NoWhere.com> writes:

>> Too disingenuous to continue.
>
> Excellent! Mind you, you've said you won't talk go to me many times
> before and I always end up disappointed.
>

Yes, me too. It is clear that when people clearly point out his
mistakes, his brain starts to go crazy and he finds it irresistible to
lash out and try to muddy the air with some illogic to try and hide the
clear rebuttal.

I think he hopes that the thread will go off some other direction and
the clear rebuttal will be forgotten.

THAT is why he calls them 'dishonest dodges', he thinks if he says that
enough some people might beleive it and not look at them.

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]

<87y28o998g.fsf@bsb.me.uk>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20254&group=comp.theory#20254

  copy link   Newsgroups: comp.theory
Followup: comp.theory
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: ben.use...@bsb.me.uk (Ben Bacarisse)
Newsgroups: comp.theory
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ distinct computations ]
Followup-To: comp.theory
Date: Thu, 26 Aug 2021 04:26:55 +0100
Organization: A noiseless patient Spider
Lines: 25
Message-ID: <87y28o998g.fsf@bsb.me.uk>
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<87h7fhgpjm.fsf@bsb.me.uk>
<cradndCzBKW6Ir_8nZ2dnUU7-XWdnZ2d@giganews.com>
<87o89pf5zi.fsf@bsb.me.uk>
<R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk>
<edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk>
<INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk>
<5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk>
<Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk>
<__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk>
<pc6dnd7lf6NfI7j8nZ2dnUU7-fXNnZ2d@giganews.com>
<5zqVI.10579$kQ4.10540@fx13.iad>
<Ea2dndkCwo0bzbv8nZ2dnUU7-dHNnZ2d@giganews.com>
<Z2BVI.1293$F26.792@fx44.iad>
<Y7udnRjYJLheQrv8nZ2dnUU7-avNnZ2d@giganews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: reader02.eternal-september.org; posting-host="d5c8a507b35e31b8ca7c2c91251dd7bc";
logging-data="12981"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19+jjhNh7WizCajvAqfX9wMnC5bTGK/en0="
Cancel-Lock: sha1:8prwuuuuc3eR8dnBWzNos0YWe0k=
sha1:cdyN58Zteii8yLz196HZaMeBnmQ=
X-BSB-Auth: 1.184d780e236d62953555.20210826042655BST.87y28o998g.fsf@bsb.me.uk
 by: Ben Bacarisse - Thu, 26 Aug 2021 03:26 UTC

olcott <NoOne@NoWhere.com> writes:

> When we define Ĵ to be exactly like Ĥ except that it has a UTM at Ĵ.qx
> instead of a simulating halt decider then we can see that Ĵ applied to
> ⟨Ĵ⟩ never halts.
>
> Ĵ copies its input ⟨Ĵ1⟩ to ⟨Ĵ2⟩ then simulates this input Ĵ1 with its input ⟨Ĵ2⟩
> which copies its input ⟨Ĵ2⟩ to ⟨Ĵ3⟩ then simulates this input Ĵ2 with
> its input ⟨Ĵ3⟩
> which copies its input ⟨Ĵ3⟩ to ⟨Ĵ4⟩ then simulates this input Ĵ3 with
> its input ⟨Ĵ4⟩ ...

Again, no. The computation is indeed non halting, but this is not
literally how it unfolds. This is a metaphorical description of the
execution, not a literal on. Only the first copy is a literal coping of
a string on the tape.

> With the Peter Linz Ĥ we have exactly the same thing while the
> simulating halt decider at Ĥ.qx remains in simulation mode.

Peter Linz's H does not exist. Yours does (and is wrong) but his does
not.

--
Ben.

Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ conversation has ended? ]

<87sfyw98xg.fsf@bsb.me.uk>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=20255&group=comp.theory#20255

  copy link   Newsgroups: comp.theory
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: ben.use...@bsb.me.uk (Ben Bacarisse)
Newsgroups: comp.theory
Subject: Re: How do we know H(P,P)==0 is the correct halt status for the input to H? [ conversation has ended? ]
Date: Thu, 26 Aug 2021 04:33:31 +0100
Organization: A noiseless patient Spider
Lines: 22
Message-ID: <87sfyw98xg.fsf@bsb.me.uk>
References: <3YOdnecvDsA5Q4r8nZ2dnUU7-TXNnZ2d@giganews.com>
<R_WdnWjO0dnDlb78nZ2dnUU7-bvNnZ2d@giganews.com>
<87k0kce1yk.fsf@bsb.me.uk>
<edCdnTY_IvB2N778nZ2dnUU7-WvNnZ2d@giganews.com>
<87bl5oc62l.fsf@bsb.me.uk>
<INadnSiJbfTFYb78nZ2dnUU7-LPNnZ2d@giganews.com>
<87tujfbv4y.fsf@bsb.me.uk>
<5bidne_8HrBuqbn8nZ2dnUU7-dfNnZ2d@giganews.com>
<87lf4rbksk.fsf@bsb.me.uk>
<Mf2dnamm9d978bn8nZ2dnUU7-cHNnZ2d@giganews.com>
<87fsuzaq8t.fsf@bsb.me.uk>
<__WdneskYvGLiLj8nZ2dnUU7-U3NnZ2d@giganews.com>
<87zgt69xah.fsf@bsb.me.uk>
<tqadndv0qJ8vOLj8nZ2dnUU7-R_NnZ2d@giganews.com>
<1LCdnZZtHK3SK7j8nZ2dnUU7-R_NnZ2d@giganews.com>
<87lf4pa56n.fsf@bsb.me.uk>
<feudnRmpetF2G7v8nZ2dnUU7-VfNnZ2d@giganews.com>
<87czq19wx0.fsf@bsb.me.uk>
<Y7adnS3RyacCCbv8nZ2dnUU7-UWdnZ2d@giganews.com>
<874kbcaojh.fsf@bsb.me.uk> <CMDVI.3286$nR3.588@fx38.iad>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org; posting-host="d5c8a507b35e31b8ca7c2c91251dd7bc";
logging-data="12981"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/OsaWfxAmB22DqmNzRI5Fvb5jls+Vv7/Q="
Cancel-Lock: sha1:3C2/swReVOrruYdDwj58TOOn0oM=
sha1:2nJG5N29zX6N0S7OzF6p7o/29to=
X-BSB-Auth: 1.a04bcb36c59c9da65d0e.20210826043331BST.87sfyw98xg.fsf@bsb.me.uk
 by: Ben Bacarisse - Thu, 26 Aug 2021 03:33 UTC

Richard Damon <Richard@Damon-Family.org> writes:

> On 8/25/21 11:10 PM, Ben Bacarisse wrote:
>> olcott <NoOne@NoWhere.com> writes:
>
>>> Too disingenuous to continue.
>>
>> Excellent! Mind you, you've said you won't talk go to me many times
>> before and I always end up disappointed.
>
> Yes, me too. It is clear that when people clearly point out his
> mistakes, his brain starts to go crazy and he finds it irresistible to
> lash out and try to muddy the air with some illogic to try and hide the
> clear rebuttal.

He'll keep replying, I'm sure. The only way the madness can end is if
we stop replying. It's not as if any casual reader can be in any doubt
that he's wrong. He'll taunt and hurl abuse, but that is a mark of
respect coming from PO.

--
Ben.

Pages:12345678910111213141516171819
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor