Timeline for Determining the value at which a function becomes non-real or undefined
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 9, 2016 at 12:44 | comment | added | AnInquiringMind | Just a quick follow-up: I have had some success in implementing this method for my specific needs by using a modified function that cleans up any function messiness after it becomes (or, in theory, should become) non-real; however, I cannot get NMaximize to give me an answer closer to the upper bound than to 3 degrees of precision, even if I've tried to increase PrecisionGoal or AccuracyGoal. Not sure if there's a way to improve that. | |
| Jun 9, 2016 at 2:47 | comment | added | AnInquiringMind |
Thanks for the response! I'm trying to get this to work for my specific cases, but I think I'm running into some issues because the constraints that I need implement functions that use FindRoot and, thus, I've had to define those functions with an argument of the form x_?NumericQ. I think NMaximize is running into issues because x is not given as a number...
|
|
| Jun 8, 2016 at 22:40 | review | Low quality posts | |||
| Jun 8, 2016 at 23:14 | |||||
| Jun 8, 2016 at 22:18 | history | answered | mikado | CC BY-SA 3.0 |