C_R

3412 Reputation

21 Badges

5 years, 311 days

MaplePrimes Activity


These are replies submitted by C_R

@Carl Love 

I requested a new password and could now validate a new email. 

 

Dear MapleSim product management,

thank you for expanding basic functionalities and not making them an extra package.

MapleSim is easy to use. In this sense highlevel components for off-shelf components add to usabiliy. 

I also agree with what has been said by @WhiteNoise about general purpose components for signal generation.

And, if I may add, don't forget about digital signal processing that is used in everyday products. 

@Carl Love 

Makes sense but I think nowadays spammers automate their work which means that there is no huge gain in using an existing account.

I will try again after a while. Maybe there is a timer or something that identifies an account as non-spam.

Looks like that I have been too naive when choosing an old account that I want to keep.

@Carl Love 

Interesting workaroud!

Will that flagging as spam also flag the email I have used as spam address?

@WhiteNoise 

Thank you for clarifying.

If the realFFT is not running why would MapleSoft list it in the code editor?

I understand that components like digital controllers are not listed because they are not working out of the box.

But listing a componet that does not run in MapleSim does not make sense to me. Do you have an explanation for that?

@WD0HHU @Rouben Rostamian

I use Maple 2025.1 for Screen Readers which has the former GUI. IMO for Screen Readers is a missnomer.

After a system update (2 days after migration... no comment) Window 11 scales the Maple 2025.1 window as expected: The title bar and the status bar are visible.

Windows key + left arrow/rigth arrow still do not work as with Maple Screen Reader 2025 and former versions.

@Scot Gould 

The screen shot above was taken from the top of the screen to the bottom. The task bar and the status bar were clipped off. Therefore I could not drag the window to do what @janhardo suggested. Only lateral sizing is possible.

@Preben Alsholm 

I got 2025.1 when I installed MapleSim 2025 yesterday. Testing the interrupt was the frist I wanted to try with your worksheet. I assume now that Windows uses wrong parameters to size the Maple window. I have to reset this somehow. I will send an update A.S.A.P. when I get access to the button.

Update @Preben Alsholm :

Interrupt works for ifactor but not for your worksheet.

@Carl Love 

dsolve is easy to use since it can determine the dependend variable. From the ICs, in this case, it was clear to me what the ODE should be solved for. 
I was wondering why Maple does not solve the problem or at least issues a warning that more information is required?

My initial conclusion was the same that Maple cannot solve the problem. 

@Carl Love 

!!!

Could an attentive documentation reader find the small correction themselves?

Appart from bugs, the GUI is not finished yet. Example

Icons to expand a collapse panels (in red) are not harmonized. The grey horizontal bar (highlighted in yellow) is still in use for animation controls

It looks to me that this is a remnant of the former (very handy!!!) tool bar

Quick access buttons and tool bars of the legacy GUI provided better flow and higher productivity. Right now, with the new GUI, it is hoped that new users become faster productive. Old users notice a setback in productivity because of too many clicks and mouse movements.
I expect Maplesoft to add customization in future versions, because all other ribbon applications I know have that and also because Maplesoft uses Maple themselves. Slowing down own staff for a manyear more of GUI developement does not make sense. 

Until then I use the screen reader version of 2025.

 

The error message is caused by Maples integration algorithm that calls the subroutine int/hermiter/horowitzLog 

with an inappropriate argument. This is not your fault. You can try to follow what int does by entering

infolevel[int]:=3;# up to 5 for more details

The integral is not trivial. To make solutions possible sometimes assumptions can help. I tried

int(G, [xi = 0 .. infinity, eta = 0 .. 1]) assuming (0 < omega, 0 < b, 0 < x)

which lets the error message dissappear without returning immediate a result. Maple is buisy filling the memory in the background by investigating cases of possible solutions. The possible parameter ranges and their relationship (see subexpressions in the integrant where more than one parameter appears) required this. If you know a case for parameters with fixed values that should return a solution you could give it a try. If that does not work, I am affraid, Maple cannot provide a solution.

@Rouben Rostamian  

and very instructive. I see your point that for a given rotation axis first two more (Euler) angles must be determined before a rotation can be performed (proivided that the right rotation matrix is used with the correct sign of the angles).

Maple should have this easy way of rotation built-in.

Thank you

Interestingly the help page of simplify does not define what a simple expresion is.

It could be that simplify does not consider changing the argument of trig functions.

I would have expected simplify,size to do this because here the user input is clear about what kind of simple is wanted.

There might be expressions where simplify,size calling combine automatically would exclude other possible simplifications an expert could desire and for this reason it did not work.

Just a guess...

1 2 3 4 5 6 7 Last Page 1 of 67