-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Settings for BigFloat #105
Comments
You are correct that the solver uses the same default settings regardless of the precision of the underlying data type. It is difficult to give numbers that will work in all cases, particularly given that the Julia BigFloat has user-definable precision. That said, I can at least make some suggestions. All of the parameters are listed here: https://oxfordcontrol.github.io/ClarabelDocs/stable/api_settings/ As a starting point, I would suggest setting all of the parameters with names like A similar comment should hold for the I would start like that. If you don't get good convergence, the next tolerance to tighten would be Unless you get really weird behaviour for your problem, or your problem is very badly scaled or something, I would be inclined to leave everything else as it is. You didn't ask this, but for anyone finding this in the future: for Float32 types, a reasonable starting point would be to take the square root of the default values for all parameters named above, leaving everything else unchanged. |
It seems that the Settings for
BigFloat
are the same as those (tolerances etc) ofFloat64
.What sets of settings for
BigFloat
do you recommend? We need a stringent one as we have more digits involvedThe text was updated successfully, but these errors were encountered: