From: li p. <li...@ya...> - 2006-04-02 15:31:59
|
Dear all, I had a strange experience with system.matrix-add. I read the mesh data first, which was made up of 6 TETs. And add a value (1.0) to matrix(0,18). The system matrix has dimension of 24*24. Then, I print it out. The value of matrix(0,18) is not there. Could anybody tell why. I send you the files. You can run the simple code with ./readmesh cube.1.node pan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Roy S. <roy...@ic...> - 2006-04-02 16:02:40
|
On Sun, 2 Apr 2006, li pan wrote: > I had a strange experience with system.matrix-add. I > read the mesh data first, which was made up of 6 TETs. > And add a value (1.0) to matrix(0,18). The system > matrix has dimension of 24*24. Then, I print it out. > The value of matrix(0,18) is not there. Could anybody > tell why. I send you the files. You can run the simple > code with > ./readmesh cube.1.node I've just run it (well, after adding an empty assemble function so it would link) with CVS libMesh + LASPACK and with CVS libMesh + PETSc 2.3.0, and in both cases entry 0,18 gets printed out as 1. Are you running libMesh 0.5.0? I'm compiling that to test with now... if this is a bug we've already fixed, it may be time to get 0.6.0 out soon. Actually, now that I'm starting to get code working on hp grids, it may be time to get 0.6.0 out soon regardless. ;-) In fact, it looks like newer gcc versions still won't compile 0.5.0 unless the << operator in parameters.h is moved to be defined before it's used... perhaps it's at least time to get 0.5.1 out. We may also want to get into the habit of forking off a "stable" branch after each new release, so that while crazy new DofMap code is limited to the CVS head for testing, small bugfixes can go into point releases too. --- Roy |