|
|
|
|
|
|
by wat10000
460 days ago
|
|
|
Determinism is unrelated to correctness. Deterministic means the output depends only on the state you consider to be relevant, and not other factors. A stopped clock is deterministic: no matter what you do, it gives you the same output. A working, accurate clock is deterministic if you consider the current time to be a relevant piece of state, but not if you don't. Consider how "deterministic builds" need to avoid timestamping their build products, because determinism in that context is assumed to mean that you can run it at a different time and get the same result. LLMs can be deterministic if you run them with a temperature of 0 or a fixed random seed, and your kernel is built to be deterministic, but they're not typically used that way, and will produce different output for identical input. |
|
|
I never said it is. That's why I qualified my example with the word correct.
> no matter what you do, it gives you the same output
This is not deterministic. This is determined. I think this is the confusion I was pointing out.
>> Deterministic means that if it is accurate/correct once, it will continue to be in future runs (unless the correct answer changes; a stopped clock is deterministic).
The bit in the parenthesis, I am trying to argue, is nonsense. If the correct answer changes, the system is not accurate or correct to begin with so the point is moot. Correcting the system will make it accurate. A stopped clock is not deterministic, it's determined. As a time indicator, a stopped clock is not a correct, accurate or deterministic model at all under any possible interpretation.