Note: This discussion is about an older version of the COMSOL Multiphysics® software. The information provided may be out of date.
Discussion Closed This discussion was created more than 6 months ago and has been closed. To start a new discussion with a link back to this one, click here.
wrong number of dof in linearization point
Posted 15.03.2011, 08:42 GMT-4 Version 3.5a 2 Replies
Please login with a confirmed email address before reporting spam
Hi,
what is the meaning of this error message when using the adaptive mesh refinement feature?
The calculation on the source mesh was succesful. Just before starting the calculation on the refined mesh, the error appears.
Best regards,
mb
what is the meaning of this error message when using the adaptive mesh refinement feature?
The calculation on the source mesh was succesful. Just before starting the calculation on the refined mesh, the error appears.
Best regards,
mb
2 Replies Last Post 09.11.2011, 20:20 GMT-5
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
Hi
my feeling is that only COMSOL developers really know what these mostly cryptic error messages means, at least I have not noticed that one before.
It is true that some chain info where the messages originates to in the solving process etc, but in user compatible words, could be useful, some more info along these lines is to be found in the error log, and you can turn (far down in the solver nodes) the error log onto "detailed", which mostly only means a few more info, often of interest, especially when fighting with convergence issues.
--
Good luck
Ivar
my feeling is that only COMSOL developers really know what these mostly cryptic error messages means, at least I have not noticed that one before.
It is true that some chain info where the messages originates to in the solving process etc, but in user compatible words, could be useful, some more info along these lines is to be found in the error log, and you can turn (far down in the solver nodes) the error log onto "detailed", which mostly only means a few more info, often of interest, especially when fighting with convergence issues.
--
Good luck
Ivar
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
I ran into this problem before, even with everything seem to set up correctly. I found two ways to solve this problem, one is to "get the initial values" within the solver, then restart the model instead of using the solver button directly, this worked for me. Another way is to restart the model all over again from the very beginning and make sure you enter your subdomain, boundary conditions, constants, and variable definition correctly (I know this seem ridiculous) but sometimes there are accumulating errors that just preventing it from working, i still don't know what the error means or how to properly resolve it, but the above seem to work for now.