@Anthrazit If you can reproduce it: Do you see a dependence when you change the dpi settings (e.g. changing the monitor)?

I am asking because I have rendering issues when I switch monitors. It could be Windows related and may depend on compatibility settings of the program.

It seems that this test case is very challenging since the analytical solution oscillates and loops back to zero. 

A force applied at the free end of the beam instead of a momentum is probably more forgiving. Loops are not possible, and the leaver arm decreases with the deflection. Unless for this new test case someone can come up with analytical or PDE solutions, verified FEM code (which I do not have access to) could be used to confirm this guess.  

For planar models: Modifying the default settings of the flexible beam compoent in the example by setting the elastic coordinate in z direction to zero will speed up the calculation (about a factor of 10 in the example with the segmented beam). This will half the number of generalized coordinates the solver has to deal with. 

Likewise, increasing the elastic coordinates will increase the number of generalized coordinates.  

@vv Works. Thank you!

@Rouben Rostamian  

Thank you for the code. It’s very instructive and much leaner than I did expect.

Could you check this code line?

Disk := plot3d(0, r=0..R, t=0..2*Pi, coords=z_cylindrical, color=col0):

With Maple 2021 I get an error message.

Error, (in plot3d) cannot convert to coordinate system: z_cylindrical

@acer is not so bad at all.

Thank you!

of a currently opened help page.

Such a string could than be pasted, for example, in the target field of the Hyperlink properties dialogue.

I had hoped that in the new release this feature would also be available for visualitsation components of MapleSim standard libraray.

I hope that visualization of rotation of spheres, cylinders and disks will be possible one day. If possible in combination with the new and very useful scaling feature.

Could you share details how you have done it?

@epostma 

Carl's solution (with an initial simplification to SI units) worked and I am fine with it.
What didn't work was the solution from tomleslie 9664 . For that one I prepared the simplified example which did not work either with the construct convert, simplify~(U.....
he proposed.
It's becomming now more a question about Maple syntax. I don't want to waist your time byond my initial request.

Thank you all!

@Carl Love 

Actually, I tried to update my worksheet with the nested commands as proposed, and it did not work.

If I interpret the execution of convert,unit_free (as I have used it in my original worksheet) correctly, it works on the operands of a sum. Wherever an operand is a product of a Unit and "something else" it strips of the unit. It does not seem to work on functions. Here is another example

Download convert_unit_free.mw

Have I overlooked something?

@Carl Love 

Very elegant and new to me! I am wondering what is the help page that I have overlooked?
Thank you!

@epostma 

This will save time and prevent us from scaling errors that can still happen with the work arounds.

To make it perfect (and I am repeating myself here), there should be a plot option to set plot label units and rescale accordingly. In this instance I would have preferred everything in mm.

@tomleslie

Thank you!

I wouldn't have thought of that. I always thought that with such a construct, simplify is executed first and then convert.
Is there an explanation what is different in a nested command compared to two separate input lines?

I have not observed it recently. It vanished after system restart. I am not using style management  often so I can’t tell whether this persists.

My guess is that it is related to a change in display resolution which happens in my case in two scenarios:

• 4k on a 32’’ Monitor to 2k on internal laptop monitor and back
• Switching between two large Monitors, one at 2k the other at 4k

My overall impression is that such issues have become less frequent with newer versions of windows.

Thank you for following up