Applications, Examples and Libraries

2D contour plot and legend

by: acer 32241 Product: Maple

February 12 2019

15 1

There have been several posts, over the years, related to visual cues about the values associated with particular 2D contours in a plot.

Some people ask or post about color-bars [1]. Some people ask or post about inlined labelling of the curves [1, 2, 3, 4, 5, 6, 7]. And some post about mouse popup/hover-over functionality [1]., which got added as general new 2D plot annotation functionality in Maple 2017 and is available for the plots:-contourplot command via its contourlabels option.

Another possibility consists of a legend for 2D contour plots, with distinct entries for each contour value. That is not currently available from the plots:-contourplot command as documented. This post is about obtaining such a legend.

Aside from the method used below, a similar effect may be possible (possibly with a little effort) using contour-plotting approaches based on individual plots:-implicitplot calls for each contour level. Eg. using Kitonum's procedure, or an undocumented, alternate internal driver for plots:-contourplot.

Since I like the functionality provided by the contourlabels option I thought that I'd highjack that (and the _HOVERCONTENT plotting substructure that plot-annotations now generate) and get a relatively convenient way to get a color-key via the 2D plotting legend. This is not supposed to be super-efficient.

Here below are some examples. I hope that it illustrates some useful functionality that could be added to the contourplot command. It can also be used to get a color-key for use with densityplot.

>

restart;

>

contplot:=proc(ee, rng1, rng2)
  local clabels, clegend, i, ncrvs, newP, otherdat, others, tcrvs, tempP;
  (clegend,others):=selectremove(type,[_rest],identical(:-legend)=anything);
  (clabels,others):= selectremove(type,others,identical(:-contourlabels)=anything);
  if nops(clegend)>0 then
    tempP:=:-plots:-contourplot(ee,rng1,rng2,others[],
                                ':-contourlabels'=rhs(clegend[-1]));
    tempP:=subsindets(tempP,'specfunc(:-_HOVERCONTENT)',
                      u->`if`(has(u,"null"),NULL,':-LEGEND'(op(u))));
    if nops(clabels)>0 then
      newP:=plots:-contourplot(ee,rng1,rng2,others[],
                              ':-contourlabels'=rhs(clabels[-1]));
      tcrvs:=select(type,[op(tempP)],'specfunc(CURVES)');
      (ncrvs,otherdat):=selectremove(type,[op(newP)],'specfunc(CURVES)');
      return ':-PLOT'(seq(':-CURVES'(op(ncrvs[i]),op(indets(tcrvs[i],'specfunc(:-LEGEND)'))),
                          i=1..nops(ncrvs)),
                      op(otherdat));
    else
      return tempP;
    end if;
  elif nops(clabels)>0 then
    return plots:-contourplot(ee,rng1,rng2,others[],
                              ':-contourlabels'=rhs(clabels[-1]));
  else
    return plots:-contourplot(ee,rng1,rng2,others[]);
  end if;
end proc:

>	contplot(x^2+y^2, x=-2..2, y=-2..2, coloring=["Yellow","Blue"], contours = 9, size=[500,400], legendstyle = [location = right], legend=true, contourlabels=true, view=[-2.1..2.1,-2.1..2.1] );

>	contplot(x^2+y^2, x=-2..2, y=-2..2, coloring=["Yellow","Blue"], contours = 17, size=[500,400], legendstyle = [location = right], legend=['contourvalue',$("null",7),'contourvalue',$("null",7),'contourvalue'], contourlabels=true, view=[-2.1..2.1,-2.1..2.1] );

>

# Apparently legend items must be unique, to persist on document re-open.

contplot(x^2+y^2, x=-2..2, y=-2..2,
      coloring=["Yellow","Blue"],
      contours = 11,
      size=[500,400],
      legendstyle = [location = right],
      legend=['contourvalue',seq(cat($(` `,i)),i=2..5),
              'contourvalue',seq(cat($(` `,i)),i=6..9),
              'contourvalue'],
      contourlabels=true,
      view=[-2.1..2.1,-2.1..2.1]
);

>	contplot(x^2+y^2, x=-2..2, y=-2..2, coloring=["Green","Red"], contours = 8, size=[400,450], legend=true, contourlabels=true );

>	contplot(x^2+y^2, x=-2..2, y=-2..2, coloring=["Yellow","Blue"], contours = 13, legend=['contourvalue',$("null",5),'contourvalue',$("null",5),'contourvalue'], contourlabels=true );

>

(low,high,N):=0.1,7.6,23:
conts:=[seq(low..high*1.01, (high-low)/(N-1))]:
contplot(x^2+y^2, x=-2..2, y=-2..2,
      coloring=["Yellow","Blue"],
      contours = conts,
      legend=['contourvalue',$("null",floor((N-3)/2)),'contourvalue',$("null",ceil((N-3)/2)),'contourvalue'],
      contourlabels=true
);

>

plots:-display(
  subsindets(contplot((x^2+y^2)^(1/2), x=-2..2, y=-2..2,
                      coloring=["Yellow","Blue"],
                      contours = 7,
                      filledregions),
             specfunc(CURVES),u->NULL),
  contplot((x^2+y^2)^(1/2), x=-2..2, y=-2..2,
      coloring=["Yellow","Blue"],
      contours = 7, #grid=[50,50],
      thickness=0,
      legendstyle = [location=right],
      legend=true),
  size=[600,500],
  view=[-2.1..2.1,-2.1..2.1]
);

>

plots:-display(
  contplot(x^2+y^2, x=-2..2, y=-2..2,
      coloring=["Yellow","Blue"],
      contours = 5,
      thickness=0, filledregions),
  contplot(x^2+y^2, x=-2..2, y=-2..2,
      coloring=["Yellow","Blue"],
      contours = 5,
      thickness=3,
      legendstyle = [location=right],
      legend=typeset("<=",contourvalue)),
  size=[700,600],
  view=[-2.1..2.1,-2.1..2.1]
);

>

N:=11:
plots:-display(
  contplot(sin(x)*y, x=-2*Pi..2*Pi, y=-1..1,
      coloring=["Yellow","Blue"],
      contours = [seq(-1+(i-1)*(1-(-1))/(N-1),i=1..N)],
      thickness=3,
      legendstyle = [location=right],
      legend=true),
   plots:-densityplot(sin(x)*y, x=-2*Pi..2*Pi, y=-1..1,
      colorscheme=["zgradient",["Yellow","Blue"],colorspace="RGB"],
      grid=[100,100],
      style=surface, restricttoranges),
   plottools:-line([-2*Pi,-1],[-2*Pi,1],thickness=3,color=white),
   plottools:-line([2*Pi,-1],[2*Pi,1],thickness=3,color=white),
   plottools:-line([-2*Pi,1],[2*Pi,1],thickness=3,color=white),
   plottools:-line([-2*Pi,-1],[2*Pi,-1],thickness=3,color=white),
   size=[600,500]
);

>

N:=13:
plots:-display(
  contplot(sin(x)*y, x=-2*Pi..2*Pi, y=-1..1,
      coloring=["Yellow","Blue"],
      contours = [seq(-1+(i-1)*(1-(-1))/(N-1),i=1..N)],
      thickness=6,
      legendstyle = [location=right],
      legend=['contourvalue',seq(cat($(` `,i)),i=2..3),
              'contourvalue',seq(cat($(` `,i)),i=5..6),
              'contourvalue',seq(cat($(` `,i)),i=8..9),
              'contourvalue',seq(cat($(` `,i)),i=11..12),
              'contourvalue']),
   plots:-densityplot(sin(x)*y, x=-2*Pi..2*Pi, y=-1..1,
      colorscheme=["zgradient",["Yellow","Blue"],colorspace="RGB"],
      grid=[100,100],
      style=surface, restricttoranges),
   plottools:-line([-2*Pi,-1],[-2*Pi,1],thickness=6,color=white),
   plottools:-line([2*Pi,-1],[2*Pi,1],thickness=6,color=white),
   plottools:-line([-2*Pi,1],[2*Pi,1],thickness=6,color=white),
   plottools:-line([-2*Pi,-1],[2*Pi,-1],thickness=6,color=white),
  size=[600,500]
);

>

Download contour_legend_post.mw

A Complete Guide for Tensor computations using...

by: ecterrab 14535 Product: Maple

January 23 2019

7 1

A Complete Guide for performing Tensors computations using Physics

This is an old request, a complete guide for using Physics to perform tensor computations. This guide, shown below with Sections closed, is linked at the end of this post as a pdf file with all the sections open, and also as a Maple worksheet that allows for reproducing its contents. Most of the computations shown are reproducible in Maple 2018.2.1, and a significant part also in previous releases, but to reproduce everything you need to have the Maplesoft Physics Updates version 283 or higher installed. Feedback one how to improve this presentation is welcome.

Physics is a package developed by Maplesoft, an integral part of the Maple system. In addition to its commands for Quantum Mechanics, Classical Field Theory and General Relativity, Physics includes 5 other subpackages, three of them also related to General Relativity: Tetrads , ThreePlusOne and NumericalRelativity (work in progress), plus one to compute with Vectors and another related to the Standard Model (this one too work in progress).

The presentation is organized as follows. Section I is complete regarding the functionality provided with the Physics package for computing with tensors in Classical and Quantum Mechanics (so including Euclidean spaces), Electrodynamics and Special Relativity. The material of section I is also relevant in General Relativity, for which section II is all devoted to curved spacetimes. (The sub-section on the Newman-Penrose formalism needs to be filled with more material and a new section devoted to the EnergyMomentum tensor is appropriate. I will complete these two things as time permits.) Section III is about transformations of coordinates, relevant in general.

For an alphabetical list of the Physics commands with a brief one-line description and a link to the corresponding help page see Physics: Brief description of each command .

I. Spacetime and tensors in Physics

This section contains all what is necessary for working with tensors in Classical and Quantum Mechanics, Electrodynamics and Special Relativity. This material is also relevant for computing with tensors in General Relativity, for which there is a dedicated Section II. Curved spacetimes .

	Default metric and signature, coordinate systems

Tensors, their definition, symmetries and operations

Physics comes with a set of predefined tensors, mainly the spacetime metric , the space metric , and all the standard tensors of General Relativity. In addition, one of the strengths of Physics is that you can define tensors, in natural ways, by indicating a matrix or array with its components, or indicating any generic tensorial expression involving other tensors.

In Maple, tensor indices are letters, as when computing with paper and pencil, lowercase or upper case, latin or greek, entered using indexation, as in , and are displayed as subscripts as in . Contravariant indices are entered preceding the letter with ~, as in , and are displayed as superscripts as in . You can work with two or more kinds of indices at the same time, e.g., spacetime and space indices.

To input greek letters, you can spell them, as in mu for , or simpler: use the shortcuts for entering Greek characters . Right-click your input and choose Convert To → 2-D Math input to give to your input spelled tensorial expression a textbook high quality typesetting.

Not every indexed object or function is, however, automatically a tensor. You first need to define it as such using the Define command. You can do that in two ways:

1.	Passing the tensor being defined, say , possibly indicating symmetries and/or antisymmetries for its indices.

2.	Passing a tensorial equation where the left-hand side is the tensor being defined as in 1. and the right-hand side is a tensorial expression - or an Array or Matrix - such that the components of the tensor being defined are equal to the components of the tensorial expression.

After defining a tensor - say or - you can perform the following operations on algebraic expressions involving them

•	Automatic formatting of repeated indices, one covariant the other contravariant

•	Automatic handling of collisions of repeated indices in products of tensors

•	Simplify products using Einstein's sum rule for repeated indices.

•	SumOverRepeatedIndices of the tensorial expression.

•	Use TensorArray to compute the expression's components

•	TransformCoordinates .

If you define a tensor using a tensorial equation, in addition to the items above you can:

•	Get each tensor component by indexing, say as in or

•	Get all the covariant and contravariant components by respectively using the shortcut notation and .

•	Use any of the special indexing keywords valid for the pre-defined tensors of Physics; they are: definition, nonzero, and in the case of tensors of 2 indices also trace, and determinant.

•	No need to specify the tensor dependency for differentiation purposes - it is inferred automatically from its definition.

•	Redefine any particular tensor component using Library:-RedefineTensorComponent

•	Minimizing the number of independent tensor components using Library:-MinimizeTensorComponent

•	Compute the number of independent tensor components - relevant for tensors with several indices and different symmetries - using Library:-NumberOfTensorComponents .

The first two sections illustrate these two ways of defining a tensor and the features described. The next sections present the existing functionality of the Physics package to compute with tensors.

	Defining a tensor passing the tensor itself

	Defining a tensor passing a tensorial equation

	Automatic formatting of repeated tensor indices and handling of their collisions in products

	Tensor symmetries

	Substituting tensors and tensor indices

	Simplifying tensorial expressions

	SumOverRepeatedIndices

	Visualizing tensor components - Library:-TensorComponents and TensorArray

	Modifying tensor components - Library:-RedefineTensorComponent

	Enhancing the display of tensorial expressions involving tensor functions and derivatives using CompactDisplay

	The LeviCivita tensor and KroneckerDelta

	The 3D space metric and decomposing 4D tensors into their 3D space part and the rest

	Total differentials, the d_[mu] and dAlembertian operators

	Tensorial differential operators in algebraic expressions

	Inert tensors

	Functional differentiation of tensorial expressions with respect to tensor functions

	The Pauli matrices and the spacetime Psigma[mu] 4-vector

	The Dirac matrices and the spacetime Dgamma[mu] 4-vector

	Quantum not-commutative operators using tensor notation

II. Curved spacetimes

Physics comes with a set of predefined tensors, mainly the spacetime metric , the space metric , and all the standard tensors of general relativity, respectively entered and displayed as: Einstein[mu,nu] = , Ricci[mu,nu] = , Riemann[alpha, beta, mu, nu] = , Weyl[alpha, beta, mu, nu], = , and the Christoffel symbols Christoffel[alpha, mu, nu] = and Christoffel[~alpha, mu, nu] = respectively of first and second kinds. The Tetrads and ThreePlusOne subpackages have other predefined related tensors. This section is thus all about computing with tensors in General Relativity.

	Loading metrics from the database of solutions to Einstein's equations

	Setting the spacetime metric indicating the line element or a Matrix

	Covariant differentiation: the D_[mu] operator and the Christoffel symbols

	The Einstein, Ricci, Riemann and Weyl tensors of General Relativity

	A conversion network for the tensors of General Relativity

	Tetrads and the local system of references - the Newman-Penrose formalism

	The ThreePlusOne package and the 3+1 splitting of Einstein's equations

	III. Transformations of coordinates

	See Also
	Physics , Conventions used in the Physics package , Physics examples , Physics Updates

Download Tensors_-_A_Complete_Guide.mw, or the pdf version with sections open: Tensors_-_A_Complete_Guide.pdf

Edgardo S. Cheb-Terrab
Physics, Differential Equations and Mathematical Functions, Maplesoft

How MapleSim Helped Canada’s Paralympic Curling...

by: John McPhee 30 Products: Maple , MapleSim

January 23 2019

5 0

Recently, my research team at the University of Waterloo was approached by Mark Ideson, the skip for the Canadian Paralympic men’s curling team, about developing a curling end-effector, a device to give wheelchair curlers greater control over their shots. A gold medalist and multi-medal winner at the Paralympics, Mark has a passion to see wheelchair curling performance improve and entrusted us to assist him in this objective. We previously worked with Mark and his team on a research project to model the wheelchair curling shot and help optimize their performance on the ice. The end-effector project was the next step in our partnership.

The use of technology in the sports world is increasing rapidly, allowing us to better understand athletic performance. We are able to gather new types of data that, when coupled with advanced engineering tools, allow us to perform more in-depth analysis of the human body as it pertains to specific movements and tasks. As a result, we can refine motions and improve equipment to help athletes maximize their abilities and performance. As a professor of Systems Design Engineering at the University of Waterloo, I have overseen several studies on the motor function of Paralympic athletes. My team focuses on modelling the interactions between athletes and their equipment to maximize athletic performance, and we rely heavily on Maple and MapleSim in our research and project development.

The end-effector project was led by my UW students Borna Ghannadi and Conor Jansen. The objective was to design a device that attaches to the end of the curler’s stick and provides greater command over the stone by pulling it back prior to release. Our team modeled the end effector in Maple and built an initial prototype, which has undergone several trials and adjustments since then. The device is now on its 7^th iteration, which we felt appropriate to name the Mark 7, in recognition of Mark’s inspiration for the project. The device has been a challenge, but we have steadily made improvements with Mark’s input and it is close to being a finished product.

Currently, wheelchair curlers use a device that keeps the stone static before it’s thrown. Having the ability to pull back on the stone and break the friction prior to release will provide great benefit to the curlers. As a curler, if you can only push forward and the ice conditions aren’t perfect, you’re throwing at a different speed every time. If you can pull the stone back and then go forward, you’ve broken that friction and your shot is far more repeatable. This should make the game much more interesting.

For our team, the objective was to design a mechanism that not only allowed curlers to pull back on the stone, but also had a release option with no triggers on the curler’s hand. The device we developed screws on to the end of the curler’s stick, and is designed to rest firmly on the curling handle. Once the curler selects their shot, they can position the stone accordingly, slide the stone backward and then forward, and watch the device gently separate from the stone.

For our research, the increased speed and accuracy of MapleSim’s multibody dynamic simulations, made possible by the underlying symbolic modelling engine, Maple, allowed us to spend more time on system design and optimization. MapleSim combines principles of mechanics with linear graph theory to produce unified representations of the system topology and modelling coordinates. The system equations are automatically generated symbolically, which enables us to view and share the equations prior to a numerical solution of the highly-optimized simulation code.

The Mark 7 is an invention that could have significant ramifications in the curling world. Shooting accuracy across wheelchair curling is currently around 60-62%, and if new technology like the Mark 7 is adopted, that number could grow to 70 or 75%. Improved accuracy will make the game more enjoyable and competitive. Having the ability to pull back on the stone prior to release will eliminate some instability for the curlers, which can help level the playing field for everyone involved. Given the work we have been doing with Mark’s team on performance improvements, it was extremely satisfying for us to see them win the bronze medal in South Korea. We hope that our research and partnership with the team can produce gold medals in the years to come.

Some Interesting Applications from 2018

by: eithne 2072 Product: Maple

January 15 2019

6 0

Throughout the course of a year, Maple users create wildly varying applications on all sorts of subjects. To mark the end of 2018, I thought I’d share some of the 2018 submissions to the Maple Application Center that I personally found particularly interesting.

Solving the 15-puzzle, by Curtis Bright. You know those puzzles where you have to move the pieces around inside a square to put them in order, and there’s only one free space to move into? I’m not good at those puzzles, but it turns out Maple can help. This is one of collection of new, varied applications using Maple’s SAT solvers (if you want to solve the world’s hardest Sudoku, Maple’s SAT solvers can help with that, too).

Romeo y Julieta: Un clasico de las historias de amor... y de las ecuaciones diferenciales [Romeo and Juliet: A classic story of love..and differential equations], by Ranferi Gutierrez. This one made me laugh (and even more so once I put some of it in google translate, which is more than enough to let you appreciate the application even if you don’t speak Spanish). What’s not to like about modeling a high drama love story using DEs?

Prediction of malignant/benign of breast mass with DNN classifier, by Sophie Tan. Machine learning can save lives.

Hybrid Image of a Cat and a Dog, by Samir Khan. Signal processing can be more fun that I realized. This is one of those crazy optical illusions where the picture changes depending on how far away you are.

Beyond the 8 Queens Problem, by Yury Zavarovsky. In true mathematical fashion, why have 8 queens when you can have n? (If you are interested in this problem, you can also see a different solution that uses SAT solvers.)

Gödel's Universe, by Frank Wang. Can’t say I understood much of it, but it involves Gödel, Einstein, and Hawking, so I don’t need to understand it to find it interesting.

Overview of the Physics Updates

by: ecterrab 14535 Product: Maple

January 11 2019

8 0

Overview of the Physics Updates

One of the problems pointed out several times about the Physics package documentation is that the information is scattered. There are the help pages for each Physics command, then there is that page on Physics conventions, one other with Examples in different areas of physics, one "What's new in Physics" page at each release with illustrations only shown there. Then there are a number of Mapleprimes post describing the Physics project and showing how to use the package to tackle different problems. We seldomly find the information we are looking for fast enough.

This post thus organizes and presents all those elusive links in one place. All the hyperlinks below are alive from within a Maple worksheet. A link to this page is also appearing in all the Physics help pages in the future Maple release. Comments on practical ways to improve this presentation of information are welcome.

Description

As part of its commitment to providing the best possible environment for algebraic computations in Physics, Maplesoft launched, during 2014, a Maple Physics: Research and Development website. That enabled users to ask questions, provide feedback and download updated versions of the Physics package, around the clock.

The "Physics Updates" include improvements, fixes, and the latest new developments, in the areas of Physics, Differential Equations and Mathematical Functions. Since Maple 2018, you can install/uninstall the "Physics Updates" directly from the MapleCloud .

Maplesoft incorporated the results of this accelerated exchange with people around the world into the successive versions of Maple. Below there are two sections

•	The Updates of Physics, as an organized collection of links per Maple release, where you can find a description with examples of the subjects developed in the Physics package, from 2012 till 2019.

•	The Mapleprimes Physics posts, containing the most important posts describing the Physics project and showing the use of the package to tackle problems in General Relativity and Quantum Mechanics.

The update of Physics in Maple 2018 and back to Maple 16 (2012)

•	Physics Updates during 2018

a.	Tensor product of Quantum States using Dirac's Bra-Ket Notation

b.	Coherent States in Quantum Mechanics

c.	The Zassenhaus formula and the algebra of the Pauli matrices

d.	Multivariable Taylor series of expressions involving anticommutative (Grassmannian) variables

e.	New SortProducts command

f.	A Complete Guide for Tensor computations using Physics

•	Physics Maple 2018 updates

g.	Automatic handling of collision of tensor indices in products

h.	User defined algebraic differential operators

i.	The Physics:-Cactus package for Numerical Relativity

j.	Automatic setting of the EnergyMomentumTensor for metrics of the database of solutions to Einstein's equations

k.	Minimize the number of tensor components according to its symmetries, relabel, redefine or count the number of independent tensor components

l.	New functionality and display for inert names and inert tensors

m.	Automatic setting of Dirac, Paul and Gell-Mann algebras

n.	Simplification of products of Dirac matrices

o.	New Physics:-Library commands to perform matrix operations in expressions involving spinors with omitted indices

p.	Miscellaneous improvements

•	Physics Maple 2017 updates

q.	General Relativity: classification of solutions to Einstein's equations and the Tetrads package

r.	The 3D metric and the ThreePlusOne (3 + 1) new Physics subpackage

s.	Tensors in Special and General Relativity

t.	The StandardModel new Physics subpackage

•	Physics Maple 2016 updates

u.	Completion of the Database of Solutions to Einstein's Equations

v.	Operatorial Algebraic Expressions Involving the Differential Operators d_[mu], D_[mu] and Nabla

w.	Factorization of Expressions Involving Noncommutative Operators

x.	Tensors in Special and General Relativity

y.	Vectors Package

z.	New Physics:-Library commands

aa.	Redesigned Functionality and Miscellaneous

•	Physics Maple 2015 updates

ab.	Simplification

ac.

Tensors

ad.	Tetrads in General Relativity

ae.	More Metrics in the Database of Solutions to Einstein's Equations

af.	Commutators, AntiCommutators, and Dirac notation in quantum mechanics

ag.	New Assume command and new enhanced Mode: automaticsimplification

ah.	Vectors Package

ai.	New Physics:-Library commands

aj.	Miscellaneous

•	Physics Maple 18 updates

ak.	Simplification

al.	4-Vectors, Substituting Tensors

am.	Functional Differentiation

an.	More Metrics in the Database of Solutions to Einstein's Equations

ao.	Commutators, AntiCommutators

ap.	Expand and Combine

aq.	New Enhanced Modes in Physics Setup

ar.

Dagger

as.	Vectors Package

at.	New Physics:-Library commands

au.	Miscellaneous

•	Physics Maple 17 updates

av.	Tensors and Relativity: ExteriorDerivative, Geodesics, KillingVectors, LieDerivative, LieBracket, Antisymmetrize and Symmetrize

aw.	Dirac matrices, commutators, anticommutators, and algebras

ax.	Vector Analysis

ay.	A new Library of programming commands for Physics

•	Physics Maple 16 updates

az.	Tensors in Special and General Relativity: contravariant indices and new commands for all the General Relativity tensors

ba.	New commands for working with expressions involving anticommutative variables and functions: Gtaylor, ToFieldComponents, ToSuperfields

bb.	Vector Analysis: geometrical coordinates with funcional dependency

Mapleprimes Physics posts

1.	The Physics project at Maplesoft

2.	Mini-Course: Computer Algebra for Physicists

3.	A Complete Guide for Tensor computations using Physics

4.	Perimeter Institute-2015, Computer Algebra in Theoretical Physics (I)

5.	IOP-2016, Computer Algebra in Theoretical Physics (II)

6.	ACA-2017, Computer Algebra in Theoretical Physics (III)

•	General Relativity

7.	General Relativity using Computer Algebra

8.	Exact solutions to Einstein's equations

9.	Classification of solutions to Einstein's equations and the ThreePlusOne (3 + 1) package

10.	Tetrads and Weyl scalars in canonical form

11.	Equivalence problem in General Relativity

12.	Automatic handling of collision of tensor indices in products

13.	Minimize the number of tensor components according to its symmetries

•	Quantum Mechanics

14.	Quantum Commutation Rules Basics

15.	Quantum Mechanics: Schrödinger vs Heisenberg picture

16.	Quantization of the Lorentz Force

17.	Magnetic traps in cold-atom physics

18.	The hidden SO(4) symmetry of the hydrogen atom

19.	(I) Ground state of a quantum system of identical boson particles

20.	(II) The Gross-Pitaevskii equation and Bogoliubov spectrum

21.	(III) The Landau criterion for Superfluidity

22.	Simplification of products of Dirac matrices

23.	Algebra of Dirac matrices with an identity matrix on the right-hand side

24.	Factorization with non-commutative variables

25.	Tensor Products of Quantum State Spaces

26.	Coherent States in Quantum Mechanics

27.	The Zassenhaus formula and the Pauli matrices

•	Physics package generic functionality

28.	Automatic simplification and a new Assume (as in "extended assuming")

29.	Wirtinger derivatives and multi-index summation

	See Also
	Conventions used in the Physics package , Physics , Physics examples , A Complete Guide for Tensor computations using Physics

Download Physics-Updates.mw

Edgardo S. Cheb-Terrab
Physics, Differential Equations and Mathematical Functions, Maplesoft

The Zassenhaus formula and the Pauli matrices

by: ecterrab 14535 Product: Maple

January 11 2019

6 0

The Zassenhaus formula and the algebra of the Pauli matrices

Edgardo S. Cheb-Terrab¹ and Bryan C. Sanctuary²

(1) Maplesoft

(2) Department of Chemistry, McGill University, Montreal, Quebec, Canada

The implementation of the Pauli matrices and their algebra were reviewed during 2018, including the algebraic manipulation of nested commutators, resulting in faster computations using simpler and more flexible input. As it frequently happens, improvements of this type suddenly transform research problems presented in the literature as untractable in practice, into tractable.

As an illustration, we tackle below the derivation of the coefficients entering the Zassenhaus formula shown in section 4 of [1] for the Pauli matrices up to order 10 (results in the literature go up to order 5). The computation presented can be reused to compute these coefficients up to any desired higher-order (hardware limitations may apply). A number of examples which exploit this formula and its dual, the Baker-Campbell-Hausdorff formula, occur in connection with the Weyl prescription for converting a classical function to a quantum operator (see sec. 5 of [1]), as well as when solving the eigenvalue problem for classes of mathematical-physics partial differential equations [2].
To reproduce the results below - a worksheet with this contents is linked at the end - you need to have your Maple 2018.2.1 updated with the Maplesoft Physics Updates version 280 or higher.

References

[1] R.M. Wilcox, "Exponential Operators and Parameter Differentiation in Quantum Physics", Journal of Mathematical Physics, V.8, 4, (1967.

[2] S. Steinberg, "Applications of the lie algebraic formulas of Baker, Campbell, Hausdorff, and Zassenhaus to the calculation of explicit solutions of partial differential equations", Journal of Differential Equations, V.26, 3, 1977.

[3] K. Huang, "Statistical Mechanics", John Wiley & Sons, Inc. 1963, p217, Eq.(10.60).

Formulation of the problem

The Zassenhaus formula expresses as an infinite product of exponential operators involving nested commutators of increasing complexity

=

Given , and their commutator , if and commute with , for and the Zassenhaus formula reduces to the product of the first three exponentials above. The interest here is in the general case, when and , and the goal is to compute the Zassenhaus coefficients in terms of , for arbitrary finite n. Following [1], in that general case, differentiating the Zassenhaus formula with respect to and multiplying from the right by one obtains

This is an intricate formula, which however (see eq.(4.20) of [1]) can be represented in abstract form as

$"0=((∑)(lambda^n)/(n!) {A^n,B})+2 lambda ((∑) (∑)(lambda^(n+m))/(n! m!) {A^m,B^n,C[2]})+3 lambda^2 ((∑) (∑) (∑)(lambda^(n+m+k))/(n! m! k!) {A^k,B^m,(C[2])^n,C[3]})+ ..."$

from where an equation to be solved for each is obtained by equating to 0 the coefficient of . In this formula, the repeated commutator bracket is defined inductively in terms of the standard commutator by

${B, A^0} = B, {B, A^(n+1)} = %Commutator(A, {A^n, B^n})$

${C[j], B^n, A^0} = {C[j], B^n}, {C[j], A^m, B^n} = %Commutator(A, {A^`-`(m, 1), B^n, C[j]^k})$

and higher-order repeated-commutator brackets are similarly defined. For example, taking the coefficient of and and respectively solving each of them for and one obtains

This method is used in [3] to treat quantum deviations from the classical limit of the partition function for both a Bose-Einstein and Fermi-Dirac gas. The complexity of the computation of grows rapidly and in the literature only the coefficients up to have been published. Taking advantage of developments in the Physics package during 2018, below we show the computation up to and provide a compact approach to compute them up to arbitrary finite order.

Computing up to

Set the signature of spacetime such that its space part is equal to +++ and use lowercaselatin letters to represent space indices. Set also , and to represent quantum operators

>

(1)

To illustrate the computation up to , a convenient example, where the commutator algebra is closed, consists of taking and as Pauli Matrices which, multiplied by the imaginary unit, form a basis for the group, which in turn exponentiate to the relevant Special Unitary Group . The algebra for the Pauli matrices involves a commutator and an anticommutator

>

(2)

Assign now and to two Pauli matrices, for instance

>

(3)

>

(4)

Next, to extract the coefficient of from

$"0=((∑)(lambda^n)/(n!) {A^n,B})+2 lambda ((∑) (∑)(lambda^(n+m))/(n! m!) {A^m,B^n,C[2]})+3 lambda^2 ((∑) (∑) (∑)(lambda^(n+m+k))/(n! m! k!) {A^k,B^m,(C[2])^n,C[3]})+..."$

to solve it for we note that each term has a factor multiplying a sum, so we only need to take into account the first terms (sums) and in each sum replace by the corresponding . For example, given to compute we only need to compute these first three terms:

$0 = Sum(lambda^n*{B, A^n}/factorial(n), n = 1 .. 2)+2*lambda*(Sum(Sum(lambda^(n+m)*{C[2], A^m, B^n}/(factorial(n)*factorial(m)), n = 0 .. 1), m = 0 .. 1))+3*lambda^2*(Sum(Sum(Sum(lambda^(n+m+k)*{C[3], A^k, B^m, C[2]^n}/(factorial(n)*factorial(m)*factorial(k)), n = 0 .. 0), m = 0 .. 0), k = 0 .. 0))$

then solving for one gets .

Also, since to compute we only need the coefficient of , it is not necessary to compute all the terms of each multiple-sum. One way of restricting the multiple-sums to only one power of consists of using multi-index summation, available in the Physics package (see Physics:-Library:-Add ). For that purpose, redefine sum to extend its functionality with multi-index summation

>

(5)

Now we can represent the same computation of without multiple sums and without computing unnecessary terms as

$0 = Sum(lambda^n*{B, A^n}/factorial(n), n = 1)+2*lambda*(Sum(lambda^(n+m)*{C[2], A^m, B^n}/(factorial(n)*factorial(m)), n+m = 1))+3*lambda^2*(Sum(lambda^(n+m+k)*{C[3], A^k, B^m, C[2]^n}/(factorial(n)*factorial(m)*factorial(k)), n+m+k = 0))$

Finally, we need a computational representation for the repeated commutator bracket

${B, A^0} = B, {B, A^(n+1)} = %Commutator(A, {A^n, B^n})$

One way of representing this commutator bracket operation is defining a procedure, say F, with a cache to avoid recomputing lower order nested commutators, as follows

>

(6)

>

For example,

>

(7)

>

(8)

>

(9)

We can set now the value of

>

(10)

and enter the formula that involves only multi-index summation

>

H := sum(lambda^n*F(A, B, n)/factorial(n), n = 2)+2*lambda*(sum(lambda^(n+m)*F(A, F(B, C[2], n), m)/(factorial(n)*factorial(m)), n+m = 1))+3*lambda^2*(sum(lambda^(n+m+k)*F(A, F(B, F(C[2], C[3], n), m), k)/(factorial(n)*factorial(m)*factorial(k)), n+m+k = 0))

(1/2)*lambda^2*%Commutator(Physics:-Psigma[1], %Commutator(Physics:-Psigma[1], Physics:-Psigma[3]))+2*lambda*(lambda*%Commutator(Physics:-Psigma[1], I*Physics:-Psigma[2])+lambda*%Commutator(Physics:-Psigma[3], I*Physics:-Psigma[2]))+3*lambda^2*C[3]

(11)

from where we compute by solving for it the coefficient of , and since due to the mulit-index summation this expression already contains as a factor,

>

C[3] = (2/3)*Physics:-Psigma[3]-(4/3)*Physics:-Psigma[1]

(12)

In order to generalize the formula for H for higher powers of , the right-hand side of the multi-index summation limit can be expressed in terms of an abstract N, and H transformed into a mapping:

>

H := unapply(sum(lambda^n*F(A, B, n)/factorial(n), n = N)+2*lambda*(sum(lambda^(n+m)*F(A, F(B, C[2], n), m)/(factorial(n)*factorial(m)), n+m = N-1))+3*lambda^2*(sum(lambda^(n+m+k)*F(A, F(B, F(C[2], C[3], n), m), k)/(factorial(n)*factorial(m)*factorial(k)), n+m+k = N-2)), N)

(13)

Now we have

>

(14)

>

(15)

The following is already equal to (11)

>

(1/2)*lambda^2*%Commutator(Physics:-Psigma[1], %Commutator(Physics:-Psigma[1], Physics:-Psigma[3]))+2*lambda*(lambda*%Commutator(Physics:-Psigma[1], I*Physics:-Psigma[2])+lambda*%Commutator(Physics:-Psigma[3], I*Physics:-Psigma[2]))+3*lambda^2*C[3]

(16)

In this way, we can reproduce the results published in the literature for the coefficients of Zassenhaus formula up to by adding two more multi-index sums to (13). Unassign first

>

We compute now up to in one go

>

for j to 4 do C[j+1] := Simplify(solve(H(j), C[j+1])) end do

(2/3)*Physics:-Psigma[3]-(4/3)*Physics:-Psigma[1]

-(8/9)*Physics:-Psigma[1]-(158/45)*Physics:-Psigma[3]-((16/3)*I)*Physics:-Psigma[2]

(17)

The nested-commutator expression solved in the last step for is

>

(18)

With everything understood, we want now to extend these results generalizing them into an approach to compute an arbitrarily large coefficient , then use that generalization to compute all the Zassenhaus coefficients up to . To type the formula for H for higher powers of is however prone to typographical mistakes. The following is a program, using the Maple programming language , that produces these formulas for an arbitrary integer power of :

Formula := proc(A, B, C, Q)

This Formula program uses a sequence of summation indices with as much indices as the order of the coefficient we want to compute, in this case we need 10 of them

>

(19)

To avoid interference of the results computed in the loop (17), unassign again

>

Now the formulas typed by hand, used lines above to compute each of , and , are respectively constructed by the computer

>

sum(lambda^n*F(Physics:-Psigma[1], Physics:-Psigma[3], n)/factorial(n), n = N)+2*lambda*(sum(lambda^(n+m)*F(Physics:-Psigma[1], F(Physics:-Psigma[3], C[2], n), m)/(factorial(n)*factorial(m)), n+m = N-1))

(20)

>

sum(lambda^n*F(Physics:-Psigma[1], Physics:-Psigma[3], n)/factorial(n), n = N)+2*lambda*(sum(lambda^(n+m)*F(Physics:-Psigma[1], F(Physics:-Psigma[3], C[2], n), m)/(factorial(n)*factorial(m)), n+m = N-1))+3*lambda^2*(sum(lambda^(n+m+k)*F(Physics:-Psigma[1], F(Physics:-Psigma[3], F(C[2], C[3], n), m), k)/(factorial(n)*factorial(m)*factorial(k)), n+m+k = N-2))

(21)

>

(22)

Construct then the formula for and make it be a mapping with respect to N, as done for after (16)

>

(23)

Compute now the coefficients of the Zassenhaus formula up to all in one go

>

for j to 9 do C[j+1] := Simplify(solve(H(j), C[j+1])) end do

(2/3)*Physics:-Psigma[3]-(4/3)*Physics:-Psigma[1]

-(8/9)*Physics:-Psigma[1]-(158/45)*Physics:-Psigma[3]-((16/3)*I)*Physics:-Psigma[2]

(1030/81)*Physics:-Psigma[1]-(8/81)*Physics:-Psigma[3]+((1078/405)*I)*Physics:-Psigma[2]

((11792/243)*I)*Physics:-Psigma[2]+(358576/42525)*Physics:-Psigma[1]+(12952/135)*Physics:-Psigma[3]

(87277417/492075)*Physics:-Psigma[1]+(833718196/820125)*Physics:-Psigma[3]+((35837299048/17222625)*I)*Physics:-Psigma[2]

-((449018539801088/104627446875)*I)*Physics:-Psigma[2]-(263697596812424/996451875)*Physics:-Psigma[1]+(84178036928794306/2197176384375)*Physics:-Psigma[3]

(3226624781090887605597040906/21022858292748046875)*Physics:-Psigma[1]+(200495118165066770268119656/200217698026171875)*Physics:-Psigma[3]+((2185211616689851230363020476/4204571658549609375)*I)*Physics:-Psigma[2]

(24)

Notes: with the material above you can compute higher order values of . For that you need:

1.	Unassign as done above in two opportunities, to avoid interference of the results just computed.

2.	Indicate more summation indices in the sequence in (19), as many as the maximum value of n in .

3.	Have in mind that the growth in size and complexity is significant, with each taking significantly more time than the computation of all the previous ones.

4.	Re-execute the input line (23) and the loop (24).

>

Download The_Zassenhause_formula_and_the_Pauli_Matrices.mw

Edgardo S. Cheb-Terrab
Physics, Differential Equations and Mathematical Functions, Maplesoft

Improve Your Chess Rating with Math

by: Joe Riel 9660

January 05 2019

9 4

Over the holidays I reconnected with an old friend and occasional
chess partner who, upon hearing I was getting soundly thrashed by run
of the mill engines, recommended checking out the ChessTempo site. It
has online tools for training your chess tactics. As you attempt to
solve chess problems your rating is computed depending on how well you
do. The chess problems, too, are rated and adjusted as visitors
attempt them. This should be familar to any chess or table-tennis
player. Rather than the Elo rating system, the Glicko rating system is
used.

You have a choice of the relative difficulty of the problems.
After attempting a number of easy puzzles and seeing my rating slowly
climb, I wondered what was the most effective technique to raise my
rating (the classical blunder). Attempting higher rated problems would lower my
solving rate, but this would be compensated by a smaller loss and
larger gain. Assuming my actual playing strength is greater than my
current rating (a misconception common to us patzers), there should be a
rating that maximizes the rating gain per problem.

The following Maple module computes the expected rating change
using the Glicko system.

Glicko := module()

export DeltaRating
    ,  ExpectedDelta
    ,  Pwin
    ;

    # Return the change in rating for a loss and a win
    # for player 1 against player2
    DeltaRating := proc(r1,rd1,r2,rd2)
    local E, K, g, g2, idd, q;

        q := ln(10)/400;
        g := rd -> 1/sqrt(1 + 3*q^2*rd^2/Pi^2);
        g2 := g(rd2);
        E := 1/(1+10^(-g2*(r1-r2)/400));
        idd := q^2*(g2^2*E*(1-E));

        K := q/(1/rd1^2+idd)*g2;

        (K*(0-E), K*(1-E));

    end proc:

    # Compute the probability of a win
    # for a player with strength s1
    # vs a player with strength s2.

    Pwin := proc(s1, s2)
    local p;
        p := 10^((s1-s2)/400);
        p/(1+p);
    end proc:

    # Compute the expected rating change for
    # player with strength s1, rating r1 vs a player with true rating r2.
    # The optional rating deviations are rd1 and rd2.

    ExpectedDelta := proc(s1,r1,r2,rd1 := 35, rd2 := 35)
    local P, l, w;
        P := Pwin(s1,r2);
        (l,w) := DeltaRating(r1,rd1,r2,rd2);
        P*w + (1-P)*l;
    end proc:

end module:

Assume a player has a rating of 1500 but an actual playing strength of 1700. Compute the expected rating change for a given puzzle rating, then plot it. As expected the graph has a peak.

Ept := Glicko:-ExpectedDelta(1700,1500,r2):
plot(Ept,r2 = 1000...2000);

Compute the optimum problem rating

fsolve(diff(Ept,r2));

                     {r2 = 1599.350691}

As your rating improves, you'll want to adjust the rating of the problems (the site doesn't allow that fine tuning). Here we plot the optimum puzzle rating (r2) for a given player rating (r1), assuming the player's strength remains at 1700.

Ept := Glicko:-ExpectedDelta(1700, r1, r2):
dEpt := diff(Ept,r2):
r2vsr1 := r -> fsolve(eval(dEpt,r1=r)):
plot(r2vsr1, 1000..1680);

Here is a Maple worksheet with the code and computations.

Glicko.mw

Later

After pondering this, I realized there is a more useful way to present the results. The shape of the optimal curve is independent of the user's actual strength. Showing that is trivial, just substitute a symbolic value for the player's strength, offset the ratings from it, and verify that the result does not depend on the strength.

Ept := Glicko:-ExpectedDelta(S, S+r1, S+r2):
has(Ept, S);
                    false

Here's the general curve, shifted so the player's strength is 0, r1 and r2 are relative to that.

r2_r1 := r -> rhs(Optimization:-Maximize(eval(Ept,r1=r), r2=-500..0)[2][]):
p1 := plot(r2_r1, -500..0, 'numpoints'=30);

Compute and plot the expected points gained when playing the optimal partner and your rating is r-points higher than your strength.

EptMax := r -> eval(Ept, [r1=r, r2=r2_r1(r)]):
plot(EptMax, -200..200, 'numpoints'=30, 'labels' = ["r","Ept"]);

When your playing strength matches your rating, the optimal opponent has a relative rating of

r2_r1(0);
                       -269.86

The expected points you win is

evalf(EptMax(0));
                       0.00956

Coherent States in Quantum Mechanics

by: ecterrab 14535 Product: Maple

January 05 2019

5 0

Coherent States in Quantum Mechanics

Pascal Szriftgiser¹ and Edgardo S. Cheb-Terrab²

(1) Laboratoire PhLAM, UMR CNRS 8523, Université Lille 1, F-59655, France

(2) Maplesoft

Coherent states are among the most relevant representations for the state of a quantum system. These states, that form an overcomplete basis, minimize the quantum uncertainty between position x and momentum p (they satisfy the Heisenberg uncertainty principle with equality and their expectation values satisfy the classical equations of motion). Coherent states are widely used in quantum optics and quantum mechanics in general; they also mathematically characterize the concept of Planck cells. Part of this development is present in Maple 2018.2.1. To reproduce what you see below, however, you need a more recent version, as the one distributed within the Maplesoft Physics Updates (version 276 or higher). A worksheet with this contents is linked at the end of this post.

Definition and the basics

>

Set a quantum operator and corresponding annihilation / creation operators

>

(1.1)

>

(1.2)

>

(1.3)

In what follows, on the left-hand sides the product operator used is `*`, which properly represents, but does not perform the attachment of Bras Kets and operators. On the right-hand sides the product operator is `.`, that performs the attachments. Since the introduction of Physics in the Maple system, we have that

>

(1.4)

>

(1.5)

>

(1.6)

New development during 2018: coherent states, the eigenstates of the annihilation operator , with all of their properties, are now understood as such by the system

>

(1.7)

is an eigenket of but not of

>

(1.8)

The norm of these states is equal to 1

>

(1.9)

These states, however, are not orthonormal as the occupation number states are, and since is not Hermitian, its eigenvalues are not real but complex numbers. Instead of (1.6) , we now have

>

%Bracket(Physics:-Bra(`#msup(mi("a"),mo("&uminus0;"))`, alpha), Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, beta)) = exp(-(1/2)*abs(alpha)^2-(1/2)*abs(beta)^2+conjugate(alpha)*beta)

(1.10)

At ,

>

(1.11)

Their scalar product with the occupation number states , using the inert %Bracket on the left-hand side and the active Bracket on the other side:

>

%Bracket(Physics:-Bra(A, n), Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha)) = exp(-(1/2)*abs(alpha)^2)*alpha^n/factorial(n)^(1/2)

(1.12)

The expansion of coherent states into occupation number states, first representing the product operation using `*`, then performing the attachments replacing `*` by `.`

>

Sum(Physics:-`*`(Physics:-Ket(A, n), Physics:-Bra(A, n)), n = 0 .. infinity)

(1.13)

>

Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha) = Physics:-`*`(Sum(Physics:-`*`(Physics:-Ket(A, n), Physics:-Bra(A, n)), n = 0 .. infinity), Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha))

(1.14)

>

Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha) = Sum(exp(-(1/2)*abs(alpha)^2)*alpha^n*Physics:-Ket(A, n)/factorial(n)^(1/2), n = 0 .. infinity)

(1.15)

Hide now the ket label. When in doubt, input show to see the Kets with their labels explicitly shown

>

(1.16)

Define eigenkets of the annihilation operator, with two different eigenvalues for experimentation

>

(1.17)

>

(1.18)

Because the properties of coherent states are now known to the system, the following computations proceed automatically. The left-hand sides use the `*`, while the right-hand sides use the `.`

>

(1.19)

>

(1.20)

>

(1.21)

>

(1.22)

Properties of Coherent states

The mean value of the occupation number N

The occupation number operator N is given by

>

(2.1.1)

>

(2.1.2)

>

(2.1.3)

N is diagonal in the basis of the Fock (occupation number) space

>

(2.1.4)

•	The mean value of N in a coherent state

>

(2.1.5)

>

(2.1.6)

The mean value of

>

(2.1.7)

>

(2.1.8)

The standard deviation for a state

>

(2.1.9)

In conclusion, a coherent state has a finite spreading . Coherent states are good approximations for the states of a laser, where the laser intensity I is proportional to the mean value of the photon number, I f , and so the intensity fluctuation, .

•	The mean value of the occupation number N in an occupation number state

>

(2.1.10)

>

(2.1.11)

The mean value of the occupation number N in a state is thus n itself, as expected since represents a (Fock space) state of n (quase-) particles. Accordingly,

>

(2.1.12)

>

(2.1.13)

The standard deviation for a state , is thus

>

(2.1.14)

That is, in a Fock state, , there is no intensity fluctuation.

The specific properties of coherent states implemented can be derived explicitly departing from the projection of into the basis of occupation number states and the definition of as the operator that annihilates the vacuum

>

Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha) = Physics:-`*`(Sum(Physics:-`*`(Physics:-Ket(A, n), Physics:-Bra(A, n)), n = 0 .. infinity), Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha))

(2.2.1)

>

Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha) = Sum(exp(-(1/2)*abs(alpha)^2)*alpha^n*Physics:-Ket(A, n)/factorial(n)^(1/2), n = 0 .. infinity)

(2.2.2)

To derive from the formula above, start multiplying by

>

Physics:-`*`(`#msup(mi("a"),mo("&uminus0;"))`, Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha)) = Physics:-`*`(`#msup(mi("a"),mo("&uminus0;"))`, Sum(exp(-(1/2)*abs(alpha)^2)*alpha^n*Physics:-Ket(A, n)/factorial(n)^(1/2), n = 0 .. infinity))

(2.2.3)

In view of , discard the first term of the sum

>

Physics:-`*`(`#msup(mi("a"),mo("&uminus0;"))`, Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha)) = Physics:-`*`(`#msup(mi("a"),mo("&uminus0;"))`, Sum(exp(-(1/2)*abs(alpha)^2)*alpha^n*Physics:-Ket(A, n)/factorial(n)^(1/2), n = 1 .. infinity))

(2.2.4)

Change variables ; in the result rename

>

Physics:-`*`(`#msup(mi("a"),mo("&uminus0;"))`, Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha)) = Sum(exp(-(1/2)*abs(alpha)^2)*Physics:-`*`(`#msup(mi("a"),mo("&uminus0;"))`, Physics:-Ket(A, n+1))*alpha^(n+1)/(factorial(n)^(1/2)*(n+1)^(1/2)), n = 0 .. infinity)

(2.2.5)

Activate the product by replacing, in the right-hand side, the product operator `*` by `.`

>

Physics:-`*`(`#msup(mi("a"),mo("&uminus0;"))`, Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha)) = Sum(exp(-(1/2)*abs(alpha)^2)*Physics:-Ket(A, n)*alpha^(n+1)/factorial(n)^(1/2), n = 0 .. infinity)

(2.2.6)

By inspection the right-hand side of (2.2.6) is equal to times the right-hand side of (2.2.2)

>

alpha*Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha)-Physics:-`*`(`#msup(mi("a"),mo("&uminus0;"))`, Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha)) = alpha*(Sum(exp(-(1/2)*abs(alpha)^2)*alpha^n*Physics:-Ket(A, n)/factorial(n)^(1/2), n = 0 .. infinity))-(Sum(exp(-(1/2)*abs(alpha)^2)*Physics:-Ket(A, n)*alpha^(n+1)/factorial(n)^(1/2), n = 0 .. infinity))

(2.2.7)

>

(2.2.8)

•	Overview of the coherent states distribution

Consider the projection of over an occupation number state

>

%Bracket(Physics:-Bra(A, n), Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha)) = exp(-(1/2)*abs(alpha)^2)*alpha^n/factorial(n)^(1/2)

(2.2.9)

An overview of the distribution of coherent states for a sample of values of n and is thus as follows

>

The distribution can be explored for ranges of values of n and using Explore

>

	=

	=

`<|>`(beta, alpha) = exp(conjugate(beta)*alpha-(1/2)*abs(beta)^2-(1/2)*abs(alpha)^2)

The identity in the title can be derived departing again from the the projection of a coherent stateinto the basis of occupation number states

>

Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha) = Sum(exp(-(1/2)*abs(alpha)^2)*alpha^n*Physics:-Ket(A, n)/factorial(n)^(1/2), n = 0 .. infinity)

(2.6.1)

>	$Dagger(subs({alpha = beta, n = k}, Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha) = Sum(exp(-(1/2)abs(alpha)^2)alpha^n*Ket(A, n)/factorial(n)^(1/2), n = 0 .. infinity)))$

Physics:-Bra(`#msup(mi("a"),mo("&uminus0;"))`, beta) = Sum(exp(-(1/2)*abs(beta)^2)*conjugate(beta)^k*Physics:-Bra(A, k)/factorial(k)^(1/2), k = 0 .. infinity)

(2.6.2)

Taking the `*` product of these two expressions

>

Physics:-`*`(Physics:-Bra(`#msup(mi("a"),mo("&uminus0;"))`, beta), Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha)) = Physics:-`*`(Sum(exp(-(1/2)*abs(beta)^2)*conjugate(beta)^k*Physics:-Bra(A, k)/factorial(k)^(1/2), k = 0 .. infinity), Sum(exp(-(1/2)*abs(alpha)^2)*alpha^n*Physics:-Ket(A, n)/factorial(n)^(1/2), n = 0 .. infinity))

(2.6.3)

Perform the attachment of Bras and Kets on the right-hand side by replacing `*` by `.`, evaluating the sum and simplifying the result

>

Physics:-`*`(Physics:-Bra(`#msup(mi("a"),mo("&uminus0;"))`, beta), Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha)) = exp(-(1/2)*abs(beta)^2-(1/2)*abs(alpha)^2+alpha*conjugate(beta))

(2.6.4)

•	Overview of the real and imaginary part of

In most cases, and are complex valued numbers. Below, the plots assume that and are both real. To take into account the general case, the possibility to tune a phase difference between and is explicitly added, so that (2.6.4) becomes

>

%Bracket(Physics:-Bra(`#msup(mi("a"),mo("&uminus0;"))`, beta), Physics:-Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha)) = exp(-(1/2)*abs(beta)^2-(1/2)*abs(alpha)^2+alpha*conjugate(beta)*exp(I*theta))

(2.6.5)

>

Explore(plot3d(Re(rhs(%Bracket(Bra(`#msup(mi("a"),mo("&uminus0;"))`, beta), Ket(`#msup(mi("a"),mo("&uminus0;"))`, alpha)) = exp(-(1/2)*abs(beta)^2-(1/2)*abs(alpha)^2+alpha*conjugate(beta)*exp(I*theta)))), alpha = -10 .. 10, beta = -10 .. 10, view = -1 .. 1, orientation = [-12, 74, 3], axes = boxed), parameters = [theta = 0 .. 2*Pi], initialvalues = [theta = (1/10)*Pi])

Download Coherent_States_in_Quantum_Mechanics.mw

Edgardo S. Cheb-Terrab
Physics, Differential Equations and Mathematical Functions, Maplesoft
Editor, Computer Physics Communications

Tensor products in Quantum Mechanics using Dirac's...

by: ecterrab 14535 Product: Maple

December 30 2018

6 0

Tensor product of Quantum States using Dirac's Bra-Ket Notation - 2018

There has been increasing interest in the details of the Maple implementation of tensor products using Dirac's notation, developed during 2018. Tensor products of Hilbert spaces and related quantum states are relevant in a myriad of situations in quantum mechanics, and in particular regarding quantum information. Below is a presentation up-to-date of the design and implementation, with input/output and examples, organized in four sections:

•	The basic ideas and design implemented

•	Tensor product notation and the hideketlabel option

•	Entangled States and the Bell basis

•	Entangled States, Operators and Projectors

Part of this development is present in Maple 2018.2. To reproduce what you see below, however, you need a more recent version, as the one distributed within the Maplesoft Physics Updates (version 272 or higher).

The basic ideas and design implemented

Suppose and are quantum operators and are, respectively, their eigenkets. The following works since the introduction of the Physics package in Maple

>

(1.1)

>

(1.2)

>

(1.3)

In previous Maple releases, all quantum operators are supposed to act on the same Hillbert space. New: suppose that and act on different, disjointed, Hilbert spaces.

1) To represent that situation, a new keyword in Setup , , is introduced. With it you can indicate the quantum operators that act on a Hilbert space, say as in with the meaning that the operator acts on one Hilbert space while acts on another one.

The Hilbert space thus has no particular name (as in 1, 2, 3 ...) and is instead identified by the operators that act on it. There can be one or more, and operators acting on one space can act on other spaces too. The disjointedspaces keyword is a synonym for hilbertspaces and hereafter all Hilbert spaces are assumed to be disjointed.

NOTE: noncommutative quantum operators acting on disjointed spaces commute between themselves, so after setting - for instance - , automatically, become quantum operators satisfying (see comment (ii) on page 156 of ref.[1])

2) Product of Kets and Bras that belong to different Hilbert spaces, are understood as tensor products satisfying (see footnote on page 154 of ref. [1]):

while

3) All the operators of one Hilbert space act transparently over operators, Bras and Kets of other Hilbert spaces. For example

and the same for the Dagger of this equation, that is

Hence, when we write the left-hand sides of the two equations above and press enter, they are automatically rewritten (returned) as the right-hand sides.

4) Every other quantum operator, set as such using Setup , and not indicated as acting on any particular Hilbert space, is assumed to act on all spaces.

5) Notation:

•

Tensor products formed with operators, or Bras and Kets belonging to different Hilbert spaces (set as such using Setup and the keyword hilbertspaces), are now displayed with the symbol 5 in between, as in instead of , and instead of . The product of an operator of one space and a Ket of another space however, is displayed , without 5.

•	A new Setup option hideketlabel , makes all the labels in Kets and Bras to be hidden at the time of displaying Kets, Bras and Bracket, so when you set it entering ,

is displayed as

This is the notation frequently used when working with angular momentum or in quantum information, where tensor products of Hilbert spaces are used.

	Design details

Tensor product notation and the hideketlabel option

According to the design section, set now two disjointed Hilbert spaces with operators acting on one of them and on the other one (you can think of )

>

(2.1)

Consider a tensor product of Kets, each of which belongs to one of these different spaces, note the new notation using

>

(2.2)

•	As explained in the Details of the design section, the ordering of the Hilbert spaces in tensor products is now preserved: Bras (Kets) of the first space always appear before Bras (Kets) of the second space. For example, construct a projector into the state (2.2)

>

(2.3)

You see that in the product of Bras, and also in the product of Kets, A comes first, then B.

Remark: some textbooks prefer a diadic style for sorting the operands in products of Bras and Kets that belong to different spaces, for example, instead of the projector sorting style of (2.3). Both reorderings of Kets and Bras are mathematically equal.

•	Because that ordering is preserved, one can now hide the label of Bras and Kets without ambiguity, as it is usual in textbooks (e.g. in Quantum Information). For that purpose use the new keyword option hideketlabel

>

(2.4)

The display for (2.3) is now

>

(2.5)

Important: this new option only hides the label while displaying the Bra or Ket. The label, however, is still there, both in the input and in the output. One can "see" what is behind this new display using show, that works the same way as it does in the context of CompactDisplay . The actual contents being displayed in (2.5) is thus (2.3)

>

(2.6)

Operators of each of these spaces act on their eigenkets as usual. Here we distribute over both sides of an equation, using `*` on the left-hand side, to see the product uncomputed, and `.` on the right-hand side to see it computed:

>

(2.7)

>

(2.8)

•	The tensor product of operators belonging to different Hilbert spaces is also displayed using 5

>

(2.9)

•

As mentioned in the preceding design section, using the commutativity between operators, Bras and Kets that belong to different Hilbert spaces, within a product, operators are placed contiguous to the Kets and Bras belonging to the space where the operator acts. For example, consider the delayed product represented using the start `*` operator

>

(2.10)

Release the product

>

(2.11)

The same operation but now using the dot product `.` operator. Start by delaying the operation

>

(2.12)

Recalling that this product is mathematically the same as (2.11), and that

>

(2.13)

by releasing the delayed product (2.12) we have

>

(2.14)

Reset hideketlabel

>

(2.15)

	Implementation details

Entangled States and the Bell basis

With the introduction of disjointed Hilbert spaces in Maple it is possible to represent entangled quantum states in a simple way, basically as done with paper and pencil.

Recalling the Hilbert spaces set at this point are,

>

(3.1)

where acts on the tensor product of the spaces where and act. A state of can then always be written as

>

(3.2)

where is a matrix of complex coefficients. Bra states of are formed as usual taking the Dagger

>

(3.3)

•

By definition, all states that can be written exactly as , that is, the product of a arbitrary state of the subspace A and another of the subspace B, are product states, and all the other ones are entangled states. Entangelment is a property that is independent of the basis used in (3.2).

The physical interpretation is the standard one: when the state of a system constituted by two subsystems A and B is represented by a product state, the properties of the subsystem A are well defined and all given by while those for the subsystem B by . When the system is in an entangled state one typically cannot assign definite properties to the individual subsystems A or B, each subsystem has no independent reality.

To determine whether a state is or not entangled it then suffices to check the rank R of the matrix (see LinearAlgebra:-Rank ): when the state is a product state, otherwise it is an entangled state. When the state being analized belongs to the tensor product of two subspaces, .is equivalent to having the determinant of equal to 0. The condition , however, is more general, and suffices to determine whether a state is a product state also on a Hilbert space that is the tensor product of three or more subspaces: , in which case the matrix M will have more rows and columns and a determinant equal to 0 would only warrant the possibility of factorizing one Ket.

Example: the Bell basis for a system of two qubits

Consider a 2-dimensional space of states acted upon by the operator , and let act upon another, disjointed, Hilbert space that is a replica of the Hilbert space on which acts. Set the dimensions of , and respectively equal to 2, 2 and 2x2 (see Setup)

>

(3.4)

The system C with the two subsystems A and B represents the a two qubits system. The standard basis for C can be constructed in a natural way from the basis of Kets of A and B, , by taking their tensor products:

>

(3.5)

Set a more mathematical display for the imaginary unit

>

The four entangled Bell states also form a basis of C and are given by

>

(3.6)

>

Physics:-Ket(`&Bscr;`, 0) = (Physics:-`*`(Physics:-Ket(A, 0), Physics:-Ket(B, 0))+Physics:-`*`(Physics:-Ket(A, 1), Physics:-Ket(B, 1)))/sqrt(2)

(3.7)

>

Physics:-Ket(`&Bscr;`, 1) = (Physics:-`*`(Physics:-Ket(A, 0), Physics:-Ket(B, 1))+Physics:-`*`(Physics:-Ket(A, 1), Physics:-Ket(B, 0)))/sqrt(2)

(3.8)

>

Physics:-Ket(`&Bscr;`, 2) = I*(Physics:-`*`(Physics:-Ket(A, 0), Physics:-Ket(B, 1))-Physics:-`*`(Physics:-Ket(A, 1), Physics:-Ket(B, 0)))/sqrt(2)

(3.9)

>

Physics:-Ket(`&Bscr;`, 3) = (Physics:-`*`(Physics:-Ket(A, 0), Physics:-Ket(B, 0))-Physics:-`*`(Physics:-Ket(A, 1), Physics:-Ket(B, 1)))/sqrt(2)

(3.10)

There is no standard notation for denoting a Bell state (the linar combinations of the right-hand sides above). The convention used here relates to the definition of the Bell states related to the Pauli matrices shown below. Regardless fo the convention used, this basis is orthonormal. That can be verified by taking dot products, for example:

>

(3.11)

In steps, perform the same operation but using the star (`*`) operator, so that the contraction is represented but not performed

>

(3.12)

Evaluate now the result at `*` = `.`, that is transforming the star product into a dot product

>

(3.13)

>

(3.14)

>

(3.15)

The Bell basis and its relation with the Pauli matrices

The Bell basis can be constructed departing from using the Pauli matrices . For that purpose, using a Vector representation for ,

(3.16)

>

Physics:-Ket(B, 0) = Vector[column](%id = 18446744078301209294), Physics:-Ket(B, 1) = Vector[column](%id = 18446744078301209414)

(3.17)

Multiplying by each of the Pauli Matrices and performing the matrix operations we have

>

[Physics:-`*`(Physics:-Psigma[1], Physics:-Ket(B, 0)) = Physics:-Psigma[1].Vector[column](%id = 18446744078301209294), Physics:-`*`(Physics:-Psigma[2], Physics:-Ket(B, 0)) = Physics:-Psigma[2].Vector[column](%id = 18446744078301209294), Physics:-`*`(Physics:-Psigma[3], Physics:-Ket(B, 0)) = Physics:-Psigma[3].Vector[column](%id = 18446744078301209294)]

(3.18)

>

[Physics:-`*`(Physics:-Psigma[1], Physics:-Ket(B, 0)) = Vector[column](%id = 18446744078376366918), Physics:-`*`(Physics:-Psigma[2], Physics:-Ket(B, 0)) = Vector[column](%id = 18446744078376368838), Physics:-`*`(Physics:-Psigma[3], Physics:-Ket(B, 0)) = Vector[column](%id = 18446744078376358606)]

(3.19)

In this result we see that and flip the state, transforming into , also multiplies the state by the imaginary unit , while leaves the state unchanged.

We can rewrite all that by removeing from (3.19) the Vector representations of (3.17). For that purpose, create a list of substitution equations, replacing the Vectors by the Kets

>

[Vector[column](%id = 18446744078301209294) = Physics:-Ket(B, 0), Vector[column](%id = 18446744078301209414) = Physics:-Ket(B, 1), Vector[column](%id = 18446744078376351494) = I*Physics:-Ket(B, 0), Vector[column](%id = 18446744078376351734) = I*Physics:-Ket(B, 1)]

(3.20)

So the action of in is given by

>

(3.21)

For , the same operations result in

>

[Physics:-`*`(Physics:-Psigma[1], Physics:-Ket(B, 1)) = Physics:-Psigma[1].Vector[column](%id = 18446744078301209414), Physics:-`*`(Physics:-Psigma[2], Physics:-Ket(B, 1)) = Physics:-Psigma[2].Vector[column](%id = 18446744078301209414), Physics:-`*`(Physics:-Psigma[3], Physics:-Ket(B, 1)) = Physics:-Psigma[3].Vector[column](%id = 18446744078301209414)]

(3.22)

>

[Physics:-`*`(Physics:-Psigma[1], Physics:-Ket(B, 1)) = Vector[column](%id = 18446744078464860518), Physics:-`*`(Physics:-Psigma[2], Physics:-Ket(B, 1)) = Vector[column](%id = 18446744078464862438), Physics:-`*`(Physics:-Psigma[3], Physics:-Ket(B, 1)) = Vector[column](%id = 18446744078464856182)]

(3.23)

>

(3.24)

To obtain the other three Bell states using the results (3.21) and (3.24), indicate to the system that the Pauli matrices operate in the subspace where operates

>

(3.25)

Multiplying given in (3.7) by each of the three we get the other three Bell states

>

Physics:-Ket(`&Bscr;`, 0) = (1/2)*2^(1/2)*(Physics:-`*`(Physics:-Ket(A, 0), Physics:-Ket(B, 0))+Physics:-`*`(Physics:-Ket(A, 1), Physics:-Ket(B, 1)))

(3.26)

>

Physics:-`*`(Physics:-Psigma[1], Physics:-Ket(`&Bscr;`, 0)) = (1/2)*2^(1/2)*Physics:-`*`(Physics:-Psigma[1], Physics:-`*`(Physics:-Ket(A, 0), Physics:-Ket(B, 0))+Physics:-`*`(Physics:-Ket(A, 1), Physics:-Ket(B, 1)))

(3.27)

Substitute in this result the first equations of (3.21) and (3.24)

>

(3.28)

>

(3.29)

>

Physics:-`*`(Physics:-Psigma[1], Physics:-Ket(`&Bscr;`, 0)) = (1/2)*2^(1/2)*Physics:-`*`(Physics:-Psigma[1], Physics:-`*`(Physics:-Ket(A, 0), Physics:-`*`(Physics:-Psigma[1], Physics:-Ket(B, 1)))+Physics:-`*`(Physics:-Ket(A, 1), Physics:-`*`(Physics:-Psigma[1], Physics:-Ket(B, 0))))

(3.30)

>

Physics:-`*`(Physics:-Psigma[1], Physics:-Ket(`&Bscr;`, 0)) = (1/2)*2^(1/2)*(Physics:-`*`(Physics:-Ket(A, 0), Physics:-Ket(B, 1))+Physics:-`*`(Physics:-Ket(A, 1), Physics:-Ket(B, 0)))

(3.31)

This is defined in (3.8)

>

Physics:-Ket(`&Bscr;`, 1) = (1/2)*2^(1/2)*(Physics:-`*`(Physics:-Ket(A, 0), Physics:-Ket(B, 1))+Physics:-`*`(Physics:-Ket(A, 1), Physics:-Ket(B, 0)))

(3.32)

>

(3.33)

Multiplying now by and substituting using the equations of (3.21) and (3.24) we get

>

Physics:-`*`(Physics:-Psigma[2], Physics:-Ket(`&Bscr;`, 0)) = (1/2)*2^(1/2)*Physics:-`*`(Physics:-Psigma[2], Physics:-`*`(Physics:-Ket(A, 0), Physics:-Ket(B, 0))+Physics:-`*`(Physics:-Ket(A, 1), Physics:-Ket(B, 1)))

(3.34)

>

(3.35)

>

(3.36)

>

(3.37)

The above is defined in (3.9)

>

(3.38)

>

(3.39)

Finally, multiplying by

>

Physics:-`*`(Physics:-Psigma[3], Physics:-Ket(`&Bscr;`, 0)) = (1/2)*2^(1/2)*Physics:-`*`(Physics:-Psigma[3], Physics:-`*`(Physics:-Ket(A, 0), Physics:-Ket(B, 0))+Physics:-`*`(Physics:-Ket(A, 1), Physics:-Ket(B, 1)))

(3.40)

Substituting

>

(3.41)

>

(3.42)

We get

>

Physics:-`*`(Physics:-Psigma[3], Physics:-Ket(`&Bscr;`, 0)) = (1/2)*2^(1/2)*(Physics:-`*`(Physics:-Ket(A, 0), Physics:-Ket(B, 0))-Physics:-`*`(Physics:-Ket(A, 1), Physics:-Ket(B, 1)))

(3.43)

which is

>

Physics:-Ket(`&Bscr;`, 3) = (1/2)*2^(1/2)*(Physics:-`*`(Physics:-Ket(A, 0), Physics:-Ket(B, 0))-Physics:-`*`(Physics:-Ket(A, 1), Physics:-Ket(B, 1)))

(3.44)

>

(3.45)

Entangled States, Operators and Projectors

Consider a fourth operator, , that is Hermitian and acts on the same space of , and then it has the same dimension,

>

[disjointedspaces = {{A, C, H}, {B, C, H}, {B, C, Physics:-Psigma}}, hermitianoperators = {H}, quantumbasisdimension = {A = 2, B = 2, C[1] = 2, C[2] = 2, H[1] = 2, H[2] = 2}]

(4.1)

To operate in a practical way with these operators, Bras and Kets, however, bracket rules reflecting their relationship are necessary. From the definition of as acting on the tensor product of spaces where and act (see (3.2)) and taking into account the dimensions specified for , and we have

>

Physics:-Ket(C, a, b) = Sum(Sum(M[a, j, b, p]*Physics:-`*`(Physics:-Ket(A, j), Physics:-Ket(B, p)), j = 0 .. 1), p = 0 .. 1)

(4.2)

>

Physics:-Bracket(Physics:-Bra(A, k), Physics:-Ket(C, a, b)) = Sum(M[a, k, b, p]*Physics:-Ket(B, p), p = 0 .. 1)

(4.3)

>

Physics:-Bracket(Physics:-Bra(B, k), Physics:-Ket(C, a, b)) = Sum(M[a, j, b, k]*Physics:-Ket(A, j), j = 0 .. 1)

(4.4)

>

(4.5)

The bracket rules for , and are the first two of these; Set these rules, so that the system can take them into account

>

[bracketrules = {%Bracket(%Bra(A, k), %Ket(C, a, b)) = Sum(M[a, k, b, p]*Physics:-Ket(B, p), p = 0 .. 1), %Bracket(%Bra(B, k), %Ket(C, a, b)) = Sum(M[a, j, b, k]*Physics:-Ket(A, j), j = 0 .. 1)}]

(4.6)

If we now recompute (4.5), the left-hand side is also computed

>

(4.7)

>

(4.8)

Suppose now that you want to compute with the Hermitian operator , that operates on the same space as , both using C using the operators and , as in

where = when is a product (not entagled) state.

For it suffices to set a bracket rule

>

[bracketrules = {%Bracket(%Bra(A, k), %Ket(C, a, b)) = Sum(M[a, k, b, p]*Physics:-Ket(B, p), p = 0 .. 1), %Bracket(%Bra(B, k), %Ket(C, a, b)) = Sum(M[a, j, b, k]*Physics:-Ket(A, j), j = 0 .. 1), %Bracket(%Bra(C, a, b), H, %Ket(C, c, d)) = `&Hscr;`[a, b, c, d]}, realobjects = {`&Hscr;`, x, y, z}]

(4.9)

After that, the system operates taking the rule into account

>

(4.10)

Regarding , since belongs to the tensor product of spaces A and B, it can be an entangled operator, one that you cannot represent just as a product of one operator acting on A times another one acting on B. A computational representation for the operator (that is not just itself or as abstract) is not possible in the general case. For that you can use a different feature: define the action of the operator on Kets of and .

Basically, we want:

A program sketch for that would be:

if H is applied to a Ket of A or B then

    if H itself is indexed then
        return H accumulating its indices, followed by the index of the Ket
    else

return H indexed by the index of the Ket;
otherwise
return the dot product operation uncomputed, unevaluated

In Maple language, that program-sketch becomes

>

"H := K -> if K::Ket and op(1, K)::'identical(A,B)' then if procname::'indexed' then if nops(procname) <4 then H[op(procname), op(2, K)] #` accumulate indices` else 'H . K' fi else H[op(2, K)] fi else 'procname . K' fi:"

Let's see it in action. Start erasing the Physics performance remember tables, that remember results like computed before the definition of

>

(4.11)

Recalling that is Hermitian,

>

(4.12)

>

(4.13)

>

(4.14)

>

(4.15)

Note that the definition of as a procedure does not interfer with the setting of an bracket rule for it with , that is still working

>

(4.16)

but the definition takes precedence, so if in it you indicate what to do with a Ket, that will be taken into account before the bracket rule. Finally, In the typical case, the first four results, (4.11), (4.12), (4.13) and (4.14) are operators while (4.15) is a scalar; you can always represent the scalar aspect by substituing the noncommutative operator by a related scalar, say H.

•	You can set the projectors for all these operators / spaces. For example,

>

`&Iopf;__A` := Projector(Ket(A, i)); `&Iopf;__B` := Projector(Ket(B, i)); `&Iopf;__C` := Projector(Ket(C, a, b))

Sum(Physics:-`*`(Physics:-Ket(A, n), Physics:-Bra(A, n)), n = 0 .. 1)

Sum(Physics:-`*`(Physics:-Ket(B, n), Physics:-Bra(B, n)), n = 0 .. 1)

Sum(Sum(Physics:-`*`(Physics:-Ket(C, a, b), Physics:-Bra(C, a, b)), a = 0 .. 1), b = 0 .. 1)

(4.17)

Since the algebra rules for computing with eigenkets of , and were already set in (4.6), from the projectors above you can construct any subspace projector, for example

>

Sum(Sum(Sum(M[a, m, b, p]*Physics:-`*`(Physics:-Ket(B, p), Physics:-Bra(C, a, b)), p = 0 .. 1), a = 0 .. 1), b = 0 .. 1)

(4.18)

>

Sum(Sum(Sum(conjugate(M[a, m, b, p])*Physics:-`*`(Physics:-Ket(C, a, b), Physics:-Bra(B, p)), p = 0 .. 1), a = 0 .. 1), b = 0 .. 1)

(4.19)

The conjugate of is due to the contraction or attachment from the right of (4.18), that is with

>

Physics:-Bra(C, a, b) = Sum(Sum(conjugate(M[a, j, b, p])*Physics:-`*`(Physics:-Bra(A, j), Physics:-Bra(B, p)), j = 0 .. 1), p = 0 .. 1)

(4.20)

The coefficients satisfy constraints due to the normalization of Kets of and . One can derive these contraints by inserting the unit operator constructing this identity

Sum(Sum(Physics:-`*`(Physics:-Ket(C, a, b), Physics:-Bra(C, a, b)), a = 0 .. 1), b = 0 .. 1)

(4.21)

>

Sum(Sum(conjugate(M[a, r, b, s])*M[a, m, b, n], a = 0 .. 1), b = 0 .. 1) = Physics:-KroneckerDelta[m, r]*Physics:-KroneckerDelta[n, s]

(4.22)

Transform this result into a function P to explore the identity further

>

proc (m, n, r, s) options operator, arrow; sum(sum(conjugate(M[a, r, b, s])*M[a, m, b, n], a = 0 .. 1), b = 0 .. 1) = Physics:-KroneckerDelta[m, r]*Physics:-KroneckerDelta[n, s] end proc

(4.23)

The first and third indices refer to the quantum numbers of , the second and fourth to , so the the right-hand sides in the following are respectively 1 and 0

>

(4.24)

>

(4.25)

To get the whole system of equations satisfied by the coefficients , use P to construct an Array with four indices running from 0..1

>

_rtable[18446744078376377150]

(4.26)

Convert the whole Array into a set of equations

>

${abs(M[0, 0, 0, 0])^2+abs(M[1, 0, 0, 0])^2+abs(M[0, 0, 1, 0])^2+abs(M[1, 0, 1, 0])^2 = 1, abs(M[0, 0, 0, 1])^2+abs(M[1, 0, 0, 1])^2+abs(M[0, 0, 1, 1])^2+abs(M[1, 0, 1, 1])^2 = 1, abs(M[0, 1, 0, 0])^2+abs(M[1, 1, 0, 0])^2+abs(M[0, 1, 1, 0])^2+abs(M[1, 1, 1, 0])^2 = 1, abs(M[0, 1, 0, 1])^2+abs(M[1, 1, 0, 1])^2+abs(M[0, 1, 1, 1])^2+abs(M[1, 1, 1, 1])^2 = 1, conjugate(M[0, 0, 0, 0])*M[0, 0, 0, 1]+conjugate(M[1, 0, 0, 0])*M[1, 0, 0, 1]+conjugate(M[0, 0, 1, 0])*M[0, 0, 1, 1]+conjugate(M[1, 0, 1, 0])*M[1, 0, 1, 1] = 0, conjugate(M[0, 0, 0, 0])*M[0, 1, 0, 0]+conjugate(M[1, 0, 0, 0])*M[1, 1, 0, 0]+conjugate(M[0, 0, 1, 0])*M[0, 1, 1, 0]+conjugate(M[1, 0, 1, 0])*M[1, 1, 1, 0] = 0, conjugate(M[0, 0, 0, 0])*M[0, 1, 0, 1]+conjugate(M[1, 0, 0, 0])*M[1, 1, 0, 1]+conjugate(M[0, 0, 1, 0])*M[0, 1, 1, 1]+conjugate(M[1, 0, 1, 0])*M[1, 1, 1, 1] = 0, conjugate(M[0, 0, 0, 1])*M[0, 0, 0, 0]+conjugate(M[1, 0, 0, 1])*M[1, 0, 0, 0]+conjugate(M[0, 0, 1, 1])*M[0, 0, 1, 0]+conjugate(M[1, 0, 1, 1])*M[1, 0, 1, 0] = 0, conjugate(M[0, 0, 0, 1])*M[0, 1, 0, 0]+conjugate(M[1, 0, 0, 1])*M[1, 1, 0, 0]+conjugate(M[0, 0, 1, 1])*M[0, 1, 1, 0]+conjugate(M[1, 0, 1, 1])*M[1, 1, 1, 0] = 0, conjugate(M[0, 0, 0, 1])*M[0, 1, 0, 1]+conjugate(M[1, 0, 0, 1])*M[1, 1, 0, 1]+conjugate(M[0, 0, 1, 1])*M[0, 1, 1, 1]+conjugate(M[1, 0, 1, 1])*M[1, 1, 1, 1] = 0, conjugate(M[0, 1, 0, 0])*M[0, 0, 0, 0]+conjugate(M[1, 1, 0, 0])*M[1, 0, 0, 0]+conjugate(M[0, 1, 1, 0])*M[0, 0, 1, 0]+conjugate(M[1, 1, 1, 0])*M[1, 0, 1, 0] = 0, conjugate(M[0, 1, 0, 0])*M[0, 0, 0, 1]+conjugate(M[1, 1, 0, 0])*M[1, 0, 0, 1]+conjugate(M[0, 1, 1, 0])*M[0, 0, 1, 1]+conjugate(M[1, 1, 1, 0])*M[1, 0, 1, 1] = 0, conjugate(M[0, 1, 0, 0])*M[0, 1, 0, 1]+conjugate(M[1, 1, 0, 0])*M[1, 1, 0, 1]+conjugate(M[0, 1, 1, 0])*M[0, 1, 1, 1]+conjugate(M[1, 1, 1, 0])*M[1, 1, 1, 1] = 0, conjugate(M[0, 1, 0, 1])*M[0, 0, 0, 0]+conjugate(M[1, 1, 0, 1])*M[1, 0, 0, 0]+conjugate(M[0, 1, 1, 1])*M[0, 0, 1, 0]+conjugate(M[1, 1, 1, 1])*M[1, 0, 1, 0] = 0, conjugate(M[0, 1, 0, 1])*M[0, 0, 0, 1]+conjugate(M[1, 1, 0, 1])*M[1, 0, 0, 1]+conjugate(M[0, 1, 1, 1])*M[0, 0, 1, 1]+conjugate(M[1, 1, 1, 1])*M[1, 0, 1, 1] = 0, conjugate(M[0, 1, 0, 1])*M[0, 1, 0, 0]+conjugate(M[1, 1, 0, 1])*M[1, 1, 0, 0]+conjugate(M[0, 1, 1, 1])*M[0, 1, 1, 0]+conjugate(M[1, 1, 1, 1])*M[1, 1, 1, 0] = 0}$

(4.27)

	Reference

>

Download Tensor_Products_of_Quantum_States_-_2018.mw

Edgardo S. Cheb-Terrab
Physics, Differential Equations and Mathematical Functions, Maplesoft

Manipulator with variable length of the last link....

by: one man 1355

December 28 2018

2 1

It can be considered as continuation of these topics: “Determination of the angles of the manipulator with the help of its mathematical model. Inverse problem.” and “The use of manipulators as multi-axis CNC machines”.
There is a simple two-link manipulator with three degrees of freedom. We change its last link with a fixed length to a variable length link. By this action we added one degree of freedom to our manipulator. Now we have a two-link manipulator with 4 degrees of freedom.
In a particular mathematical model the variable length of the link is related to the x7, and in the figure the total length of the last link is displayed as the result of subtracting the fixed part of the link (L2) from x7 (equation f2). At the same time, the value of the variable x7 depends on the inclination of the first link (equation f4). x1, x2, x3 are the coordinates of the moving point of the first link, x4, x5, x6 are the coordinates of the operating point. The equation f2 defines the type of connection between the links, the equations f5 and f6 are the trajectory of the working point.

MAN_2_4_Variable_length_MP.mw

Three bucket problem and its generalization

by: Kitonum 21425

December 24 2018

3 3

Here is a classic puzzle:
You are camping, and have an 8-liter bucket which is full of fresh water. You need to share this water fairly into exactly two portions (4 + 4 liters). But you only have two empty buckets: a 5-liter and a 3-liter. Divide the 8 liters in half in as short a time as possible.

This is not an easy task and requires at least 7 transfusions to solve it.

The procedure Pouring solves a similar problem for the general case. Given n buckets of known volume and the amount of water in each bucket is known. Buckets can be partially filled, be full or be empty (of course the case when all is empty or all is full is excluded). With each individual transfusion, the bucket from which it is poured must be completely free, or the bucket into which it is poured must be completely filled. It is forbidden to pour water anywhere other than the indicated buckets.

Formal parameters of the procedure: BucketVolumes is a list of bucket volumes, WaterVolumes is a list of water volumes in these buckets. The procedure returns all possible states that can occur during transfusions in the form of a tree (the initial state WaterVolumes is its root).

restart;
Pouring:=proc(BucketVolumes::list(And(positive,{integer,float,fraction})),WaterVolumes::list(And(nonnegative,{integer,float,fraction})), Output:=graph)
local S, W, n, N, OneStep, j, v, H, G;
uses ListTools, GraphTheory;

n:=nops(BucketVolumes); 
if nops(WaterVolumes)<>n then error "The lists should be the same length" fi;
if n<2 then error "Must have at least 2 buckets" fi;
if not `or`(op(WaterVolumes>~0)) then error "There must be at least one non-empty bucket" fi;
if BucketVolumes=WaterVolumes then error "At least one bucket should not be full" fi;
if not `and`(seq(WaterVolumes[i]<=BucketVolumes[i], i=1..n)) then error "The amount of water in each bucket cannot exceed its volume" fi;
W:=[[WaterVolumes]];

OneStep:=proc(W)
local w, k, i, v, V, k1, v0;
global L;
L:=convert(Flatten(W,1), set);
k1:=0; 
for w in W do
k:=0; v:='v';
for i from 1 to n do
for j from 1 to n do
if i<>j and w[-1][i]<>0 and w[-1][j]<BucketVolumes[j] then k:=k+1; v[k]:=subsop(i=`if`(w[-1][i]<=BucketVolumes[j]-w[-1][j],0,w[-1][i]-(BucketVolumes[j]-w[-1][j])),j=`if`(w[-1][i]<=BucketVolumes[j]-w[-1][j],w[-1][j]+w[-1][i],BucketVolumes[j]),w[-1]); fi;
od; 
od; 
v:=convert(v,list);
if `and`(seq(v0 in L, v0=v)) then k1:=k1+1; V[k1]:=w else 
for v0 in v do  
if not (v0 in L) then k1:=k1+1; V[k1]:=[op(w),v0] fi;
od;
fi;
L:=L union convert(v,set);
od;
convert(V,list);
end proc:

S[0]:={};
for N from 1 do
H[N]:=(OneStep@@N)(W);
S[N]:=L;
if S[N-1]=S[N] then break fi;
od;
if Output=set then return L else
if Output=trails then interface(rtablesize=infinity);
return <H[N-1]> else
G:=Graph(seq(Trail(map(t->t[2..-2],convert~(h,string))),h=H[N-1]));
DrawGraph(G, style=tree, root=convert(WaterVolumes,string)[2..-2], stylesheet = [vertexcolor = "Yellow", vertexfont=[TIMES,20]], size=[800,500])  fi; fi;

end proc:

Examples of use:

Here is the solution to the original puzzle above. We see that at least 7 transfusions are
required to get equal volumes (4 + 4) in two buckets

Pouring([8,5,3], [8,0,0]);

With an increase in the number of buckets, the number of solutions is extremely
increased. Here is the solution to the problem: is it possible to equalize the amount of water (7+7+7+7) in the following example?

Pouring([14,10,9,9],[14,10,4,0]);
S:=Pouring([14,10,9,9],[14,10,4,0], set);
is([7,7,7,7] in S);
nops(S);

Download Pouring.mw

Musings on Package Defaults

by: Joe Riel 9660 Product: Maple

December 23 2018

4 3

Am pondering how to best provide user-configurable options for a few packages I've written. The easiest method is to use global variables, preassign their default values during the package definition (but don't protect them) and save them with the mla used for the package. A user could then assign new values, say in their Maple initialization file or in a worksheet. For example

  FooDefaultBar := true:
  FooDefaultBaz := false:

That works for a few variables, but is unwieldy if there are many, as the names generally have to be long and verbose to avoid accidental collision. Better may be to use a single record

  FooDefaults := Record('Bar' = true, 'Baz' = false):

To change one or more values, the user could do

   use FooDefaults in
      Bar := false;
   end use:

A drawback of using a global variable or record is that the user can assign any type to the variable, so the using program will have to check it. While one could use a record with typed fields, for example,

  FooDefaults := Record('Bar' :: truefalse = true, 'Baz' :: truefalse := false):

that only has an effect on assignments if kernelopts(assertlevel) is 2, which isn't the default.

A different approach is to use a Maple object to handle configuration variables. The object should be defined separate from the package it is configuring, so that the target package doesn't have to be loaded to customize its configuration. I've created a small object for this, but am not satisfied with its usage. Here is how it is currently used

# Create configuration object for package foo
Configure('fooDefaults', 'Bar' :: truefalse = true, 'Baz' :: truefalse = false):

The Assign method is used to reassign one or more fields

Assign(fooDefaults, 'Bar' = false, 'Baz' = true):

If a value does not match the declared type, an error is raised. Values from the object are available via the index operator:

   fooDefaults['Bar'];

Am not wild about this approach, the assignment seems clunky and would require a user to consult a help page to learn about the existence of the Assign method, though that would probably be necessary, regardless, to learn about the defaults themselves. Any thoughts on improvements? Attached is the current code.

Configure := module()

option object;

local Default # record of values
    , Type    # record of types
    , nomen   # string corresponding to name of assigned object
    , all :: static := {}
    ;

export
    ModuleApply :: static := proc()
        Object(Configure, _passed);
    end proc;

export
    ModuleCopy :: static := proc(self :: Configure
                                 , proto :: Configure
                                 , nm :: name
                                 , defaults :: seq(name :: type = anything)
                                 , $
                                )
    local eq;
        self:-Default := Record(defaults);
        self:-Type    := Record(seq(op([1,1], eq) = op([1,2], eq), eq = [defaults]));
        self:-nomen   := convert(nm,'`local`');
        nm := self;
        protect(nm);
        self:-all := {op(self:-all), self:-nomen};
        nm;
    end proc;

export
    ModulePrint :: static := proc(self :: Configure)
    local default;
        if self:-Default :: 'record' then
            self:-nomen(seq(default = self:-Default[default]
                            , default = exports(self:-Default)
                           ));
        else
            self:-nomen();
        end if;
    end proc;

export
    Assign :: static := proc(self :: Configure
                             , eqs :: seq(name = anything)
                             , $
                            )
    local eq, nm, val;
        # Check eqs
        for eq in [eqs] do
            (nm, val) := op(eq);
            if not assigned(self:-Default[nm]) then
                error "%1 is not a default of %2", nm, self:-nomen;
            elif not val :: self:-Type[nm] then
                error ("%1 must be of type %2, received %3"
                       , nm, self:-Type[nm], val);
            end if;
        end do;
        # Assign defaults
        for eq in [eqs] do
            (nm, val) := op(eq);
            self:-Default[nm] := val;
        end do;
        self;
    end proc;

export
    `?[]` :: static := proc(self :: Configure
                            , indx :: list
                            , val :: list
                           )
    local opt;
        opt := op(indx);
        if not assigned(self:-Default[opt]) then
            error "'%0' is not an assigned field of this Configure object", indx[];
        elif nargs = 2 then
            self:-Default[opt];
        elif not val :: [self:-Type[opt]] then
            error "value for %1 must be of type %2", opt, self:-Type[opt];
        else
            self:-Default[opt] := op(val);
        end if;
    end proc;

export
    ListAll :: static := proc(self :: Configure)
        self:-all;
    end proc;

end module:

Later: Observing that this is just a glorified record with an assurance that the values match their declared types, but with less nice methods to set and get the values, I concluded that what I really want is a record that enforces types regardless the setting of . Maybe created with

   FooDefaults := Record[strict]('Bar' :: truefalse = true, 'Baz :: truefalse = false):

In the meantime, I'll probably just use a record and not worry about whether a user has assigned an invalid value.

The one way of rolling surface. Rolling without...

by: one man 1355 Product: Maple 17

December 20 2018

1 3

On the convex part of the surface we place a curve (not necessarily flat, as in this case). We divide this curve into segments of equal length (in the text Ls [i]) and divide the path that our surface will roll (in the text L [i]) into segments of the same length as segments of curve. Take the next segment of the trajectory L [i] and the corresponding segment on the curve Ls [i], calculate the angles between them. After that, we perform well-known transformations that place the curve in the space so that the segment Ls [i] coincides with the segment L [i]. At the same time, we perform exactly the same transformations with the equation of surface.

For example, the ellipsoid rolls on the oX1 axis, and each position of the ellipsoid in space corresponds to the equation in the figure.
Rolling_of_surface.mw

And similar examples:

Exact solutions for PDE and Boundary / Initial...

by: ecterrab 14535 Product: Maple

December 19 2018

11 0

Exact solutions for PDE and Boundary / Initial Conditions

Significant developments happened during 2018 in Maple's ability for the exact solving of PDE with Boundary / Initial conditions. This is work in collaboration with Katherina von Bülow. Part of these developments were mentioned in previous posts. The project is still active but it's December, time to summarize.

First of all thanks to all of you who provided feedback. The new functionality is described below, in 11 brief Sections, with 30 selected examples and a few comments. A worksheet with this contents is linked at the end of this post. Some of these improvements appeared first in 2018.1, then in 2018.2, but other ones are posterior. To reproduce the input/output below in Maple 2018.2.1, the latest Maplesoft Physics Updates (version 269 or higher) needs to be installed.

1. PDE and BC problems solved using linear change of variables

PDE and BC problems often require that the boundary and initial conditions be given at certain evaluation points (usually in which one of the variables is equal to zero). Using linear changes of variables, however, it is possible to change the evaluation points of BC, obtaining the solution for the new variables, and then changing back to the original variables. This is now automatically done by the pdsolve command.

Example 1: A heat PDE & BC problem in a semi-infinite domain:

>

Note the evaluation points A and B. The method typically described in textbooks requires the evaluation points to be . The change of variables automatically used in this case is:

>

(1)

so that pdsolve's task becomes solving this other problem, now with the appropriate evaluation points

>	$PDEtools:-dchange(transformation, [pde__1, iv__1], {tau, upsilon, xi})$

[diff(upsilon(xi, tau), tau) = (1/4)*(diff(diff(upsilon(xi, tau), xi), xi)), upsilon(0, tau) = 0, upsilon(xi, 0) = 10]

(2)

and then changing the variables back to the original {x, t, u} and giving the solution. The process all in one go:

>

(3)

Example 2: A heat PDE with a source and a piecewise initial condition

>

iv__2 := u(x, 1) = piecewise(0 <= x, 0, x < 0, 1)

>

u(x, t) = 3/2-(1/2)*erf((1/2)*x/(mu^(1/2)*(t-1)^(1/2)))-t

(4)

Example 3: A wave PDE & BC problem in a semi-infinite domain:

>

u(x, t) = (1/2)*exp(-(-x+t+5)^2)+(1/2)*exp(-(-x+t-7)^2)+(1/2)*exp(-(x+t-7)^2)+(1/2)*exp(-(x+t+5)^2)+(1/2)*t-1/2

(5)

Example 4: A wave PDE & BC problem in a semi-infinite domain:

>

u(x, t) = piecewise((1/2)*t < x-1, (1/2)*exp(-(1/4)*(t+2*x)^2)+(1/2)*exp(-(1/4)*(t-2*x)^2), x-1 < (1/2)*t, (1/2)*exp(-(1/4)*(t+2*x)^2)+(1/2)*exp(-(1/4)*(t-2*x+4)^2))

(6)

Example 5: A wave PDE with a source:

>

u(x, t) = (1/2)*(Int(Int((diff(diff(h(zeta), zeta), zeta))*c^2*tau+(diff(diff(g(zeta), zeta), zeta))*c^2+f(zeta, tau+1), zeta = (-t+tau+1)*c+x .. x+c*(t-1-tau)), tau = 0 .. t-1)+(2*t-2)*c*h(x)+2*g(x)*c)/c

(7)

>

(8)

2. It is now possible to specify or exclude method(s) for solving

The pdsolve/BC solving methods can now be indicated, either to be used for solving, as in to be tried in the indicated order, or to be excluded, as in . The methods and sub-methods available are organized in a table,

>

(9)

So, for example, the methods for PDEs of first order and second order are, respectively,

>

(10)

>

(11)

Some methods have sub-methods (their existence is visible in (9)):

>

(12)

>

(13)

Example 6:

>

pde__6 := diff(u(r, theta), r, r)+diff(u(r, theta), theta, theta) = 0

>

(14)

>

u(r, theta) = ((3/2)*I)*exp(2*r-4-(2*I)*theta)-((3/2)*I)*exp(-2*r+4+(2*I)*theta)+1

(15)

Example 7:

>

(16)

>

(17)

>

u(x, y) = (1/2)*(Int(exp(-s*y+I*s*x), s = -infinity .. infinity))/Pi

(18)

>

(19)

3. Series solutions for linear PDE and BC problems solved via product separation with eigenvalues that are the roots of algebraic expressions which cannot be inverted

Linear problems for which the PDE can be separated by product, giving rise to Sturm-Liouville problems for the separation constant (eigenvalue) and separated functions (eigenfunctions), do not always result in solvable equations for the eigenvalues. Below are examples where the eigenvalues are respectively roots of a sum of functions and of the non-inversible equation .

Example 8: This problem represents the temperature distribution in a thin circular plate whose lateral surfaces are insulated (Articolo example 6.9.2):

>

pde__8 := diff(u(r, theta, t), t) = (diff(u(r, theta, t), r)+r*(diff(u(r, theta, t), r, r))+(diff(u(r, theta, t), theta, theta))/r)/(25*r)

>

$u(r, theta, t) = `casesplit/ans`(Sum(-(4/3)*BesselJ(1, lambda[n]*r)*sin(theta)*exp(-(1/25)*lambda[n]^2*t)*(BesselJ(0, lambda[n])*lambda[n]^3-BesselJ(1, lambda[n])*lambda[n]^2+4*lambda[n]*BesselJ(0, lambda[n])-8*BesselJ(1, lambda[n]))/(lambda[n]^3*(BesselJ(0, lambda[n])^2*lambda[n]+BesselJ(1, lambda[n])^2*lambda[n]-2*BesselJ(0, lambda[n])*BesselJ(1, lambda[n]))), n = 0 .. infinity), {And(-BesselJ(1, lambda[n])+BesselJ(2, lambda[n])*lambda[n] = 0, 0 < lambda[n])})$

(20)

In the above we see that the eigenvalue satisfies . When is the root of one single BesselJ or BesselY function of integer order, the Maple functions BesselJZeros and BesselYZeros are used instead. That is the case, for instance, if we slightly modify this problem changing the first boundary condition to be instead of

>

$u(r, theta, t) = `casesplit/ans`(Sum(-(4/3)*BesselJ(1, lambda[n]*r)*sin(theta)*exp(-(1/25)*lambda[n]^2*t)*(lambda[n]^2+4)/(BesselJ(0, lambda[n])*lambda[n]^3), n = 1 .. infinity), {And(lambda[n] = BesselJZeros(1, n), 0 < lambda[n])})$

(21)

Example 9: This problem represents the temperature distribution in a thin rod whose left end is held at a fixed temperature of 5 and whose right end loses heat by convection into a medium whose temperature is 10. There is also an internal heat source term in the PDE (Articolo's textbook, example 8.4.3):

>

$u(x, t) = `casesplit/ans`(Sum(piecewise(lambda[n] = 0, 0, (80/3)*exp(-(1/20)*lambda[n]^2*t)*sin(lambda[n]*x)*(lambda[n]^2*cos(lambda[n])+lambda[n]*sin(lambda[n])+4*cos(lambda[n])-4)/(lambda[n]^2*(sin(2*lambda[n])-2*lambda[n]))), n = 0 .. infinity)+Int(Sum(piecewise(lambda[n] = 0, 0, 4*exp(-(1/20)*lambda[n]^2*(t-tau))*sin(lambda[n]*x)*tau*(cos(lambda[n])-1)/(sin(2*lambda[n])-2*lambda[n])), n = 0 .. infinity), tau = 0 .. t)+(5/2)*x+5, {And(tan(lambda[n])+lambda[n] = 0, 0 < lambda[n])})$

(22)

For information on how to test or plot a solution like the one above, please see the end of the Mapleprimes post "Sturm-Liouville problem with eigenvalues that are the roots of algebraic expressions which cannot be inverted"

4. Superposition method for linear PDE with more than one non-homogeneous BC

Previously, for linear homogeneous PDE problems with non-periodic initial and boundary conditions, pdsolve was only consistently able to solve the problem as long as at most one of those conditions was non-homogeneous. The superposition method works by taking advantage of the linearity of the problem and the fact that the solution to such a problem in which two or more of the BC are non-homogeneous can be given as

u = + ..., where each is a solution of the PDE with all but one of the BC homogenized.

Example 10: A Laplace PDE with one homogeneous and three non-homogeneous conditions:

>

u(x, y) = ((exp(2*Pi)-1)*(Sum((-1)^n*n*(exp(2*Pi)-1)*exp(n*(Pi-y)-Pi)*sin(n*x)*(exp(2*n*y)-1)/(Pi*(n^2+1)*(exp(2*Pi*n)-1)), n = 1 .. infinity))+(exp(2*Pi)-1)*(Sum(2*sin(n*y)*exp(n*(Pi-x))*n*sinh(Pi)*((-1)^n+1)*(exp(2*n*x)-1)/(Pi*(exp(2*Pi*n)-1)*(n^2-1)), n = 2 .. infinity))+sin(x)*(exp(-y+2*Pi)-exp(y)))/(exp(2*Pi)-1)

(23)

5. Polynomial solutions method:

This new method gives pdsolve better performance when the PDE & BC problems admit polynomial solutions.

Example 11:

>

(24)

6. Solving more problems using the Laplace transform or the Fourier transform

These methods now solve more problems and are no longer restricted to PDE of first or second order.

Example 12: A third order PDE & BC problem:

>

u(x, t) = (1/4)*(Int((4/3)*Pi*f(-zeta)*(-(x+zeta)/(-t)^(1/3))^(1/2)*BesselK(1/3, -(2/9)*3^(1/2)*(x+zeta)*(-(x+zeta)/(-t)^(1/3))^(1/2)/(-t)^(1/3))/(-t)^(1/3), zeta = -infinity .. infinity))/Pi^2

(25)

Example 13: A PDE & BC problem that is solved using Laplace transform:

>

(26)

To see the computational flow, the solving methods used and in which order they are tried use

>

(27)

Example 14:

>

* trying method "SpecializeArbitraryFunctions" for 2nd order PDEs
   -> trying "LinearInXT"
   -> trying "HomogeneousBC"
* trying method "SpecializeArbitraryConstants" for 2nd order PDEs
* trying method "Wave" for 2nd order PDEs
   -> trying "Cauchy"
   -> trying "SemiInfiniteDomain"
   -> trying "WithSourceTerm"
* trying method "Heat" for 2nd order PDEs
   -> trying "SemiInfiniteDomain"
   -> trying "WithSourceTerm"
* trying method "Series" for 2nd order PDEs
   -> trying "ThreeBCsincos"
   -> trying "FourBC"
   -> trying "ThreeBC"
   -> trying "ThreeBCPeriodic"
   -> trying "WithSourceTerm"
      * trying method "SpecializeArbitraryFunctions" for 2nd order PDEs
         -> trying "LinearInXT"
         -> trying "HomogeneousBC"
            Trying travelling wave solutions as power series in tanh ...
               Trying travelling wave solutions as power series in ln ...
      * trying method "SpecializeArbitraryConstants" for 2nd order PDEs
         Trying travelling wave solutions as power series in tanh ...
            Trying travelling wave solutions as power series in ln ...
      * trying method "Wave" for 2nd order PDEs
         -> trying "Cauchy"
         -> trying "SemiInfiniteDomain"
         -> trying "WithSourceTerm"
      * trying method "Heat" for 2nd order PDEs
         -> trying "SemiInfiniteDomain"
         -> trying "WithSourceTerm"
      * trying method "Series" for 2nd order PDEs
         -> trying "ThreeBCsincos"
         -> trying "FourBC"
         -> trying "ThreeBC"
         -> trying "ThreeBCPeriodic"
         -> trying "WithSourceTerm"
         -> trying "ThreeVariables"
      * trying method "Laplace" for 2nd order PDEs
         -> trying a Laplace transformation
      * trying method "Fourier" for 2nd order PDEs
         -> trying a fourier transformation

      * trying method "Generic" for 2nd order PDEs
         -> trying a solution in terms of arbitrary constants and functions to be adjusted to the given initial conditions
      * trying method "PolynomialSolutions" for 2nd order PDEs

      * trying method "LinearDifferentialOperator" for 2nd order PDEs
      * trying method "Superposition" for 2nd order PDEs
   -> trying "ThreeVariables"
* trying method "Laplace" for 2nd order PDEs
   -> trying a Laplace transformation
* trying method "Fourier" for 2nd order PDEs
   -> trying a fourier transformation

<- fourier transformation successful
<- method "Fourier" for 2nd order PDEs successful

u(x, y) = invfourier(exp(s*(b+y))*fourier(h(x), x, s)/(exp(2*s*b)-1), s, x)-invfourier(exp(s*(b-y))*fourier(h(x), x, s)/(exp(2*s*b)-1), s, x)

(28)

>

u(x, y) = (1/2)*(Int((Int(h(x)*exp(-I*x*s), x = -infinity .. infinity))*exp(s*(b+y)+I*s*x)/(exp(2*s*b)-1), s = -infinity .. infinity))/Pi-(1/2)*(Int((Int(h(x)*exp(-I*x*s), x = -infinity .. infinity))*exp(s*(b-y)+I*s*x)/(exp(2*s*b)-1), s = -infinity .. infinity))/Pi

(29)

Reset the infolevel to avoid displaying the computational flow:

>

7. Improvements to solving heat and wave PDE, with or without a source:

Example 15: A heat PDE:

>

u(x, t) = 1/2+Sum(2*cos(n*Pi*x)*exp(-13*Pi^2*n^2*t)*(-1+(-1)^n)/(Pi^2*n^2), n = 1 .. infinity)+13*t+(1/2)*x^2

(30)

To verify an infinite series solution such as this one you can first use pdetest

>

[0, 0, 0, 1/2+Sum(2*cos(n*Pi*x)*(-1+(-1)^n)/(Pi^2*n^2), n = 1 .. infinity)-x]

(31)

To verify that the last condition, for is satisfied, we plot the first 1000 terms of the series solution with and make sure that it coincides with the plot of the right-hand side of the initial condition . Expected: the two plots superimpose each other

>

Example 16: A heat PDE in a semi-bounded domain:

>

u(x, t) = -5*exp(x^2/(-t+beta-1))*((erf(((t-beta-1)*alpha+x)/((t-beta+1)^(1/2)*(t-beta)^(1/2)))-1)*exp(4*alpha*(-x+alpha)/(-t+beta-1))+erf(((t-beta+1)*alpha-x)/((t-beta+1)^(1/2)*(t-beta)^(1/2)))-1)/(t-beta+1)^(1/2)

(32)

Example 17: A wave PDE in a semi-bounded domain:

>

u(x, t) = piecewise(3*t < x, 9*t^3*x+t*x^3, x < 3*t, (27/4)*t^4+(9/2)*t^2*x^2+(1/12)*x^4)

(33)

Example 18: A wave PDE with a source

>

u(x, t) = Sum(((-Pi^2*(-1)^n*n^2+Pi^2*n^2+2*(-1)^(n+1)+1)*cos(n*Pi*(t-x))-Pi*(-1)^n*n*sin(n*Pi*(t-x))+(Pi^2*(-1)^n*n^2-Pi^2*n^2+2*(-1)^n-1)*cos(n*Pi*(t+x))+Pi*n*(2*exp(-t)*(-1)^(n+1)*sin(n*Pi*x)+sin(n*Pi*(t+x))*(-1)^n))/(Pi^2*n^2*(Pi^2*n^2+1)), n = 1 .. infinity)

(34)

Example 19: Another wave PDE with a source

>

u(x, t) = ((Sum(-2*((1/2)*cos(n*x-t)*n^3-(1/2)*cos(n*x+t)*n^3+((-2*n^4-(1/2)*Pi*n^2+(1/8)*Pi)*sin(2*n*t)+(t-cos(2*n*t)+1)*n*(n-1/2)*Pi*(n+1/2))*sin(n*x))*(-1)^n/(Pi*n^4*(4*n^2-1)), n = 1 .. infinity))*Pi+x*sin(t))/Pi

(35)

8. Improvements in series methods for Laplace PDE problems

" Example 20:A Laplace PDE with BC representing the inside of a quarter circle of radius 1. The solution we seek is bounded as r approaches 0:"

>

pde__20 := diff(u(r, theta), r, r)+(diff(u(r, theta), r))/r+(diff(u(r, theta), theta, theta))/r^2 = 0

>

u(r, theta) = Sum(2*(Int(f(theta)*sin(2*n*theta), theta = 0 .. (1/2)*Pi))*r^(2*n)*sin(2*n*theta)/(Pi*n), n = 1 .. infinity)

(36)

Example 21: A Laplace PDE for which we seek a solution that remains bounded as y approaches :

>

u(x, y) = ((Sum(-2*A*sin(n*Pi*x/a)*exp(-n*Pi*y/a)/(n*Pi), n = 1 .. infinity))*a-A*(x-a))/a

(37)

9. Better simplification of answers:

Example 22: For this wave PDE with a source term, pdsolve used to return a solution with uncomputed integrals:

>

u(x, t) = Sum(2*(-1)^n*A*sin(n*Pi*x)*cos(n*Pi*t)/(n^3*Pi^3), n = 1 .. infinity)+(1/6)*(-x^3+x)*A

(38)

Example 23: A BC at is now handled by pdsolve:

>

u(x, y) = Sum(2*piecewise(a = Pi*n, (1/2)*Pi*n, -Pi*(-1)^n*sin(a)*n*a/(Pi^2*n^2-a^2))*exp(-n*Pi*x/a)*sin(n*Pi*y/a)/a, n = 1 .. infinity)

(39)

Example 24: A reduced Helmholtz PDE in a square of side Previously, pdsolve returned a series starting at , when the limit of the term is 0.

>

u(x, y) = Sum(-2*sin(n*y)*(-1+(-1)^n)*(exp(-(-2*Pi+x)*(n^2+k)^(1/2))-exp((n^2+k)^(1/2)*x))/((exp(2*(n^2+k)^(1/2)*Pi)-1)*Pi*n), n = 1 .. infinity)

(40)

10. Linear differential operator: more solutions are now successfully computed

Example 25:

>

(41)

Example 26:

>

pde__26 := diff(w(x1, x2, x3, t), t)-(D[1, 2](w))(x1, x2, x3, t)-(D[1, 3](w))(x1, x2, x3, t)-(D[3, 3](w))(x1, x2, x3, t)+(D[2, 3](w))(x1, x2, x3, t) = 0

>

(42)

Example 27:

>

pde__27 := diff(w(x1, x2, x3, t), t, t) = (D[1, 2](w))(x1, x2, x3, t)+(D[1, 3](w))(x1, x2, x3, t)+(D[3, 3](w))(x1, x2, x3, t)-(D[2, 3](w))(x1, x2, x3, t)

>

w(x1, x2, x3, t) = x1^3*x2^2+3*x2*(-t+a)^2*x1^2+(1/2)*(-t+a)*(a^3-3*a^2*t+3*a*t^2-t^3-2)*x1-(1/6)*a^3+(1/2)*a^2*t+(1/6)*(-3*t^2+6*x2*x3)*a+(1/6)*t^3-t*x2*x3+x3

(43)

11. More problems in 3 variables are now solved

Example 28: A Schrödinger type PDE in two space dimensions, where Z is Planck's constant.

>

pde__28 := I*`&hbar;`*(diff(f(x, y, t), t)) = -`&hbar;`^2*(diff(f(x, y, t), x, x)+diff(f(x, y, t), y, y))/(2*m)

>

iv__28 := f(x, y, 0) = sqrt(2)*(sin(2*Pi*x)*sin(Pi*y)+sin(Pi*x)*sin(3*Pi*y)), f(0, y, t) = 0, f(1, y, t) = 0, f(x, 1, t) = 0, f(x, 0, t) = 0

>

f(x, y, t) = 2^(1/2)*sin(Pi*x)*(2*exp(-((5/2)*I)*`&hbar;`*t*Pi^2/m)*cos(Pi*x)*sin(Pi*y)+exp(-(5*I)*`&hbar;`*t*Pi^2/m)*sin(3*Pi*y))

(44)

Example 29: This problem represents the temperature distribution in a thin rectangular plate whose lateral surfaces are insulated yet is losing heat by convection along the boundary , into a surrounding medium at temperature 0 (Articolo example 6.6.3):

>

iv__29 := (D[1](u))(0, y, t) = 0, (D[1](u))(1, y, t)+u(1, y, t) = 0, u(x, 0, t) = 0, u(x, 1, t) = 0, u(x, y, 0) = (1-(1/3)*x^2)*y*(1-y)

>

$u(x, y, t) = `casesplit/ans`(Sum(Sum((32/3)*exp(-(1/50)*t*(Pi^2*n^2+lambda[n1]^2))*(-1+(-1)^n)*cos(lambda[n1]*x)*sin(n*Pi*y)*(-lambda[n1]^2*sin(lambda[n1])+lambda[n1]*cos(lambda[n1])-sin(lambda[n1]))/(Pi^3*n^3*lambda[n1]^2*(sin(2*lambda[n1])+2*lambda[n1])), n1 = 0 .. infinity), n = 1 .. infinity), {And(tan(lambda[n1])*lambda[n1]-1 = 0, 0 < lambda[n1])})$

(45)

Articolo's Exercise 7.15, with 6 boundary/initial conditions, two for each variable

>

pde__30 := diff(u(x, y, t), t, t) = 1/4*(diff(u(x, y, t), x, x)+diff(u(x, y, t), y, y))-(1/10)*(diff(u(x, y, t), t))

>

iv__30 := (D[1](u))(0, y, t) = 0, (D[1](u))(1, y, t)+u(1, y, t) = 0, (D[2](u))(x, 0, t)-u(x, 0, t) = 0, (D[2](u))(x, 1, t) = 0, u(x, y, 0) = (1-(1/3)*x^2)*(1-(1/3)*(y-1)^2), (D[3](u))(x, y, 0) = 0

This problem is tricky ... There are three independent variables, therefore two eigenvalues (constants that appear separating variables by product) in the Sturm-Liouville problem. But after solving the separated system and also for the eigenvalues, the second eigenvalue is equal to the first one, and in addition cannot be expressed in terms of known functions, because the equation it solves cannot be inverted.

>

$u(x, y, t) = `casesplit/ans`(Sum((1/6)*(lambda[n]^2*sin(lambda[n])-lambda[n]*cos(lambda[n])+sin(lambda[n]))*cos(lambda[n]*x)*(exp((1/10)*t*(-200*lambda[n]^2+1)^(1/2))*(-200*lambda[n]^2+1)^(1/2)+exp((1/10)*t*(-200*lambda[n]^2+1)^(1/2))+(-200*lambda[n]^2+1)^(1/2)-1)*exp(-(1/20)*t*((-200*lambda[n]^2+1)^(1/2)+1))*(cos(lambda[n]*y)*lambda[n]+sin(lambda[n]*y))*(6*lambda[n]^2*cos(lambda[n])^2+cos(lambda[n])^2-5*lambda[n]^2-1)/((-200*lambda[n]^2+1)^(1/2)*(-cos(lambda[n])^4+(lambda[n]*sin(lambda[n])-1)*cos(lambda[n])^3+(lambda[n]^2+lambda[n]*sin(lambda[n])+1)*cos(lambda[n])^2+(lambda[n]^2+2*lambda[n]*sin(lambda[n])+1)*cos(lambda[n])+lambda[n]*(lambda[n]+sin(lambda[n])))*lambda[n]^4*(cos(lambda[n])-1)), n = 0 .. infinity), {And(tan(lambda[n])*lambda[n]-1 = 0, 0 < lambda[n])})$

(46)

>

Download PDE_and_BC_during_2018.mw

Edgardo S. Cheb-Terrab
Physics, Differential Equations and Mathematical Functions, Maplesoft

Bugs in maximize and minimize commands

by: Kitonum 21425 Product: Maple 2018

December 11 2018

2 1

Yesterday, I accidentally discovered a nasty bug in a fairly simple example:

restart;
Expr:=a*sin(x)+b*cos(x);
maximize(Expr, x=0..2*Pi);
minimize(Expr, x=0..2*Pi);

I am sure the correct answers are sqrt(a^2+b^2) and -sqrt(a^2+b^2) for any real values a and b . It is easy to prove in many ways. The simplest method does not require any calculations and can be done in the mind. We will consider Expr as the scalar product (or the dot product) of two vectors <a, b> and <sin(x), cos(x)>, one of which is a unit vector. Then it is obvious that the maximum of this scalar product is reached if the vectors are codirectional and equals to the length of the first vector, that is, sqrt(a^2+b^2).

Bugs in these commands were noted by users and earlier (see search by keywords bug, maximize, minimize) but unfortunately are still not fixed.

E-Mail Address:
Password:
Remember Me:	Automatically sign in on future visits

E-Mail Address:
Password:
Remember Me:	Automatically sign in on future visits

Ask a Question

Create a Post