Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

latex() printing bugs

See original GitHub issue

Noticed a few latex bugs. In order of perceived ease of fixing:

Controlpanel printing should be modularized (moved to #885)
The opening line of the latex string should be \begin{array}{ll} instead of \begin{array}[ll] (http://latex.wikia.com/wiki/Array_(LaTeX_environment))
Some constraints and objectives are followed by the units of the objective/constraint in square brackets whereas other aren’t
Currently the latex environment chosen does not support multi-page models, which is a problem for larger models. This might be best resolved by using a different environment (e.g. align). (now in #949)
Making seemingly innocuous changes will toggle on/off the MODELNAME part of a variable name. e.g. I changed one of my variable strings from Wpp to W\'\' and suddenly all of my variables have subscript Fuselage appended to them.
M. Drela suggests putting a small space between variables in monomials, if there is no exponent taking up space. This probably isn’t specific to the latex() method but that’s just where I noticed it. (now in #949)
modelname is printed in latex output (and controlpanel sliders!), even when all variables come from the same model, which is distracting (now #780)
latex for merged models gets very long, making latex difficult to read and controlpanel difficult to use
latex for some unit strings underscores letters after underscores. ex: pound_force_per_square_inch (now in #949)