(最新整理)comsol錯(cuò)誤提示及解決方法

1、(完整)comsol錯(cuò)誤提示及解決方法(完整)comsol錯(cuò)誤提示及解決方法 編輯整理：尊敬的讀者朋友們：這里是精品文檔編輯中心，本文檔內(nèi)容是由我和我的同事精心編輯整理后發(fā)布的，發(fā)布之前我們對(duì)文中內(nèi)容進(jìn)行仔細(xì)校對(duì)，但是難免會(huì)有疏漏的地方，但是任然希望（(完整)comsol錯(cuò)誤提示及解決方法）的內(nèi)容能夠給您的工作和學(xué)習(xí)帶來(lái)便利。同時(shí)也真誠(chéng)的希望收到您的建議和反饋，這將是我們進(jìn)步的源泉，前進(jìn)的動(dòng)力。本文可編輯可修改，如果覺(jué)得對(duì)您有幫助請(qǐng)收藏以便隨時(shí)查閱，最后祝您生活愉快 業(yè)績(jī)進(jìn)步，以下為(完整)comsol錯(cuò)誤提示及解決方法的全部?jī)?nèi)容。diagnostics ： error messageserr

2、or messagesthis section summarizes the most common error messages and solver messages generated by comsol multiphysics. all error messages are numbered and sorted in different categories according to the following table.table 2-1: error message categoriesnumberscategory10001999importing models200029

3、99 geometry modeling30003999 cad import40004999 mesh generation50005999 point， edge, boundary， and subdomain specification60006999 assembly and extended mesh70007999 solvers80008999 postprocessing90009999 generalfor error messages that do not appear in the following lists, contact comsols support te

4、am for help.20002999 geometry modelingtable 2-2: geometry modeling error messageserror numbererror messageexplanation2118negative output from empty inputincorrect geometry mfile.2119non scalar output from empty inputincorrect geometry m-file。2120normal directions are inconsistentincorrect input data

5、 from stl/vrml import.2138self intersections not supportedcurves resulting in selfintersections are not supported。2140singular extrusions not supportederror in input parameters。2141singular revolutions not supportedthe revolved mesh has a singularity at the z axis. if possible, create the cylinder u

6、sing a 3d primitive or by revolving the geometry before meshing。2146subdomain must bounded at least four boundary segmentsincorrect geometry for mapped mesh。2147subdomain must bound one connected edge component onlyincorrect geometry for mapped mesh。2190invalid radius or distanceincorrect input para

7、meters to fillet/chamfer.2197operation resulted in empty geometry objectgeometry operation resulted in an empty geometry object which is not allowed. make sure an empty geometry object is not created。2209geometry to revolve may not cross axis of revolutionthe axis of revolution and the geometry inte

8、rsect. check the dimension of the geometry and the definition of the axis for the revolution。40004999 mesh generationtable 23: mesh generation error messageserror numbererror messageexplanation4002a degenerated tetrahedron was createdthe mesh generator ran into numerical difficulties while creating

9、tetrahedrons with a size based on user-controlled parameters. causes could be too small and narrow subdomains relative to the rest of the geometry or exceedingly short boundary segments. try to avoid creating small and narrow subdomains and very short boundary segments that are adjacent to longer bo

10、undary segments.4003a degenerated triangle was created the mesh generator ran into numerical difficulties while creating triangles with a size based on usercontrolled parameters. causes could be too small and narrow subdomains relative to the rest of the geometry or exceedingly short boundary segmen

11、ts. try to avoid creating small and narrow subdomains and very short boundary segments that are adjacent to longer boundary segments.4012cannot create mapped mesh for this geometrythe geometry does not fulfill the topological requirements for a mapped mesh。 changes in input parameters or further sub

12、domain division can possibly help this。4026failed create matching edge discretizationscannot make mapped mesh with the given input parameters。4029failed to insert pointproblems inserting point at given coordinate. manually inserting a point there may help。4031failed to respect boundary element on ge

13、ometry edgethe mesh generator failed in making the elements compatible with the geometry objects edges。 the reason for this could be that the face mesh is too coarse or contains adjacent elements with large differences in scale。 another reason can be that some subdomains in the geometry are too narr

14、ow with respect to the rest of the geometry.4032failed to respect boundary element on geometry facesee error message 4031.4044internal error boundary respecting see error message 4031。4054invalid topology of geometrythe geometry object cannot be used for creating a mapped mesh。 it must be subdivided

15、。4055isolated entities foundentities that are not connected to the boundaries of a geometry objects is found。 the mapped mesh generator does not support such isolated entities。4119singular edge detectedthe geometry object contains an edge of zero length。60006999 assembly and extended meshtable 2-4:

16、assembly and extended mesh error messageserror numbererror messageexplanation6008circular variable dependency detecteda variable has been defined in terms of itself, possibly in a circular chain of expression variables. make sure that variable definitions are sound。 be cautious with equation variabl

17、es in equations。6063invalid degree of freedom namethe software does not recognize the name of a degree of freedom. check the names of dependent variables that you have entered for the model. see also error 7192。6139wrong number of dofs in initial valuethe current solution or the stored solution has

18、for some reason the wrong number of degrees of freedom, sometimes due to a change of the implementation of elements between two versions of the software。 to overcome the problem， go to the initial value area in the solver manager, and select initial value expression. then the initial value expressio

19、ns is evaluated without using the current or stored solution。6140wrong number of dofs in linearization pointthe current solution or the stored solution has for some reason the wrong number of degrees of freedom, sometimes due to a change of the implementation of elements between two versions of the

20、software。 to overcome the problem, go to the value of variables not solved for and linearization point area in the solver manager, and click the use setting from initial value frame button or the zero button.6163divide by zeroa property in the model contains a divisor that becomes zero. check to mak

21、e sure that division by zero does not occur in any expression or coefficient. 6164duplicate variable namea variable name has two different definitions。 for instance， the same variable name appears two or more times for a dependent variable, a constant， an expression variable, or a coupling variable.

22、 remove or rename one of the variables.6170failed to evaluate variablean error occurred when evaluating the variable. the domains in which comsol multiphysics tried to evaluate the variable are indicated. also， the error message shows the expression that comsol multiphysics was unable to evaluate。 m

23、ake sure that you have defined the variables correctly in the indicated domains.6176attempt to evaluate real logarithm of negative numberan expression contains log(a), where a becomes negative or zero. to make the logarithm welldefined， make sure that a0. often， a becomes only slightly negative （due

24、 to approximations in the solution process)。 then, a possible solution is to use log(a+e)， where e is a small constant. another remedy is to use log（abs（a)。 if you do want to have a complex logarithm, go to the advanced tab of solver parameters and select the use complex functions with real input ch

25、eck box。6177matrix has zero on diagonalwhen the equations have a structure such that the stiffness matrix (jacobian matrix) has zeros on the diagonal， it is not possible to use the following linear system solvers/preconditioners/smoothers: all versions of sor and diagonal scaling (jacobi)。 try the v

26、anka preconditioner/smoother instead。6188out of memory during assemblythe software ran out of memory during assembly of the finite element model。 see error 7144 regarding general memorysaving tips。6194attempt to evaluate nonintegral power of negative numberan expression contains ab， where a becomes

27、negative and b is not an integer. to make the power well-defined， make sure that a0。 often, a becomes only slightly negative (due to approximations in the solution process）。 then, a possible solution is to use （a+e)b， where e is a small constant。 another remedy is to use abs（a)b. if you do want to h

28、ave a complex number ab, go to the advanced tab of solver parameters and select use complex functions with real input.6199attempt to evaluate real square root of negative numberthe model contains a sqrt (square root) function that takes the square root of a negative number。 either make sure that the

29、 square-root argument is nonnegative or select the use complex functions with real input check box on the advanced tab in the solver parameters dialog box。6204undefined function callan expression contains an undefined function name。 check that the function name is correct and that the function is in

30、 comsol multiphysics or matlabs path.6206internal evaluation error: unexpected nan encounterednot-a-number （nan) appears unexpectedly。 a possible cause is improperly defined coupling variables。 as a first step, check that the definitions of the source and destination domains of any coupling variable

31、s or periodic boundary conditions are correct.6245unsupported integration orderintegration order is too high. for triangular elements the order can be up to 10， and for tetrahedral elements the order can be up to 8。 find more information in the section “numerical quadrature” on page 505.6259failed t

32、o evaluate variable jacobianan error occurred when evaluating the jacobian of the indicated variable。 the domains in which comsol multiphysics tried to evaluate the variable are indicated。 make sure that you have defined the variable correctly in the indicated domains。70007999 solvers and preconditi

33、onerstable 2-5： solver error messageserror numbererror messageexplanation7001adaption only implemented for tetrahedral meshesit is only possible to use adaptive mesh refinement in 3d for models using tetrahedral mesh elements. either turn off adaptive mesh refinement or switch from brick or prism el

34、ements to tetrahedral elements。7002adaption only implemented for triangular meshesit is only possible to use adaptive mesh refinement in 2d for models using triangular mesh elements。 either turn off adaptive mesh refinement or switch from quadrilateral elements to triangular elements。7022segregated

35、solver steps do not involve all of solcompthe groups for the segregated solver do not include all dependent variables. one reason for this error could be that some boundary conditions （for example， for laminar inflow in fluid-flow models) add dependent variables that are not initially in the model.7

36、043initial guess leads to undefined function valuethis error message usually appears when you have set up an expression that returns “not a value，” that is， it is undefined， for the initial condition you have set。 for instance， this happens if an expression contains a divisor that becomes zero or a

37、logarithm of a negative value。 to solve the problem， change the expression or the initial value so that the expression is welldefined when substituting the initial value of the variables。 also, watch out for warnings in the log window.7067system matrix is zerothis error message appears if there are

38、no volume elements in the mesh. in the case that you have a mapped surface mesh， try sweeping or extruding the surface mesh to get a volume mesh.7069maximum number of linear iterations reached the iterative linear system solver did not converge due to a bad initial guess or a bad preconditioner. inc

39、rease the limit on the number of linear iterations or use a better preconditioner. if possible, use a direct linear system solver。7081no parameter name giventhe parametric solver does not find a name for the parameter。 check the name of parameter edit field on the general page of the solver manager.

40、7092out of memory in algebraic multigridthe algebraic multigrid solver/preconditioner ran out of memory。 see error 7144 regarding general memory-saving tips。7093out of memory during back substitutionthe solver ran out of memory during back substitution。 see error 7144 regarding general memory-saving

41、 tips.7094out of memory during lu factorizationthe solver ran out of memory during lu factorization。 see error 7144 regarding general memory-saving tips。7111singular matrixthe system matrix （jacobian matrix or stiffness matrix） is singular, so the solver cannot invert it. usually this means that the

42、 system is underdetermined。 check that all equations are fully specified and that the boundary conditions are appropriate。 for instance， in a stationary model you usually need to have a dirichlet condition on some boundary。 a singular matrix could also occur if mesh elements are of too low quality。

43、if the minimum element quality is less than 0.005 you might be in trouble。 another reason for this error message is that you have different element orders for two variables that are coupled by， for example， a weak constraint. use the same element order for all variables that are coupled.7136very ill

44、conditioned preconditioner. the relative residual is more than 1000 times larger than the relative toleranceyou need to improve the quality of the preconditioner to get an accurate solution. for the incomplete lu preconditioner, lower the drop tolerance。 7144out of memory in adaptive solverthe adapt

45、ive solver ran out of memory。 the adaptive mesh refinement has generated a too fine mesh. in general， when you run out of memory, try to use memoryefficient modeling techniques such as utilizing symmetries, solving models sequentially， and selecting memory-efficient solvers. see the chapter “solving

46、 the model” on page 377 in the comsol multiphysics users guide for more information。 see also the comsol installation and operations guide for information about system memory management.7145out of memory in eigenvalue solverthe eigenvalue solver ran out of memory. see error 7144 regarding general me

47、morysaving tips。7146out of memory in stationary solverthe stationary solver ran out of memory。 see error 7144 regarding general memorysaving tips.7147out of memory in time-dependent solverthe timedependent solver ran out of memory. see error 7144 regarding general memorysaving tips。7192invalid degre

48、e of freedom name in manual scalingthe name of a dependent variable in the manual scaling edit field on the advanced page in the solver parameters dialog box does not match any of the dependent variables in the model.7199reordering failedone of the pardiso reordering algorithms failed. try a differe

49、nt reordering algorithm or try turning off row preordering.7248undefined value foundsee the explanation of error 7043 for some possible reasons as to why this error number appears. in most situations you get a more detailed description of the error by pressing the details button.7297undefined value

50、foundthis error number appears if one of the linear system solvers encounters an undefined value （such values appear， for instance， if a division by zero has been performed or if some arithmetic operation results in a larger number than can be represented by the computer）. for direct solvers this er

51、ror might appear if the stiffness matrix （jacobian matrix） is singular or almost singular。 for iterative solvers this error might appear, for instance， if the iterative process diverges。 press the details button to see which linear solver caused the error。90009999 general errorstable 2-6: general er

52、ror messageserror numbererror messageexplanation9037failed to initialize 3d graphics. opengl not fully supportedopengl is not available on the computer。 this can happen if your graphics card does not support opengl or if you have a unix/linux computer where opengl has not been configured。9040fatal e

53、rrorif you receive this error, click the detail button. copy and paste the entire error message and send it to support along with your license file and details of how to reproduce the error。9052invalid address/portyou did not enter the correct server name or server port when trying to connect a clie

54、nt to a server。9084server connection errorthe client somehow lost the connection to the server. for example, the server crashed unexpectedly， or the power saving mechanism on a laptop shut down the tcp/ip connection。9143license errorthe most common reasons for this message: the license file license.

55、dat has been removed from the right directory in the comsol software installation。 the license.dat file must be located in the comsol35a/license directory, where $comsol35a is the comsol3。5a installation directory. the license manager has not started properly。 please find the flexlm log file (named

56、by the person who started the license manager）。 inspect this file to see the server status. send it to supportcomsol。com if you are in doubt about how to interpret this file.it is crucial that you use the correct license。dat file on both the server and the clients9178error in callbackan error occurr

57、ed when calling a matlab function from comsol multiphysics. make sure that the mfile that defines the function is correct and exists in the current path。 check that the function is written so that all inputs are vectors of the same size and the output is a vector of the same size.solver error messagesthese error messages can appear during solution and appear on the log tab in the progress window。table 27： solver error messages in log windowsolver error messageexplanationcannot meet error tolerances。 increase absolute or relative tolerance.the timedependent solver cannot solve the model to th