Sweet - that is great news! Thanks for working this out Ben!
Derek
On Mon, Mar 3, 2014 at 9:13 AM, John Peterson wrote:
>
>
>
> On Mon, Mar 3, 2014 at 8:33 AM, Kirk, Benjamin (JSC-EG311) <
> benjamin.k...@nasa.gov> wrote:
>
>> Looks like we're in the clear:
>>
>> > Glad to hear that libHilber
On Mon, Mar 3, 2014 at 8:33 AM, Kirk, Benjamin (JSC-EG311) <
benjamin.k...@nasa.gov> wrote:
> Looks like we're in the clear:
>
> > Glad to hear that libHilbert found a home somewhere. Shouldn't be a
> problem to re-release that under the LGPL.
> >
> > It took me a few days to get access to my old
Looks like we're in the clear:
> Glad to hear that libHilbert found a home somewhere. Shouldn't be a problem
> to re-release that under the LGPL.
>
> It took me a few days to get access to my old university account, but you can
> find the new source here:
>
> https://web.cs.dal.ca/~chamilto/hi
Right - we don't do m->n restart so that works for us.
Also - recall that I don't like this reordering business because the
un-reordering destroys the original ordering... so that's another reason
not to reorder...
Unfortunately though it turns out that something about the reordering
might be
Short term yes, but this will break m->n restart I think.
I recall something similar in the mesh a few yearns back when two disjoint
nodes created an identical index. The fix there was to handle identical keys
for separate nodes. If I can extend that to this case all will be good.
On Jan 3, 2
If I just comment out the renumbering in EquationSystems::write() then
everything looks fine. Would anyone object to me adding a flag
to EquationSystems::write() allowing you to turn off the renumbering?
Derek
On Fri, Jan 3, 2014 at 10:39 AM, Derek Gaston wrote:
> Ok - MeshCommunication::assi
Ok - MeshCommunication::assign_global_indices() is beyond my
comprehension... BUT there are a couple of "#if 0" error checks in there
that if un-#if'd they do trigger these things with my test case:
Error: nodes with duplicate Hilbert keys!
node 7, (x,y,z)=( 0.5, 0.5,0) has Hilber
On Thu, 2 Jan 2014, Derek Gaston wrote:
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 th
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
