math

See this issue sympy/sympy#11044 . That issue was fixed in PR sympy/sympy#11566. Though no test case was added for the lambdify.

What needs to be done?

Add test case that this works just fine:

>>> from sympy import MatrixSymbol, lambdify
>>> x = MatrixSymbol('x', 3, 1)
>>> f = lambdify(x, x.T*x)

Test case needs to

Enhancement proposal

Currently, Dot3D uses the default Sphere resolution of (12, 24). Running a scene with lots of Dot3Ds, like a scene with polyhedra, takes incredibly long because of the high resolution. I think a resolution of (8, 8) is a good balance between speed and visual looks. After changing the resolution, the control data for some tests have to be regenerated.

Addition

Generated cpp code appears to assign results of multiple solutions to the same "argument" variable, and uses undeclared th_1, th_2, th_3 (etc) variables in solution calculations. The code won't compile, and is unusable.

The generated python code doesn't appear to have these issues.

My robot definition:

    if(name == 'Flexo'):
       # standardize on the order "alpha N-1, a N-1, d N, 

Currently, we are having readthedocs.org build the documentation for each PR and, if there are any warnings, the build fails immediately. This is a good thing, because it ensures that every PR is generating good documentation, including running the examples.

As discussed in #271, it would be nice to be able to see all of the warnings for the doc build instead of failing on the first one. B