Skip to main content
replaced http://mathematica.stackexchange.com/ with https://mathematica.stackexchange.com/
Source Link

Update: This bug has been fixed in the just released Mathematica 11.1.


A good workaround was suggested by ilianilian.

For a workaround, please try Method -> "InteriorPoint".

This workaround worked for me. In particular, I can now run the first FindMinimum command for the code listing in my question as many times as I want, and the second FindMinimum command does not cause a crash either. Even better, the solution found with this option seems to be more accurate. I also did not notice a slow down when I applied this workaround to the original application.

Update: This bug has been fixed in the just released Mathematica 11.1.


A good workaround was suggested by ilian.

For a workaround, please try Method -> "InteriorPoint".

This workaround worked for me. In particular, I can now run the first FindMinimum command for the code listing in my question as many times as I want, and the second FindMinimum command does not cause a crash either. Even better, the solution found with this option seems to be more accurate. I also did not notice a slow down when I applied this workaround to the original application.

Update: This bug has been fixed in the just released Mathematica 11.1.


A good workaround was suggested by ilian.

For a workaround, please try Method -> "InteriorPoint".

This workaround worked for me. In particular, I can now run the first FindMinimum command for the code listing in my question as many times as I want, and the second FindMinimum command does not cause a crash either. Even better, the solution found with this option seems to be more accurate. I also did not notice a slow down when I applied this workaround to the original application.

added 174 characters in body
Source Link
ilian
  • 25.5k
  • 4
  • 117
  • 187

Update: This bug has been fixed in the just released Mathematica 11.1.


A good workaround was suggested by ilian.

For a workaround, please try Method -> "InteriorPoint".

This workaround worked for me. In particular, I can now run the first FindMinimum command for the code listing in my question as many times as I want, and the second FindMinimum command does not cause a crash either. Even better, the solution found with this option seems to be more accurate. I also did not notice a slow down when I applied this workaround to the original application.

A good workaround was suggested by ilian.

For a workaround, please try Method -> "InteriorPoint".

This workaround worked for me. In particular, I can now run the first FindMinimum command for the code listing in my question as many times as I want, and the second FindMinimum command does not cause a crash either. Even better, the solution found with this option seems to be more accurate. I also did not notice a slow down when I applied this workaround to the original application.

Update: This bug has been fixed in the just released Mathematica 11.1.


A good workaround was suggested by ilian.

For a workaround, please try Method -> "InteriorPoint".

This workaround worked for me. In particular, I can now run the first FindMinimum command for the code listing in my question as many times as I want, and the second FindMinimum command does not cause a crash either. Even better, the solution found with this option seems to be more accurate. I also did not notice a slow down when I applied this workaround to the original application.

Source Link
Brian Moths
  • 829
  • 5
  • 14

A good workaround was suggested by ilian.

For a workaround, please try Method -> "InteriorPoint".

This workaround worked for me. In particular, I can now run the first FindMinimum command for the code listing in my question as many times as I want, and the second FindMinimum command does not cause a crash either. Even better, the solution found with this option seems to be more accurate. I also did not notice a slow down when I applied this workaround to the original application.