Jason K. Moore
Jason K. Moore
We use `latex_to_png()` in here: https://github.com/sympy/sympy/blob/master/sympy/interactive/printing.py#L113, maybe that is helpful. The scale may bump the DPI, not sure though.
Yes, basically there will be an upper limit of examples we can include as the times all add up. It is always helpful to redeuce their running time.
If the user sets bounds on the trajectories, those could be used to make some scaling rules because the max/min of each state would be known.
There is some general rule for keeping objective and constraint values small, but here is the basic documentation: https://coin-or.github.io/Ipopt/OPTIONS.html#OPT_NLP_Scaling and it ties to applying scaling to the internal linear solve...
Tips on scaling: https://github.com/coin-or/Ipopt/discussions/498#discussioncomment-1002700
From intel build: ``` Run python examples/parallel_example.py clang: error: unsupported option '-fopenmp' /Users/runner/miniconda3/envs/test/lib/python3.10/site-packages/opty/utils.py:572: UserWarning: openmp is not installed or not working properly, request for parallel execution ignored. warnings.warn(msg) Time for...
A related issue is that the CSE variables don't have the assumptions of the expressions they replace. See #216 for related info.
Yes, but this may need more thought than I've explained here. I recall thinking the fix isn't so simple. That's why I didn't pursue.
Yes, this is a bit deeper issue: https://github.com/csu-hmc/opty/issues/215#issuecomment-2320003714