On Fri, Oct 7, 2011 at 12:19 PM, Roy Stogner wrote:
>
>
> On Fri, 7 Oct 2011, Andrea Hawkins-Daarud wrote:
>
>> Aha! Right, I had used an old one of mine (libMesh-0.7.0+) as a basis,
>> but then got the error it didn't recognize the libmesh-0.7, so I
>> switched it to the Deal one.
>
> Could you s
On Fri, 7 Oct 2011, Andrea Hawkins-Daarud wrote:
> Aha! Right, I had used an old one of mine (libMesh-0.7.0+) as a basis,
> but then got the error it didn't recognize the libmesh-0.7, so I
> switched it to the Deal one.
Could you send me the 0.7.0+ file it didn't like? 0.7.1 isn't
compatible w
Aha! Right, I had used an old one of mine (libMesh-0.7.0+) as a basis,
but then got the error it didn't recognize the libmesh-0.7, so I
switched it to the Deal one. But libMesh-0.7.2 works! I get a
different error, but it at least seems to read it! =)
Is there a good recent write up of the differe
This looks kind of like a hybrid between the "DEAL 003:003" headered
file format used in our lshaped.xda example and the "libMesh-0.7.0+"
headered file format that we wrote (up until making a change to
"libMesh-0.7.2" recently to accomodate per-subdomain variable
metadata).
And while we can read
Hello-
I'm currently trying to write a xda file given a set of nodes and
element connectivities. I'm not positive I have the header right (it's
trying to mimic the l-shaped.xda in the examples), but given the
following input file
DEAL 003:003
1# number of elements
4# number of nod
>
> Try configuring the svn head with --disable-libHilbert and see if
> things read properly.
The old file does read properly when read with the svn head with
--disable-libHilbert.
Thank you!
Andrea
> ---
> Roy
--
En
On Wed, 23 Mar 2011, Andrea Hawkins-Daarud wrote:
Search through the svn logs for libHilbert, which we use to get
partitioning-independent node numbering in mesh files. There was a
bug in our earlier interface to libHilbert which was actually creating
corrupted outputs in some cases. IIRC we
>
> Search through the svn logs for libHilbert, which we use to get
> partitioning-independent node numbering in mesh files. There was a
> bug in our earlier interface to libHilbert which was actually creating
> corrupted outputs in some cases. IIRC we switched the renumbering off
> to avoid trig
On Wed, 23 Mar 2011, Andrea Hawkins-Daarud wrote:
> It appears that this topic came up before, but I did not see a
> resolution. Anyway, I have a few mesh and solution xda files that I
> created back in (about) August that do not seem to read in correctly.
> I don't know what version of libMesh I
Hello-
It appears that this topic came up before, but I did not see a
resolution. Anyway, I have a few mesh and solution xda files that I
created back in (about) August that do not seem to read in correctly.
I don't know what version of libMesh I was using then, but the headers
of these files say
On Wed, 23 Apr 2008, Paulo Correia wrote:
> I am using Triangle separately to build a specific mesh and I am
> writing a filter to convert it in xda format. However there is a
> variable "Sum of Element Weights" which I don't know how to
> calculate knowing the number of elements, its nodes and c
> I am using Triangle separately to build a specific mesh and I am writing a
> filter to convert it in xda format. However there is a variable "Sum of
> Element Weights" which I don't know how to calculate knowing the number of
> elements, its nodes and cooodinates.
> Can anyone give me an hint?
>
Hello,
I am using Triangle separately to build a specific mesh and I am writing a
filter to convert it in xda format. However there is a variable "Sum of Element
Weights" which I don't know how to calculate knowing the number of elements,
its nodes and cooodinates.
Can anyone give me an hint?
Th
13 matches
Mail list logo
