One of my users brought an issue to my attention: libMesh is not properly
handling multiple nodes occupying the same position when writing out
xda/xdr files for the solution vector.
I am attaching a mesh and main.C that show the issue. If you look at the
resulting eq_sys.xda file you will see tha
On Thu, Jan 2, 2014 at 12:45 PM, Roy Stogner wrote:
>
> Some static analysis tools pointed me to a few problems with the
> Elem::SideIter class - basically there's a correctness mistake that's
> masked by a performance mistake.
>
> This is fixable, but this is also code that I find literally no us
On Thu, 2 Jan 2014, Kirk, Benjamin (JSC-EG311) wrote:
> I am planning to polish up a release in two weeks while at AIAA, so
> if you want to deprecate it now I'd think that would be a good
> approach.
Will do.
> Which code was actually using this?
No code using this; I'm running our stuff thro
I am planning to polish up a release in two weeks while at AIAA, so if you want
to deprecate it now I'd think that would be a good approach.
Which code was actually using this?
On Jan 2, 2014, at 1:45 PM, Roy Stogner
wrote:
>
> Some static analysis tools pointed me to a few problems with t
Some static analysis tools pointed me to a few problems with the
Elem::SideIter class - basically there's a correctness mistake that's
masked by a performance mistake.
This is fixable, but this is also code that I find literally no usage
of in the rest of the library or our example apps. I'm not
