@acer 

Is it not the case that selecting Atomic Variables in the View menu changes the color of all such variables in the document? The magenta color assumed by these atomics stands out pretty clearly. So, I wonder why you pointed to such an odd visual clue in your comment. Am I missing something?

When the Enter key is pressed, Maple searches for a solution, but fails to find one, so returns NULL.

If you eliminate w and the derivative with respect to w, Maple returns a solution. So, it would appear that as the equation becomes more complex, Maple cannot find a solution, or perhaps it means no solution exists.

@tsunamiBTP 

The Gibbs phenomenon refers to the fact that near a jump discontinuity, the partial sums of a Fourier series "overshoot" the one-sided limit of the function by an amount equal to approximately 9% of the jump at the discontinuity. The attached worksheet examines what happens to a function that has a jump of three units at a discontinuity at x=0. The Gibbs spike in several partial sums are found to have heights slightly larger than the one-sided limit from the right. The amount by which this max exceeds the limit from the right is shown to be approximately 9% of the jump of 3.Gibbs.mw

The relevant command in the LinearAlgebra package is Eigenvectors, not eigenvects or eigenvectors. This command returns a sequence of two objects, a vector containing the eigenvalues, and a matrix whose columns are the eigenvectors. There are options available in this command that will alter the form in which this information is displayed. One can obtain the algebraic and geometric multiplicities of the eigenvalues, etc. Look at the help page for details.

It is a rare 8x8 matrix whose eigenpairs can be found in closed form. Think about it. You essentially have to solve an 8th-degree polynomial equation. Of course, you remember that there is no formula for solving such polynomial equations once the degree exceeds 4. But for the matrix in your worksheet, the characteristic polynomial factors, and the eigenvalues can be found exactly. In general, if the matrix contains a single floag (a number with a decimal point), the calculation of eigenpairs will be done with numeric tools and the return of the Eigenvectors command will contain just floating-point numbers.

One of the exact eigenvalues for your 8x8 matrix is exactly zero. If the matrix T contains a single float, then the eigenvalues are computed and returned as floats, and the zero eigenvalue is no longer zero, but a small real number. That is what you have to contend with as you grapple with the matrix you are importing into Maple.

The ordinary technique of separating variables will not work on this BVP because the Neumann BCs are not homogeneous. You will not get a solution via the technique you are using. The ordinary method for solving this problem requires introducing a perturbation that replaces the nonhomogeneity in the BCs with an inhomogeneity in the PDE. There's an example in my AEM ebook, and I'm sure you can find similar examples in the internet. But be prepared to do a lot of work if you want an explicit (analytic) solution.

@Christopher2222 

Given that Maple can use I in its represention of the real solutions of a cubic equation, simply removing anything with I might not be optimal. Floating the solutions can result in small imaginary parts, again causing a failure of the "remove I" approach. For example, the cubic x^3+7*x^2-5*x-12 has three real solutions but Maple represents them with I. Applying evalf results in numbers with a small imaginary part. For this particular cubic, using the solve command in the RealDomain package gives the three solutions as real numbers and without I. Without access to the OP's seq of equations, it's hard to say more.

@mathiaszip Round brackets (parentheses) are used for all mathematical operations. Square brackets denote a list. Curley braces (i.e., {...}) denote a set. A list can contain multiple copies of an object, and preserves the order of its objects. A set will not contain multiple copies of an object, and will not preserve the order of the objects. Is this enough of a hint?

@tsunamiBTP Type "Fourier series" in the search box in the upper-right portion of the MaplePrimes window. A list of relevant links will be generated. Follow the appropriate links to learn about the various packages that users have created for Fourier series.

@Zeineb 

It seems that the second derivatives are approximated with central differences, but the first derivative is approximated with a forward difference. I changed that to a central difference, and the case where I couldn't get a solution (nX=nY=8) now solves.

When I examined that case for nX=Ny=3, where I could reduce the equations to two in two unknowns, and obtain an implicitplot, now the curves intersect. However, there are multiple intersections, so determining programmatically which of the many possible solutions are the right ones will be difficult.

But it would appear that using two different types of differences for the derivatives was not appropriate.

@Zeineb 

Tried nX=nY=4..7 and got solutions in each case. At 8, fsolve returns unevaluated. But at 7, the solution takes a bit of time. So, the issue seems to be in Maple's ability to solve the set of equations generated in the worksheet. The equations are nonlinear, so at some point fsolve probably needs some help determining where to look for solutions.

@tomleslie 

eliminate(newEqs,[U[1,1],U[2,1]]); reduces the system to two equations in two unknowns. Then, an implicitplot shows the curves defined by these two equations do not intersect. So you are probably right about there being something wrong with the original equations.

@MapleMathMatt 

I think your use of % gives the desired result, but that's not the & mentioned in your text. But your code seems to be the simplest way to obtain the desired result.

@mortezaghafoori 

As far as I can tell, you have a first order ODE but you are applying two boundary conditions.

Maple can provide a general solution to the ODE itself. It contains only one constant, so you can't apply both boundary conditions, unless what appears to be "A" on the right-hand side is a second parameter that can be adjusted. Unfortunately, my experiments with this approach seem to indicate that the problem (as I've interpreted it) has no solution.

By the way, it is not true that dsolve only handles initial-value problems. It will also solve boundary-value problems as well.

Finally, rather than post an image of your work, post a worksheet containing this work by using the green "up-arrow" in the MaplelPrimes toolbar.

I just installed the .3 update to Maple 2017 and noted that the glitch exhibited by vv persists in the updated version.

@NorwegianStudent 

I don't know if both packages can exist simultaneously in Maple. There may be clashes that lurk beneath the surface. These packages are not maintained by Maplesoft, so there's no guarantee that they are compatible. Perhaps someone with greater coding skills might be able to give a more definitive answer.