Timeline for NMaximize and Conditional Loop
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 8, 2021 at 2:21 | history | edited | xzczd♦ |
edited tags
|
|
| Aug 1, 2013 at 18:04 | comment | added | Daniel Lichtblau | @xzczd I had missed that. Would be better to make it a vector, say, or an explicit function. | |
| Aug 1, 2013 at 8:37 | history | edited | image_doctor | CC BY-SA 3.0 |
Correct title spelling
|
| Aug 1, 2013 at 6:01 | answer | added | xzczd♦ | timeline score: 1 | |
| Aug 1, 2013 at 5:54 | comment | added | xzczd♦ |
@DanielLichtblau But in this sample, a is only a Head…
|
|
| Aug 1, 2013 at 5:50 | comment | added | Daniel Lichtblau |
Possibly NMaximize will be less inclined to sulk if the function is a "black box", that is, only evaluating for explicitly numeric arguments. That can be attained via e.g. f[a_?NumberQ] := ...
|
|
| Aug 1, 2013 at 4:43 | history | edited | m_goldberg | CC BY-SA 3.0 |
Improved formatting
|
| Aug 1, 2013 at 2:42 | review | First posts | |||
| Aug 1, 2013 at 4:43 | |||||
| Aug 1, 2013 at 2:24 | history | asked | dixontw | CC BY-SA 3.0 |