monomi | provides tools for handling mobile | Runtime Evironment library

In an isympy session:

It looks like the b's are functions, that would be powers of x

This is due to the pretty-printer limiting how much it prints (to reduce voluminous output), not an internal limitation of z3.

You can raise the limit by adding the following line after from z3 import *:

You can return std::array/std::vector from functions/lambdas:

In your code, you're inserting a linebreak for every even-power monomial, except for the last one.

You can do this using Expr manipulation like:

1. The new BigDecimal(double) constructor is not something you generally want to be using; the whole reason BigDecimal exists in the first place is that double is wonky: There are almost 2^64 unique values that a double can represent, but that's it - (almost) 2^64 distinct values, smeared out logarithmically, with about a quarter of all available numbers between 0 and 1, a quarter from 1 to infinity, and the other half the same but as negative numbers. 3.14159265358979323846264 is not one of the blessed numbers. Use the string constructor instead - just toss " symbols around it.

2. every loop, sign should switch, well, sign. You're not doing that.

3. In the first loop, you overwrite x with x = x.abs().multiply(x.abs()).multiply(x).multiply(sign);, so now the 'x' value is actually -x^3, and the original x value is gone. Next loop, you repeat this process, and thus you definitely are nowhere near the desired effect. The solution - don't overwrite x. You need x, throughout the calculation. Make it final (getSin(final BigDecimal x) to help yourself.

Make another BigDecimal value and call it accumulator or what not. It starts out as a copy of x.

Every loop, you multiply x to it twice then toggle the sign. That way, the first time in the loop the accumulator is -x^3. The second time, it is x^5. The third time it is -x^7, and so on.

1. There is more wrong, but at some point I'm just feeding you your homework on a golden spoon.

I strongly suggest you learn to debug. Debugging is simple! All you really do, is follow along with the computer. You calculate by hand and double check that what you get (be it the result of an expression, or whether a while loop loops or not), matches what the computer gets. Check by using a debugger, or if you don't know how to do that, learn, and if you don't want to, add a ton of System.out.println statements as debugging aids. There where your expectations mismatch what the computer is doing? You found a bug. Probably one of many.

Then consider splicing parts of your code up so you can more easily check the computer's work.

For example, here, num is supposed to reflect:

• before first loop: x
• first loop: x - x^3/3!
• second loop: x - x^3/3! + x^5/5!

etcetera. But for debugging it'd be so much simpler if you have those parts separated out. You optimally want:

• first loop: 3 separated concepts: -1, x^3, and 3!.
• second loop: +1, x^5, and 5!.

That debugs so much simpler.

It also leads to cleaner code, generally, so I suggest you make these separate concepts as variables, describe them, write a loop and test that they are doing what you want (e.g. you use sysouts or a debugger to actually observe the power accumulator value hopping from x to x^3 to x^5 - this is easily checked), and finally put it all together.

This is a much better way to write code than to just 'write it all, run it, realize it doesn't work, shrug, raise an eyebrow, head over to stack overflow, and pray someone's crystal ball is having a good day and they see my question'.

in graph mode ,If you want to fill a tensor in a loop like a list,you can use TensorArray :

to 'initialise' e.g:

It's because you're not closing print function, one a close parenthesis at the end is missing. I suggest you to use some linter to debug and find warning and errors. The final code should be as below: