Talk:Simulated annealing: Difference between revisions
m
→k
m (→k) |
m (→k) |
||
Line 28:
: I am pretty sure you mean the 'k' which is described in the task description at the top of the page, and not the language k. But, for a start, please take a look at the top of the page and see if that addresses your concerns... --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 21:33, 29 September 2019 (UTC)
: After thinking about this further (and trying to address Peter E's concerns), it looks like this issue resides in the original draft of the linked wikipedia page (and persists in the current pseudocode).
: Quoting the current wikipedia page: "The annealing schedule is defined by the call temperature(r), which should yield the temperature to use, given the fraction r of the time budget that has been expended so far." This might suggest that k in the ratio k/kMax starts at kMax and falls to 0, but the pseudocode explicitly states the opposite.
: For compatibility with the pseudocode, we've used the expression (1-k/kMax) for r, instead of a simple ratio and made the function temperature(r) be kT*r where kT is 1...
: Of course, we could have used any of a variety of other expressions for the temperature function, and the cooling aspect does not specifically have to be encoded into r. So -- with an overly narrow focus -- it's easy to argue that the existing approach is "just fine".
: But it's also fair to be confused by the current approach, and to ask questions about it... --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 16:03, 30 September 2019 (UTC)
| |||