Jarekkk

439 Reputation

13 Badges

14 years, 223 days

MaplePrimes Activity


These are replies submitted by Jarekkk

@Markiyan Hirnyk Yes, of course. I tried to search for it on MaplePrimes to add an original link, but couldn't find it. Sorry.

@pagan w has to be in the first quadrant, i.e. positive both real and imaginary part

@pagan w has to be in the first quadrant, i.e. positive both real and imaginary part

Yes, you're right. When I copied/pasted it I forgot this line:

y := Vector([[1, 1, 1, 1, 1, 1, 1, 1]]):

So I added it to the code I wrote before.

Yes, you're right. When I copied/pasted it I forgot this line:

y := Vector([[1, 1, 1, 1, 1, 1, 1, 1]]):

So I added it to the code I wrote before.

What is u? There is nothing assigned to it.

This is because of these two equalities (should be changed to assignments):

It does work. You typed pi which is just for the symbol. You have to type Pi (with big first letter) to have its value.

It does work. You typed pi which is just for the symbol. You have to type Pi (with big first letter) to have its value.

There seems to be a problem that after loading a Units[Natural] (or a Units[Standard]) package it is not possible to assign a value to the MathContainer.

If you insist on using one of those packages, then you can do some kind of workaround that you load the package, perform the tasks you want to perform with it, unload the package and then you assign a value to the MathContainer. In your example the code in Action when value changes of the slider component can look like:

alpha:=Do(%Slider0(value)):

use Units[Natural] in
beta:=Do(cos(alpha*deg)) end use:

Do(%MathContainer0=beta)

There seems to be a problem that after loading a Units[Natural] (or a Units[Standard]) package it is not possible to assign a value to the MathContainer.

If you insist on using one of those packages, then you can do some kind of workaround that you load the package, perform the tasks you want to perform with it, unload the package and then you assign a value to the MathContainer. In your example the code in Action when value changes of the slider component can look like:

alpha:=Do(%Slider0(value)):

use Units[Natural] in
beta:=Do(cos(alpha*deg)) end use:

Do(%MathContainer0=beta)

@acer Thank you. Now, it behaves how I expected before. :) With evalhf even the computation of Matrix values is significantly faster than in Excel.

@acer Thank you. Now, it behaves how I expected before. :) With evalhf even the computation of Matrix values is significantly faster than in Excel.

@Ronan I am sorry. I made a mistake. I haven't looked carefully to the indices and thought that they are the same. But they aren't! So, this is OK!

However, the equation which causes that no solution is found by solve command is this one:

It is placed after the equation with g[2003]. Sorry again for mystification.

@Ronan I am sorry. I made a mistake. I haven't looked carefully to the indices and thought that they are the same. But they aren't! So, this is OK!

However, the equation which causes that no solution is found by solve command is this one:

It is placed after the equation with g[2003]. Sorry again for mystification.

3 4 5 6 7 8 9 Last Page 5 of 15