On 2/29/2024 8:24 PM, Richard Damon wrote:
On 2/29/24 5:13 PM, olcott wrote:
On 2/29/2024 4:06 PM, wij wrote:
On Thu, 2024-02-29 at 15:59 -0600, olcott wrote:
On 2/29/2024 3:50 PM, wij wrote:
On Thu, 2024-02-29 at 15:27 -0600, olcott wrote:
On 2/29/2024 3:15 PM, wij wrote:
On Thu, 2024-02-29 at 15:07 -0600, olcott wrote:
On 2/29/2024 3:00 PM, wij wrote:
On Thu, 2024-02-29 at 14:51 -0600, olcott wrote:
On 2/29/2024 2:48 PM, wij wrote:
On Thu, 2024-02-29 at 13:46 -0600, olcott wrote:
On 2/29/2024 1:37 PM, Mikko wrote:
On 2024-02-29 15:51:56 +0000, olcott said:
H ⟨Ĥ⟩ ⟨Ĥ⟩ (in a separate memory space) merely needs to
report on
A Turing machine is not in any memory space.
That no memory space is specified because Turing machines >>>>>>>>>>>>> are imaginary fictions does not entail that they have no >>>>>>>>>>>>> memory space. The actual memory space of actual Turing >>>>>>>>>>>>> machines is the human memory where these ideas are located. >>>>>>>>>>>>>
The entire notion of undecidability when it depends on >>>>>>>>>>>>> epistemological antinomies is incoherent.
People that learn these things by rote never notice this. >>>>>>>>>>>>> Philosophers that examine these things looking for
incoherence find it.
...14 Every epistemological antinomy can likewise be used >>>>>>>>>>>>> for a similar undecidability proof...(Gödel 1931:43) >>>>>>>>>>>>>
So, do you agree what GUR says?
People believes GUR. Why struggle so painfully, playing >>>>>>>>>>>> idiot everyday ?
Give in, my friend.
Graphical User Robots?
The survival of the species depends on a correct
understanding of truth.
People believes GUR are going to survive.
People does not believe GUR are going to vanish.
What the Hell is GUR ?
Selective memory?
https://groups.google.com/g/comp.theory/c/_tbCYyMox9M/m/XgvkLGOQAwAJ >>>>>>>>
Basically, GUR says that no one even your god can defy that HP >>>>>>>> is undecidable.
I simplify that down to this.
...14 Every epistemological antinomy can likewise be used for
a similar undecidability proof...(Gödel 1931:43)
The general notion of decision problem undecidability is
fundamentally
flawed in all of those cases where a decider is required to
correctly
answer a self-contradictory (thus incorrect) question.
When we account for this then epistemological antinomies are always >>>>>>> excluded from the domain of every decision problem making all of >>>>>>> these decision problems decidable.
It seems you try to change what the halting problem again.
https://en.wikipedia.org/wiki/Halting_problem
In computability theory, the halting problem is the problem of
determining, from a description of
an
arbitrary computer program and an input, whether the program will
finish running, or continue to
run
forever....
This wiki definition had been shown many times. But, since your
English is
terrible, you often read it as something else (actually, deliberately >>>>>> interpreted it differently, so called 'lie')
If you want to refute Halting Problem, you must first understand
what the
problem is about, right? You never hit the target that every one
can see, but POOP.
Note: My email was delivered strangely. It swapped to sci.logic !!!
If we have the decision problem that no one can answer this question: >>>>> Is this sentence true or false: "What time is it?"
This is not the halting problem.
Someone has to point out that there is something wrong with it.
This is another problem (not the HP neither)
The halting problem is one of many problems that is
only "undecidable" because the notion of decidability
incorrectly requires a correct answer to a self-contradictory
(thus incorrect) question.
The question itself is NOT self-contradictory, but EVERY instance of
the question has a correct answer, just not the one the decider the
input is contradictory to give.
Note, you are a bit on the right track, one of the causes of this
uncomputability is the ability of the system to support the making of
an input that is decider-contrary. IF there was something about the
decider that the input couldn't do, then this common method would break.
The key point is that all these logic system have become powerful
enough with the axioms to support the ability to produce such a result.
And that is one way to keep systemms for becoming incomplete, limit
the power of the expression that you allow in the system.
The simple way around this is to understand that
self-contradictory inputs are invalid.
I think that you already agreed with this:
LP = "This sentence is not true."
Boolean True(English, LP) is false
Boolean True(English, ~LP) is false
*You probably did not understand that the above refutes Tarski*
The simple way around this is to understand that
self-contradictory inputs are invalid.
On 3/5/2024 3:59 AM, Mikko wrote:
On 2024-03-04 16:53:10 +0000, olcott said:
On 3/4/2024 8:46 AM, Mikko wrote:
On 2024-03-02 18:06:01 +0000, olcott said:
On 3/2/2024 5:24 AM, Mikko wrote:
On 2024-03-01 17:09:46 +0000, olcott said:
On 3/1/2024 5:27 AM, Mikko wrote:
On 2024-03-01 03:32:44 +0000, olcott said:
The simple way around this is to understand that
self-contradictory inputs are invalid.
They are not unless the problem statements say so. What is or is >>>>>>>> not a valid input is specified in the problem statement. Your
opinions don't matter.
The correct philosophical foundation of the notion of truth
itself proves that epistemological antinomies have no truth
value because they are not truth bearers proves that they are
outside of the domain of decision problems.
That does not contradict what I said above.
Yes it does. it is generically the case that every input
to a decision problem either has a correct yes/no answer
or this input is outside of the domain of this decider.
No, it doesn't. It is generically the case that the domain
is what the problem specification says. If you leave anything
out of the domain you will have at most a partial solution,
not the solution of the problem.
I have reversed my position on this.
Have you already updated your web page?
I have many papers on Researchgate here is my most recent one: https://www.researchgate.net/publication/374806722_Does_the_halting_problem_place_an_actual_limit_on_computation
Termination Analyzer H is Not Fooled by Pathological Input D https://www.researchgate.net/publication/369971402_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D
I may update that one with the algorithm suggested by Mike
and anchor it better in the Linz Halting problem proof.
The key most important discovery is that it is the combination
of H/D that forms the single counter-example input to H1.
Ĥ.q0 ⟨Ĥ⟩ ⊢* Ĥ.Hq0 ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.Hqy ∞ // Ĥ applied to ⟨Ĥ⟩ halts
Ĥ.q0 ⟨Ĥ⟩ ⊢* Ĥ.Hq0 ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.Hqn // Ĥ applied to ⟨Ĥ⟩ does not halt
In other words H/D is isomorphic to Linz Ĥ and H1 is
isomorphic to Linz H. Actual Turing machines do not
call other Turing Machines instead they embed these
machines within themselves. That most texts on the
halting problem have D calling H lead me astray for
may years.
Because of this I reversed my position and no longer claim
that H(D,D) reports on the behavior specified by its input
(it does, but this is unconventional). When it is construed
that H must report on the behavior of the direct execution
of its input it does get the wrong answer yet only because
the combination of H/D is self-contradictory.
In other words the halting problem only proves that an
otherwise correct halt decider H can be caused to report
incorrectly by embedding it as Ĥ.Hq0 in another machine
Ĥ that contradicts every value that it returns.
That this has no actual effect on the original H is
apparently too difficult for many people to understand.
It is as easy as first grade arithmetic to me because
I fully understand all of the details of how this works.
My H1(D,D) machine versus my H(D,D) machine conclusively
proves that when two otherwise identical machine are
at different locations in memory then when each is applied
to the same input they can correctly derived different results.
They correctly derive different results because these machine
are at different locations in memory only one of these two machines
has its return value contradicted and the other does not.
People that disagree with this are disagreeing with empirically
verified facts. The x86 execution race clearly proves that H(D,D)
does meet its "abort simulation" criteria and H1(D,D) does not
meet this criteria.
Ĥ.q0 ⟨Ĥ⟩ ⊢* Ĥ.Hq0 ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.Hqy ∞ // Ĥ applied to ⟨Ĥ⟩ halts
Ĥ.q0 ⟨Ĥ⟩ ⊢* Ĥ.Hq0 ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.Hqn // Ĥ applied to ⟨Ĥ⟩ does not halt
Richard has agreed that Ĥ.H must transition to Ĥ.Hqn
to prevent its own infinite execution and this causes
Ĥ to halt.
*This entails that H ⟨Ĥ⟩ ⟨Ĥ⟩ would be correct to transition to H.qy*
So I have shown that a correct halt status for the counter-example
input <is> possible and Richard's last remaining rebuttal to this
is that he doesn't think that H is is smart enough to do this.
*When H ⟨Ĥ⟩ ⟨Ĥ⟩ uses the exact same criteria as Ĥ.H*
Both H and Ĥ.H transition to their NO state when a correct and
complete simulation of their input would cause their own infinite
execution and otherwise transition to their YES state.
When they both apply this criteria correctly then
Ĥ.H ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to NO and H ⟨Ĥ⟩ ⟨Ĥ⟩ transitions to YES.
Simply not believing that they can do this is not really
any actual rebuttal at all.
I have reversed my position on this.
Have you already updated your web page?
I have many papers on Researchgate here is my most recent one: https://www.researchgate.net/publication/374806722_Does_the_halting_problem_place_an_actual_limit_on_computation
Termination Analyzer H is Not Fooled by Pathological Input D https://www.researchgate.net/publication/369971402_Termination_Analyzer_H_is_Not_Fooled_by_Pathological_Input_D
I may update that one with the algorithm suggested by Mike
and anchor it better in the Linz Halting problem proof.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 307 |
Nodes: | 16 (2 / 14) |
Uptime: | 45:54:30 |
Calls: | 6,910 |
Files: | 12,377 |
Messages: | 5,429,452 |