Open PavelBal opened 7 years ago
Could you explain what non-solvable
start values mean? I don't understand the issue that you are facing
The observed behavior is that the first evaluation of the run(s) is not possible - "RHS not finite" or something similar - and no start error can be calculated. Therefore, the run stops before performing any optimization.
My interpretation of this is that the particular set of the chosen parameter values leads to numerical problems in solving the simulation.
@PavelBal ok understood. This change in the workflow will be quite hard to implement as the runs are "run" in parallel so intercepting the behavior to add more runs would be tricky.
In your case I would suggest the following
I would not automatically replace runs with invalid start values:
If a run with random start values fails because of non-solvable start values, a new set of values should be tried out. To aviod endless trials, the user should be able to define the maximal amount of start values sets per run (e.g. 100).
As an example, out of 100 created runs in my PI, only two are running, and the rest failed at creation.