See #23 - it's probably best to let users decide what performance/precision balance is best for them.
Should probably do this for both integrate.quadrature and optimize.brenth calls with two separate flags, since I think both of these can lead to the warnings in question. Note that this will require a version bump on both this package and betarat since the latter currently does not expose maxiter for the integration.
See #23 - it's probably best to let users decide what performance/precision balance is best for them.
Should probably do this for both
integrate.quadratureandoptimize.brenthcalls with two separate flags, since I think both of these can lead to the warnings in question. Note that this will require a version bump on both this package andbetaratsince the latter currently does not exposemaxiterfor the integration.