Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)

Liste des GroupesRevenir à s logic 
Sujet : Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)
De : polcott2 (at) *nospam* gmail.com (olcott)
Groupes : comp.theory sci.logic
Date : 08. Mar 2024, 01:02:07
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <usdh1e$19t14$1@dont-email.me>
References : 1 2
User-Agent : Mozilla Thunderbird
On 3/7/2024 4:32 PM, Richard Damon wrote:
On 3/7/24 1:05 PM, olcott wrote:
H1(D,D) maps its input + its own machine address 00001422 to its output.
  H(D,D) maps its input + its own machine address 00001522 to its output.
Thus both H1 and H are computable functions of their input.
 And thus you are admitting that Neither H or H1 are actually correct Halt Deciders, as Halt Deciders must be only a function of the description of the Compuation to be decided.
 
It turns out that both H(D,D) and H1(D,D) do correctly determine
whether or not they must abort the simulation of their input.
That you or others consider this somehow improper does not change
the verified fact that they both correctly determine whether or
not they must abort their simulation.
It is also the case that both H1(D,D) and H(D,D) are a pure function
of their inputs when we construe their own machine address to be an
element of these inputs.

>
Turing machines don't even have the idea of their own machine
address so this exact same thing cannot be Turing computable.
 And it isn't a Halt Decider even in Olcott machines as the algorithm is shown to vary by a parameter that it isn't allowed to vary to be a Halt Decider.
 
>
Olcott machines entirely anchored in Turing machine notions
can compute the equivalent of H1(D,D) and H(D,D).
>
Because Olcott machines are essentially nothing more than
conventional UTM's combined with Conventional Turing machine
descriptions their essence is already fully understood.
>
The input to Olcott machines can simply be the conventional
space delimited Turing Machine input followed by four spaces.
>
This is followed by the machine description of the machine
that the UTM is simulating followed by four more spaces.
>
When this input is ignored Olcott machines compute the
exact same set as Turing machines.
>
Unlike Turing machines, Olcott machines have the basis to
determine that they have been called with copies of their
own TMD.
>
Ĥ.q0 ⟨Ĥ⟩ ⊢* Ĥ.Hq0 ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.Hqy ∞ // Ĥ applied to ⟨Ĥ⟩ halts
Ĥ.q0 ⟨Ĥ⟩ ⊢* Ĥ.Hq0 ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.Hqn   // Ĥ applied to ⟨Ĥ⟩ does not halt
>
With Olcott machines Ĥ.H ⟨Ĥ⟩ ⟨Ĥ⟩ <Ĥ> and H ⟨Ĥ⟩ ⟨Ĥ⟩ <H> do
not have the same inputs thus can compute different outputs
when they do not ignore their own TMD.
>
>
 THen you build H^ wrong. Of course with your change in mechanics, the H^ that needs to be generated will be a bit different.
 
That Olcott machines always know their own TMD is unconventional.
That their own TMD is correctly construed as an additional input
to their computation (whenever they don't ignore it) does provide
the reason why Ĥ.H ⟨Ĥ⟩ ⟨Ĥ⟩ <Ĥ> and H ⟨Ĥ⟩ ⟨Ĥ⟩ <H> can compute different
results and still be computations.

H^ needs to have a copy of the algorithm of the decider at that point, and give it exactly the same input as the decider will get.
 
Both Ĥ and H have a copy of their own non-identical TMD's.

Since H will get on its tape the string (H^) (H^) (H), that is exactly what H^ (H^) must put on its tape,
Not at all. Olcott machines are exactly the same as Turing machines
yet always have a copy of their own machine description appended to
the end of their own tape. That you assert that H must have a copy of
some other TMD at the end of its tape is quite nutty.

so since H^ starts its tape with the values (M) (H^),
Not at all. The only Ĥ that I am talking about only has
its own TMD for its input.

it must duplicate the (M), and replace the (H^) with the description of the version of H it is going to confound. (even though that isn't the description of the copy at H^.H).
 Note, while your master UTM may make sure that no Top level machine is given the wrong description, there is nothing stopping a machine from faking the data to a submachine of it.
 
No matter how Ĥ screws things up it will either halt or fail
to halt. No matter how much Ĥ screws itself up none of these
things have any effect what-so-ever on H.

You are just not thinking the problem out far enough.
 You are apparently not smart enough to figure out what this change needed to be to handle you new definition of Olcott machines, but I was able to do that in just a few minutes of thinking.
I thought this through more deeply than you have and you cannot
show otherwise by providing correct reasoning why my ideas will
not work.
*Like most people you conflate unconventional with impossible*
--
Copyright 2024 Olcott "Talent hits a target no one else can hit; Genius
hits a target no one else can see." Arthur Schopenhauer

Date Sujet#  Auteur
7 Mar 24 * We finally know exactly how H1(D,D) derives a different result than H(D,D)52olcott
8 Mar 24 +* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)49Richard Damon
8 Mar 24 i`* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)48olcott
8 Mar 24 i +* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)18olcott
8 Mar 24 i i+* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)2olcott
8 Mar 24 i ii`- Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)1Richard Damon
8 Mar 24 i i+* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)10olcott
8 Mar 24 i ii+- Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)1Richard Damon
8 Mar 24 i ii`* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)8Richard Damon
8 Mar 24 i ii `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)7olcott
8 Mar 24 i ii  `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)6Richard Damon
8 Mar 24 i ii   `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)5olcott
8 Mar 24 i ii    `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)4Richard Damon
8 Mar 24 i ii     `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)3olcott
8 Mar 24 i ii      `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)2olcott
8 Mar 24 i ii       `- Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)1olcott
8 Mar 24 i i`* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)5olcott
8 Mar 24 i i `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)4olcott
8 Mar 24 i i  `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D) --closure yet?--3olcott
8 Mar 24 i i   `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D) --closure yet?--2olcott
9 Mar 24 i i    `- Re: We finally know exactly how H1(D,D) derives a different result than H(D,D) --Richard goes around in circles--1immibis
8 Mar 24 i `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)29André G. Isaak
8 Mar 24 i  +* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)27immibis
8 Mar 24 i  i+* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)23olcott
8 Mar 24 i  ii`* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)22Richard Damon
8 Mar 24 i  ii `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)21olcott
8 Mar 24 i  ii  `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)20Richard Damon
8 Mar 24 i  ii   `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)19olcott
8 Mar 24 i  ii    `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)18Yaxley Peaks
15 Mar 24 i  ii     `* Re: H ⟨Ĥ⟩ ⟨Ĥ⟩ is correct when reports on the actual behavior that it sees --outermost H--17olcott
15 Mar 24 i  ii      +* Re: H ⟨Ĥ⟩ ⟨Ĥ⟩ is correct when reports on the actual behavior that it sees --outermost H--13Fred. Zwarts
15 Mar 24 i  ii      i`* Re: H ⟨Ĥ⟩ ⟨Ĥ⟩ is correct when reports on the actual behavior that it sees --outermost H--12olcott
15 Mar 24 i  ii      i +* Re: H ⟨Ĥ⟩ ⟨Ĥ⟩ is correct when reports on the actual behavior that it sees --outermost H--2Richard Damon
15 Mar 24 i  ii      i i`- Re: H(D,D)==0 is correct when reports on the actual behavior that it sees --outermost H--1olcott
15 Mar 24 i  ii      i `* Re: H ⟨Ĥ⟩ ⟨Ĥ⟩ is correct when reports on the actual behavior that it sees --outermost H--9immibis
15 Mar 24 i  ii      i  `* Re: H(D,D)==0 is correct when reports on the actual behavior that it sees --outermost H--8olcott
15 Mar 24 i  ii      i   +* Re: H(D,D)==0 is correct when reports on the actual behavior that it sees --outermost H--5immibis
15 Mar 24 i  ii      i   i`* Re: H(D,D)==0 is correct when reports on the actual behavior that it sees --outermost H--4olcott
15 Mar 24 i  ii      i   i `* Re: H(D,D)==0 is correct when reports on the actual behavior that it sees --outermost H--3immibis
15 Mar 24 i  ii      i   i  `* Re: H(D,D)==0 is correct when reports on the actual behavior that it sees --outermost H--2olcott
15 Mar 24 i  ii      i   i   `- Re: H(D,D)==0 is correct when reports on the actual behavior that it sees --outermost H--1immibis
15 Mar 24 i  ii      i   `* Re: H(D,D)==0 is correct when reports on the actual behavior that it sees --outermost H--2Richard Damon
15 Mar 24 i  ii      i    `- Re: H(D,D)==0 is correct when reports on the actual behavior that it sees --outermost H--1olcott
15 Mar 24 i  ii      `* Re: H ⟨Ĥ⟩ ⟨Ĥ⟩ is correct when reports on the actual behavior that it sees --outermost H--3immibis
15 Mar 24 i  ii       `* Re: H(D,D) ==0 is correct when reports on the actual behavior that it sees --outermost H--2olcott
15 Mar 24 i  ii        `- Re: H(D,D) ==0 is correct when reports on the actual behavior that it sees --outermost H--1immibis
8 Mar 24 i  i`* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)3Richard Damon
8 Mar 24 i  i `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)2immibis
8 Mar 24 i  i  `- Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)1olcott
8 Mar 24 i  `- Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)1olcott
8 Mar 24 `* Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)2immibis
8 Mar 24  `- Re: We finally know exactly how H1(D,D) derives a different result than H(D,D)1olcott

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal