@digerdiga Coordinates(X, P) automatically defines X and P as tensor, so that Define is not necessary anymore. But you could still used it instead, if you prefer.

@digerdiga Except for the macro not used, it seems OK as well:
 

Download PhysicsCommutator_II.mw

@digerdiga It seems to work OK, see the attached. I have define X and P as coordinates, so that Define is not necessary.
 

Download PhysicsCommutator.mw

@Samir Khan It is nice to see how Maple evolves with new features and improved reliability. Whether you are a student, a teacher, an engineer, or a researcher, many Maple’s feature are just unique. About the debugger, I consider that keeping some effort on this point is strategic. Maple’s debugger do not require an incremental improvement, it needs to be reinvented. As suggested by nm, Matlab’s debugger is a very good model of inspiration for that.

Thanks for this new release!

@Carl Love Thanks, that's interesting, a good solution.

@tomleslie Thanks, this way is easy to automate, it seems that's exacty what I need!

@Kitonum  Yes, thanks, but my idea was rather how to get an automated representation of the 2D integrating surface. Of course, it is always possible to reconstruct it from the integration range given by VectorCalculus:-int. But I would like to know if it is possible to draw it prior to this calculation, in order to check it.

@Kitonum Thank you very much! I can adapt these procedure to exactly what I need. Also, I was not aware of the "foldl" operator, very interesting.

@Kitonum Thanks, works fine, but difficult to generilize to an arbitrary number of nested sums.

Hi,

Regarding the statement :

"It would be great to write an equation that isn't meant to be executed by the kernel.  In other words the equation should only be for display. "

This feature exists, it is the inert form. For instance, enter:

%int(sin(x), x = a .. b)

You will see that it appears not executed. The "%" in front of "int" makes it inert. To my knowledge, there is no limitation, almost anything in Maple can be made inert. To proceed, use the instruction "value".

One can also use quote. Try:

'int(sin(x), x = a .. b)'

It will be displayed unexecuted for once. The next time it is called, it is computed.

@John Fredsted Yes, M2018.2.1 with the latest physics up-date, v239.

Hi,

You have written D[mu] phi =D[mu] phi + something which is not consitent.

Also, do you intend to use any particular metric?

A major debugger improvement. For a comparison, the picture below gives an overview of Matlab’s debugger. It is very easy and convenient to use, leading to fast and accurate development. Its major features are:

- One can add (or remove) a break point by a single click on the left, this is the red circle. There is no instruction to write and to remove aftewards.

- Unlike Maple's debugger which only shows a single line at a time (I guess everyone can remember all the lines of his code), one still keep an overview of all the code surrounding the line of interest.

- To inspect the content of a variable, just bring the pointer on it, and a “tooltip” displays its content.

I think something similar could be implemented in Maple's code edit region.

Also related :

https://www.mapleprimes.com/posts/209233-Why-No-Improvements-Made-To-Maple-Debugger#comment203061

@Joe Riel Thanks for this information. I think, there is an important need for a better debugger, so, yes a short demonstration video would be very useful. Besides, what about implementing this debugger in the official release? It would be well suited within “code edit region”, and available to every body. BTW, “code edit region” is a very good tool and has been improved for M2018.

Hi,

I Agree with that! Maple is a software I love, but its debugger is awful. In comparison, it is so easy to develop code for Matlab. I even consider that this poor debugger is a limitation to Maple's development itself, for both users and developers. It seems however that something better exists. I have Windows, but if you have a MAC, you could try:

http://www.mapleprimes.com/posts/130672-Improved-Debugger-For-Maple