Timeline for Can one force NMaximize to continue for a specified time?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 6, 2019 at 7:54 | comment | added | spaced | Thanks, I'm familiar with the tutorial. The optimizer needs to explore a fitness landscape that I suspect is very rough and discrete. There may be multiple maxima with the same fitness value. In some known cases I've tested, it quits before finding any of these maxima. I want it to keep looking indefinitely (hopefully more intelligently than a random search) and when it finds a maximum (sinceI know what it's fitness value will be - what I'm looking for are the optimal input values) it can then exit. | |
| Jun 6, 2019 at 7:41 | comment | added | Szabolcs | You'll find the list of available methods and their sub-options here: reference.wolfram.com/language/tutorial/… | |
| Jun 6, 2019 at 7:38 | comment | added | Szabolcs | Can you explain what you actually want to achieve? meta.stackexchange.com/q/66377/164803 | |
| Jun 6, 2019 at 4:35 | comment | added | march |
It doesn't really make sense to force it to compute for a certain amount of time, but you can force it do more iterations by adding the option MaxIterations -> 10000 or something.
|
|
| Jun 6, 2019 at 4:25 | review | Low quality posts | |||
| Jun 6, 2019 at 5:33 | |||||
| Jun 6, 2019 at 4:08 | history | asked | spaced | CC BY-SA 4.0 |