gunnarmein-ts

I think internal representation as fractions is not necessarily a bad thing. Converting a number to a text decimal, and then trying to find a close fitting fraction is the...

To your second point, it is not simplify() that does that, it is simply how Nerdamer represents numbers internally. .text("decimals") or simply .text() is your friend if that is what...

Also, if you want functions like sqrt(2) evaluated, you need to say "evaluate()". I agree with the concept of keeping things symbolic as long as one can.

What you put into WolframAlpha there is a+ the set {1,2,3}. Adding "a" to a vector in the way you do makes no sense: if a is a scalar, then...

Hmm. How to proceed should be to allow vectors in symbolic computation, no? `nerdamer("solve([a+2,1=[4,1],a)").toString()` should work as easily as `nerdamer("solve(a+2=4,a)").toString()` and (reaching here): `nerdamer("solve(a+vector(1,2,3)=vector(2,3,4),a)")` should figure out that a=[1,1,1] But...

Michael, I have also stumbled about inconsistencies with .solveFor() - but the good news is you can use `nerdamer('solve(y=(1/2)*a*b^2*c^(-2),y)')` instead. Works better in every case I know.

Here is a slightly simpler case: nerdamer("simplify(sqrt(2a+2b))").text() ===> '2*sqrt(a+b)'

Martin, here is a proposed fix in Algebra.js mfactor (quote starts line 3017) ` var factors2 = new Factors(), arg = __.Factor.common(symbol.args[0].clone(), factors2); // factors are put into factors2 here...

[Algebra.js.zip](https://github.com/jiggzson/nerdamer/files/7997185/Algebra.js.zip)

@rkanumola are you loading the iframe from the same location as the container doc?