On 7/20/2025 6:11 AM, joes wrote:
Am Sat, 19 Jul 2025 16:36:42 -0500 schrieb olcott:
On 7/19/2025 4:26 PM, wij wrote:
On Sat, 2025-07-19 at 16:05 -0500, olcott wrote:
Not at all. The HP proof claims that DD correctly simulated by HHHDD correctly simulated by HHH cannot reach past the "if" statement
thus cannot reach the "return" statement.
That is roughly what HP proof says.
reaches the self-contradictory part of DD and thus forms a
contradiction.
No. It proves that the direct execution reaches the part that contra-
dicts HHH's return value.
<ChatGPT>
Misrepresentation of Input:
The standard proof assumes a decider
H(M,x) that determines whether machine
M halts on input x.
But this formulation is flawed, because:
Turing machines can only process finite
encodings (e.g. ⟨M⟩), not executable entities
like M.
So the valid formulation must be
H(⟨M⟩,x), where ⟨M⟩ is a string.
</ChatGPT>
On 7/20/25 10:33 AM, olcott wrote:
On 7/20/2025 6:11 AM, joes wrote:
Am Sat, 19 Jul 2025 16:36:42 -0500 schrieb olcott:
On 7/19/2025 4:26 PM, wij wrote:
On Sat, 2025-07-19 at 16:05 -0500, olcott wrote:
Not at all. The HP proof claims that DD correctly simulated by HHHDD correctly simulated by HHH cannot reach past the "if" statement >>>>>> thus cannot reach the "return" statement.
That is roughly what HP proof says.
reaches the self-contradictory part of DD and thus forms a
contradiction.
No. It proves that the direct execution reaches the part that contra-
dicts HHH's return value.
<ChatGPT>
Misrepresentation of Input:
The standard proof assumes a decider
H(M,x) that determines whether machine
M halts on input x.
But this formulation is flawed, because:
Turing machines can only process finite
encodings (e.g. ⟨M⟩), not executable entities
like M.
So the valid formulation must be
H(⟨M⟩,x), where ⟨M⟩ is a string.
</ChatGPT>
In other words, your explaination to Chat GPR was just in error, as the decider *IS* given the representation of the program M.
On 7/20/2025 2:57 AM, Fred. Zwarts wrote:
Op 19.jul.2025 om 21:19 schreef olcott:
On 7/19/2025 12:02 PM, Richard Damon wrote:
On 7/19/25 10:42 AM, olcott wrote:
On 7/18/2025 3:49 AM, joes wrote:
That is wrong. It is, as you say, very obvious that HHH cannot
simulate
DDD past the call to HHH. You just draw the wrong conclusion from it. >>>>>> (Aside: what "seems" to you will convince no one. You can just call >>>>>> everybody dishonest. Also, they are not "your reviewers".)
For the purposes of this discussion this is the
100% complete definition of HHH. It is the exact
same one that I give to all the chat bots.
Termination Analyzer HHH simulates its input until
it detects a non-terminating behavior pattern. When
HHH detects such a pattern it aborts its simulation
and returns 0.
So, the only HHH that meets your definition is the HHH that never
detects the pattern and aborts, and thus never returns.
All of the Chat bots conclude that HHH(DDD) is correct
to reject its input as non-halting because this input
specified recursive simulation. They figure this out
on their own without any prompting.
https://chatgpt.com/share/687aa4c2-b814-8011-9e7d-b85c03b291eb
I just read a news item where an AI told that bread with shit is a
nice desert. So, we know what a proof by AI means.
That would be a detectable error.
There is no detectable error in the above link
pertaining to the correct return value of HHH(DDD).
On 7/20/2025 5:11 PM, Richard Damon wrote:
On 7/20/25 10:33 AM, olcott wrote:
On 7/20/2025 6:11 AM, joes wrote:
Am Sat, 19 Jul 2025 16:36:42 -0500 schrieb olcott:
On 7/19/2025 4:26 PM, wij wrote:
On Sat, 2025-07-19 at 16:05 -0500, olcott wrote:
Not at all. The HP proof claims that DD correctly simulated by HHHDD correctly simulated by HHH cannot reach past the "if" statement >>>>>>> thus cannot reach the "return" statement.
That is roughly what HP proof says.
reaches the self-contradictory part of DD and thus forms a
contradiction.
No. It proves that the direct execution reaches the part that contra-
dicts HHH's return value.
<ChatGPT>
Misrepresentation of Input:
The standard proof assumes a decider
H(M,x) that determines whether machine
M halts on input x.
But this formulation is flawed, because:
Turing machines can only process finite
encodings (e.g. ⟨M⟩), not executable entities
like M.
So the valid formulation must be
H(⟨M⟩,x), where ⟨M⟩ is a string.
</ChatGPT>
In other words, your explaination to Chat GPR was just in error, as
the decider *IS* given the representation of the program M.
H(M,x) is wrong and H(⟨M⟩,x) is correct.
You must actually pay attention or you miss
important details.
On 7/20/2025 2:57 AM, Fred. Zwarts wrote:
Op 19.jul.2025 om 21:19 schreef olcott:
On 7/19/2025 12:02 PM, Richard Damon wrote:
On 7/19/25 10:42 AM, olcott wrote:
On 7/18/2025 3:49 AM, joes wrote:
That is wrong. It is, as you say, very obvious that HHH cannot
simulate
DDD past the call to HHH. You just draw the wrong conclusion from it. >>>>>> (Aside: what "seems" to you will convince no one. You can just call >>>>>> everybody dishonest. Also, they are not "your reviewers".)
For the purposes of this discussion this is the
100% complete definition of HHH. It is the exact
same one that I give to all the chat bots.
Termination Analyzer HHH simulates its input until
it detects a non-terminating behavior pattern. When
HHH detects such a pattern it aborts its simulation
and returns 0.
So, the only HHH that meets your definition is the HHH that never
detects the pattern and aborts, and thus never returns.
All of the Chat bots conclude that HHH(DDD) is correct
to reject its input as non-halting because this input
specified recursive simulation. They figure this out
on their own without any prompting.
https://chatgpt.com/share/687aa4c2-b814-8011-9e7d-b85c03b291eb
I just read a news item where an AI told that bread with shit is a
nice desert. So, we know what a proof by AI means.
That would be a detectable error.
There is no detectable error in the above link
pertaining to the correct return value of HHH(DDD).
On 7/21/2025 3:38 AM, Fred. Zwarts wrote:
Op 20.jul.2025 om 17:18 schreef olcott:
On 7/20/2025 2:57 AM, Fred. Zwarts wrote:
Op 19.jul.2025 om 21:19 schreef olcott:
On 7/19/2025 12:02 PM, Richard Damon wrote:
On 7/19/25 10:42 AM, olcott wrote:
On 7/18/2025 3:49 AM, joes wrote:
That is wrong. It is, as you say, very obvious that HHH cannot >>>>>>>> simulate
DDD past the call to HHH. You just draw the wrong conclusion
from it.
(Aside: what "seems" to you will convince no one. You can just call >>>>>>>> everybody dishonest. Also, they are not "your reviewers".)
For the purposes of this discussion this is the
100% complete definition of HHH. It is the exact
same one that I give to all the chat bots.
Termination Analyzer HHH simulates its input until
it detects a non-terminating behavior pattern. When
HHH detects such a pattern it aborts its simulation
and returns 0.
So, the only HHH that meets your definition is the HHH that never >>>>>> detects the pattern and aborts, and thus never returns.
All of the Chat bots conclude that HHH(DDD) is correct
to reject its input as non-halting because this input
specified recursive simulation. They figure this out
on their own without any prompting.
https://chatgpt.com/share/687aa4c2-b814-8011-9e7d-b85c03b291eb
I just read a news item where an AI told that bread with shit is a
nice desert. So, we know what a proof by AI means.
That would be a detectable error.
There is no detectable error in the above link
pertaining to the correct return value of HHH(DDD).
Errors have been detected in the input for the chat-box and pointed
out to you.
E.g., that ' HHH simulates its input until it detects a non-
terminating behaviour pattern' contradicts 'When HHH detects such a
pattern it aborts its simulation and returns 0'.
void Infinite_Recursion()
{
Infinite_Recursion();
}
void Infinite_Loop()
{
HERE: goto HERE;
return;
}
<sarcasm>
Sure and we know that you are correct because the
correct simulation of Infinite_Recursion() and
Infinite_Loop() would eventually reach their "return"
statement and terminate normally if we just wait
long enough.
</sarcasm>
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 1,064 |
Nodes: | 10 (0 / 10) |
Uptime: | 150:04:17 |
Calls: | 13,691 |
Calls today: | 1 |
Files: | 186,936 |
D/L today: |
438 files (115M bytes) |
Messages: | 2,410,972 |