Error Diagnostics

Some common error messages, usual problems and possible solutions are described in this chapter. A link to the mumps users guide is provided as follows. http://mumps.enseeiht.fr/doc/userguide_5.2.1.pdf

MUMPS Equation Solver Messages

In many cases problems result from the equation solver. So, if the solution does not give any results, or all results are zero or infinity, then the feature ’Additional Logfile Output’ should be activated. This is done in the ’Solver Parameters’ (RMB on the solution) in register ’Numerical’. To make the button visible, first the ’Equation Solver’ must be set to ’MUMPS, direct (Default)’. With this feature activated the solver should be started again and there will be a large section of additional messages in the solver logfile. At the end of these messages check for INFOG(1) and INFOG(2). If these show negative values, this means an error occurred. Following is a list of usual messages, explanations and some workarounds:

• INFOG(1) = –1
  An error occurred on processor INFO(2).

• INFOG(1) = –2
  NZ is out of range. INFO(2)=NZ.

• INFOG(1) = –3
  MUMPS was called with an invalid value for JOB. This may happen for example if the analysis (JOB=1) was not performed before the factorization (JOB=2), or the factorization was not performed before the solve (JOB=3). This error also occurs if JOB does not contain the same value on all processes on entry to MUMPS.

• INFOG(1) = –4
  Error in user-provided permutation array PERM_IN in position INFO(2). This error occurs on the host only.

• INFOG(1) = –5
  Problem of REAL workspace allocation of size INFO(2) during analysis.

• INFOG(1) = –6
  Matrix is singular in structure.

• INFOG(1) = –7
  Problem of INTEGER workspace allocation of size INFO(2) during analysis.

• INFOG(1) = –8
  MAXIS too small for factorization. This may happen, for example, if numerical pivoting leads to significantly more fill-in than was predicted by the analysis. The user should increase the value of ICNTL(14) or the value of MAXIS before entering the factorization (JOB=2).

• INFOG(1) = -9
  The main internal work array S is too small. Increasing parameter ICNTL(14) may help. Try values between 20 and 100. Also, in many cases this results from missing material properties. Especially this happens if there is zero electric conductivity applied to an electric body.

• INFOG(1) = -10
  Numerically singular matrix. The system is somehow under determined and cannot be solved. In many cases this results from missing material properties. Especially this happens if there is zero electric conductivity applied to an electric body. But also stranded coils with missing loads will lead to this problem.

• INFOG(1) = –11
  MAXS too small for solution. See error INFO(1)=–9.

• INFOG(1) = –12
  MAXS too small for iterative refinement. See error INFO(1)=–9.

• INFOG(1) = -13
  The computer didn’t have enough memory available. Activating the Out-Of-Core feature (if not already done) can maybe overcome this. Reducing the number of elements or using more memory are other approaches. [6pt]If -13 appears, the requested working memory is larger than the available memory. Working memory is either estimated by the system or can be defined by parameter ICNTL(23).

• INFOG(1) –14
  MAXIS too small for solution. See error INFO(1)=–8.

• INFOG(1) –15
  MAXIS too small for iterative refinement and/or error analysis. See error INFO(1)=–8.

• INFOG(1) –16
  N is out of range. INFO(2)=N.

• INFOG(1) –17
  The internal send buffer that was allocated dynamically by MUMPS on the processor is too small. The user should increase the value of ICNTL(14) before entering the analysis (JOB=1).

• INFOG(1) –18
  MAXIS too small to process root node. See error INFO(1)=–8.

• INFOG(1) = -19
  The maximum allowed size of working memory is too small to solve this model (in the factorization phase). Working memory is either estimated by the system or can be defined by parameter ICNTL(23).

• INFOG(1) = –21
  Incompatible values of PAR=0 and NPROCS=1. INFO(2)=NPROCS. Running MUMPS in host-node mode (the host is not a slave processor itself) requires at least two processors. The user should either set PAR to 1 or increase the number of processors.

• INFOG(1) = –22
  A pointer array is provided by the user that is not associated or that has insufficient size. INFO(2) points to the pointer array having the wrong format.

• INFOG(1) = –23
  MPI was not initialized by the user prior to a call to MUMPS with JOB=–1.

• INFOG(1) = -90
  Error in out-of-core management. Check the following: Does the directory for out of core files exist? Is there enough disk space?

• INFOG(2) = -2697 (or any other negative value). [6pt]The system was trying to allocate an extra 2697*1E6 = 2.697E9 units of memory. If you are using 64 reals this would be 2.697E9*8 bytes, or 21.6 GB. If you are using 64 complex numbers it would be twice this. This will be the size of an allocate in a single MPI instance. It will also be in addition to any memory already in use.