Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

Your own mileage may vary.


tech / sci.math / Re: Concise refutation of halting problem proofs V52 [ error or dishonesty ]

Re: Concise refutation of halting problem proofs V52 [ error or dishonesty ]

<PaqdncLyCYZdhW_8nZ2dnUU7-evNnZ2d@giganews.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=89383&group=sci.math#89383

  copy link   Newsgroups: comp.theory comp.ai.philosophy sci.logic sci.math
Followup: comp.theory
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 26 Jan 2022 22:00:00 -0600
Date: Wed, 26 Jan 2022 21:59:59 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.5.1
Subject: Re: Concise refutation of halting problem proofs V52 [ error or
dishonesty ]
Content-Language: en-US
Newsgroups: comp.theory,comp.ai.philosophy,sci.logic,sci.math
References: <ssh8vu$4c0$1@dont-email.me>
<qOWdnYg47f8nkW38nZ2dnUU7-XvNnZ2d@giganews.com>
<yW%HJ.7148$h91.5996@fx48.iad>
<pMmdnUSKnpgnEm38nZ2dnUU7-bnNnZ2d@giganews.com>
<Bq0IJ.313197$qz4.269632@fx97.iad>
<GbOdnRAEI7BXAm38nZ2dnUU7-XnNnZ2d@giganews.com>
<UW1IJ.38990$i%.5899@fx04.iad>
<1IudnXCb-OzhJm38nZ2dnUU7-bvNnZ2d@giganews.com>
<Dq3IJ.17537$f04.1511@fx23.iad>
<ubqdneNkd89jWG38nZ2dnUU7-SnNnZ2d@giganews.com>
<S64IJ.27704$7U.16191@fx42.iad>
<8eydnSpcWIVSUm38nZ2dnUU7-XvNnZ2d@giganews.com>
<9k4IJ.15452$jb4.2046@fx24.iad>
<SNudnYZfaZX6Tm38nZ2dnUU7-I3NnZ2d@giganews.com> <LMaIJ.8332$V31.330@fx47.iad>
<hsCdneOV_eybwGz8nZ2dnUU7-KPNnZ2d@giganews.com> <xalIJ.8632$rQ.8159@fx18.iad>
<r8OdnZwzO4tUf2z8nZ2dnUU7-SnNnZ2d@giganews.com> <eXlIJ.16438$2W.334@fx36.iad>
<zIKdnXB_n-rDbWz8nZ2dnUU7-enNnZ2d@giganews.com> <0wmIJ.176$XDR2.80@fx02.iad>
<37adnXNhdcJynW_8nZ2dnUU7-d3NnZ2d@giganews.com>
<csnIJ.19295$OU.5598@fx22.iad>
<vvWdnWkD_aAWm2_8nZ2dnUU7-UHNnZ2d@giganews.com> <N9oIJ.384$N31.159@fx45.iad>
Followup-To: comp.theory
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <N9oIJ.384$N31.159@fx45.iad>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Message-ID: <PaqdncLyCYZdhW_8nZ2dnUU7-evNnZ2d@giganews.com>
Lines: 157
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-OGH+nNh+R0CFdqezZIlxRKasDJIm+/qnHK0cp41Pkd4pbTp4+kzZHW1pQqjAzsqNWElNUZRxuCodQG4!SyCI84szFbLJaKqyPgvPT7GSn6WXkkySRmi4t3Tv24Aw5ha37bbfTGzVNGRCB62C+/5kzbYZFmIj
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: 8977
 by: olcott - Thu, 27 Jan 2022 03:59 UTC

On 1/26/2022 9:18 PM, Richard Damon wrote:
> On 1/26/22 9:42 PM, olcott wrote:
>> On 1/26/2022 8:29 PM, Richard Damon wrote:
>>> On 1/26/22 9:18 PM, olcott wrote:
>>>> On 1/26/2022 7:25 PM, Richard Damon wrote:
>>>>> On 1/26/22 8:07 PM, olcott wrote:
>>>>>> On 1/26/2022 6:46 PM, Richard Damon wrote:
>>>>>>> On 1/26/22 7:09 PM, olcott wrote:
>>>>>>>> On 1/26/2022 5:54 PM, Richard Damon wrote:
>>>>>>>>> On 1/26/22 9:39 AM, olcott wrote:
>>>>>>>>>> On 1/26/2022 6:03 AM, Richard Damon wrote:
>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> _Infinite_Loop()
>>>>>>>>>>>> [00000d9a](01)  55              push ebp
>>>>>>>>>>>> [00000d9b](02)  8bec            mov ebp,esp
>>>>>>>>>>>> [00000d9d](02)  ebfe            jmp 00000d9d
>>>>>>>>>>>> [00000d9f](01)  5d              pop ebp
>>>>>>>>>>>> [00000da0](01)  c3              ret
>>>>>>>>>>>> Size in bytes:(0007) [00000da0]
>>>>>>>>>>>>
>>>>>>>>>>>> You keep coming back to the idea that only an infinite
>>>>>>>>>>>> simulation of an infinite sequence of configurations can
>>>>>>>>>>>> recognize an infinite sequence of configurations.
>>>>>>>>>>>>
>>>>>>>>>>>> That is ridiculously stupid.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> You can detect SOME (not all) infinite execution in finite
>>>>>>>>>>> time due to patterns.
>>>>>>>>>>>
>>>>>>>>>>> There is no finite pattern in the H^ based on an H that at
>>>>>>>>>>> some point goest to H.Qn that correctly detects the infinite
>>>>>>>>>>> behavior.
>>>>>>>>>>>
>>>>>>>>>>> THAT is the point you miss, SOME infinite patterns are only
>>>>>>>>>>> really infinite when you work them out to infinitity.
>>>>>>>>>>>
>>>>>>>>>>> Part of your problem is that the traces you look at are
>>>>>>>>>>> wrong. When H simulates H^, it needs to trace out the actual
>>>>>>>>>>> execution path of the H that part of H^, not switch to
>>>>>>>>>>> tracing what it was tracing.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> You simply lack the intellectual capacity to understand that
>>>>>>>>>> when embedded_H simulates ⟨Ĥ⟩ applied to ⟨Ĥ⟩ this is the pattern:
>>>>>>>>>>
>>>>>>>>>> Ĥ copies its input ⟨Ĥ⟩ to ⟨Ĥ⟩ then embedded_H simulates ⟨Ĥ⟩
>>>>>>>>>> ⟨Ĥ⟩...
>>>>>>>>>> Ĥ copies its input ⟨Ĥ⟩ to ⟨Ĥ⟩ then embedded_H simulates ⟨Ĥ⟩
>>>>>>>>>> ⟨Ĥ⟩...
>>>>>>>>>> Ĥ copies its input ⟨Ĥ⟩ to ⟨Ĥ⟩ then embedded_H simulates ⟨Ĥ⟩
>>>>>>>>>> ⟨Ĥ⟩...
>>>>>>>>>> Ĥ copies its input ⟨Ĥ⟩ to ⟨Ĥ⟩ then embedded_H simulates ⟨Ĥ⟩
>>>>>>>>>> ⟨Ĥ⟩...
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Which only happens if H NEVER aborts its simulation and thus
>>>>>>>>> can't give an answer.
>>>>>>>>>
>>>>>>>>> If H DOES abort its simulation at ANY point, then the above is
>>>>>>>>> NOT the accurate trace of the behavior of the input.
>>>>>>>>>
>>>>>>>>>
>>>>>>>> YOU ARE MUCH DUMBER THAN A BOX OF ROCKS BECAUSE
>>>>>>>>
>>>>>>>> _Infinite_Loop()
>>>>>>>> [00000d9a](01)  55              push ebp
>>>>>>>> [00000d9b](02)  8bec            mov ebp,esp
>>>>>>>> [00000d9d](02)  ebfe            jmp 00000d9d
>>>>>>>> [00000d9f](01)  5d              pop ebp
>>>>>>>> [00000da0](01)  c3              ret
>>>>>>>> Size in bytes:(0007) [00000da0]
>>>>>>>>
>>>>>>>> You exactly same jackass point equally applies to this case:
>>>>>>>>
>>>>>>>> Unless H simulates the infinite loop infinitely it is not an
>>>>>>>> accurate simulation.
>>>>>>>>
>>>>>>>
>>>>>>> So, no rubbutal just red herring sushi.
>>>>>>>
>>>>>>>
>>>>>>> The key point you miss is that if H does abort its simulation,
>>>>>>> then it needs to take into account that the machine it is
>>>>>>> simulating will do so too.
>>>>>>>
>>>>>>
>>>>>> As long as H correctly determines that its simulated input cannot
>>>>>> possibly reach its final state in any finite number of steps it
>>>>>> has conclusively proved that this input never halts according to
>>>>>> the Linz definition:
>>>>>
>>>>>
>>>>> But it needs to prove that the UTM of its input never halts, and
>>>>> for H^, that means even if the H insisde H^ goes to H.Qn which
>>>>> means that H^ goes to H^.Qn, which of course Halts.
>>>>>
>>>>
>>>> As soon as embedded_H (not H) determines that its simulated input
>>>> ⟨Ĥ⟩ applied to ⟨Ĥ⟩ cannot possibly reach its final state in any
>>>> finite number of steps it terminates this simulation immediately
>>>> stopping every element of the entire chain of nested simulations.
>>>>
>>>
>>> If you are claiming that embedded_H and H behave differently then you
>>> have been lying that you built H^ by the instruction of Linz, as the
>>> copy of H inside H^ is IDENTICAL (except what happens AFTER getting
>>> to H.Qy)
>>>
>>> Now, IF H could make that proof, then it would be correct to go to
>>> H.Qn, but it would need to take into account that H^ halts if its
>>> copy of H goes to H.Qn, so this is NEVER possible.
>>>
>>> FAIL
>>>
>>>> Then embedded_H transitions to Ĥ.qn which causes the original Ĥ
>>>> applied to ⟨Ĥ⟩ to halt. Since Ĥ applied to ⟨Ĥ⟩ is not an input to
>>>> embedded_H and a decider is only accountable for computing the
>>>> mapping from its actual inputs to an accept or reject state it makes
>>>> no difference that Ĥ applied to ⟨Ĥ⟩ halts.
>>>
>>> Thus you have admitted to LYING about working on the Halting problem
>>> as if you were the embedded_H would be the same algorithm as H, and
>>> the requirement on H was that is IS accoutable for the machine its
>>> input represents,
>>
>> You are simply too freaking stupid to understand that deciders thus
>> halt deciders are only accountable for computing the mapping from
>> their actual inputs (nothing else in the whole freaking universe
>> besides their actual inputs) to an accept or reject state.
>>
>> An actual computer scientist would know this.
>>
>
> It seems you don't understand the difference between capabilities and
> requirements.
>
> H is only CAPABLE of deciding based on what it can do. It can only
> computate a mapping based on what it actually can do.
>
> It is REQUIRED to meet its requirements, which is to decide on the
> behavior of what its input would do if given to a UTM.
>

embedded_H must only determine whether or not is simulated input can
ever reach its final state in any finite number of steps.

--
Copyright 2021 Pete Olcott

Talent hits a target no one else can hit;
Genius hits a target no one else can see.
Arthur Schopenhauer

SubjectRepliesAuthor
o Concise refutation of halting problem proofs V52 [ Linz Proof ]

By: olcott on Sat, 22 Jan 2022

72olcott
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor