Hi
The subject says it all. The side node numbering in exodus_IO.C
const int ExodusII::ElementMaps::hex27_node_map[27] = { 1, 5, 6, 2, 0,
4, 7, 3, 13, 17, 14, 9, 8, 16,
18, 10, 12, 19, 15,
11, 24, 25, 22, 26, 21, 23, 20};
On Fri, Aug 8, 2008 at 8:26 AM, Martin Luethi <[EMAIL PROTECTED]> wrote:
> Hi
>
> The subject says it all. The side node numbering in exodus_IO.C
>
> const int ExodusII::ElementMaps::hex27_node_map[27] = { 1, 5, 6, 2, 0,
> 4, 7, 3, 13, 17, 14, 9, 8, 16,
>
On Fri, 8 Aug 2008, Martin Luethi wrote:
> The subject says it all. The side node numbering in exodus_IO.C
> is wrong. Without proper documentation this is pretty hard to fix. Does
> anybody have an idea what their node ordering on the sides is?
Hmm... I'd say this was Derek's bailiwick, but he
On Fri, Aug 8, 2008 at 8:54 AM, Roy Stogner <[EMAIL PROTECTED]> wrote:
>
> On Fri, 8 Aug 2008, Martin Luethi wrote:
>
> > The subject says it all. The side node numbering in exodus_IO.C
> > is wrong. Without proper documentation this is pretty hard to fix. Does
> > anybody have an idea what their n
I would own up to it if it were me! I actually didn't implement the
Exodus writer in libMesh (although I have contributed a lot of changes
to it). It appears that Ben put this stuff in way back in 2004. I
don't know what documentation he was working from... but I can't find
HEX27's in an
On Fri, 8 Aug 2008, Derek Gaston wrote:
> I would own up to it if it were me!
Oh, yeah - by bailiwick I didn't mean "who's at fault", just "who's
been working with the code most recently and most familiar with it".
> I'll email Greg Sjaardema at Sandia and see if he can dig up the side node
>
The exodusII-4.pdf file available here
http://sourceforge.net/project/showfiles.php?group_id=146943
has the specification in Table 2 on page 24.
Who's familiar enough with libMesh's Hex27 node ordering to decipher
what's in the code and compare it to this document?
Derek
On Aug 8, 2008, at
John and I can probably do that. John wrote the original implementation,
and I am pretty sure the node ordering is solid as we have used it before.
Am I correct that the issue here is the face node ordering?
-Ben
On 8/8/08 10:46 AM, "Derek Gaston" <[EMAIL PROTECTED]> wrote:
> The exodusII-4.p
On Fri, Aug 8, 2008 at 10:46 AM, Derek Gaston <[EMAIL PROTECTED]> wrote:
> The exodusII-4.pdf file available here
> http://sourceforge.net/project/showfiles.php?group_id=146943
> has the specification in Table 2 on page 24.
Cool, that table implies the positions of the mid-face nodes on the
prec
Ben... where are we at on the Trilinos integration with libMesh? I
know that you did some work a little while ago to put an eptra_matrix
object in there. How much of that is working?? How long do you think
it would take someone to finish off epetra_matrix and epetra_vector?
The Trilinos q
> Ben... where are we at on the Trilinos integration with libMesh? I
> know that you did some work a little while ago to put an eptra_matrix
> object in there. How much of that is working?? How long do you think
> it would take someone to finish off epetra_matrix and epetra_vector?
Actually wou
> If they have the time to pour through the Trilinos documentation
> then great,
> if they know Trilinos even better... The major libMesh stuff is done.
The biggest libMesh thing to me is the sparsity graph. Do you have
epetra_matrix and epetra_vector building the correct parallel sparsity
> The biggest libMesh thing to me is the sparsity graph. Do you have
> epetra_matrix and epetra_vector building the correct parallel sparsity
> Map based on our sparsity graph yet? If so, then truly there isn't
> much work to do.
The DofMap builds the proper sparsity pattern, but the Epetra side
On Fri, Aug 8, 2008 at 11:28 AM, John Peterson <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 8, 2008 at 10:46 AM, Derek Gaston <[EMAIL PROTECTED]> wrote:
>> The exodusII-4.pdf file available here
>> http://sourceforge.net/project/showfiles.php?group_id=146943
>> has the specification in Table 2 on pag
Hi John
John Peterson writes:
> On Fri, Aug 8, 2008 at 11:28 AM, John Peterson <[EMAIL PROTECTED]> wrote:
> > On Fri, Aug 8, 2008 at 10:46 AM, Derek Gaston <[EMAIL PROTECTED]> wrote:
> >> The exodusII-4.pdf file available here
> >> http://sourceforge.net/project/showfiles.php?group_id=146943
Forgot to copy to the list.
-- Forwarded message --
From: John Peterson <[EMAIL PROTECTED]>
Date: Fri, Aug 8, 2008 at 5:46 PM
Subject: Re: [Libmesh-devel] Exodus export for HEX27 broken
To: Martin Luethi <[EMAIL PROTECTED]>
On Fri, Aug 8, 2008 at 5:40 PM, Martin Luethi <[EMAIL P
> I'd like to refactor this code a bit while I'm at it ... parts of it I
> wrote in 2002 and it shows :-P For example, dynamic memory allocation
> is used in several places where, as far as I can tell, it's not
> necessary.
Can you grab a hex27 mesh from Bill made by Cubit? I know we have import
On Fri, Aug 8, 2008 at 5:40 PM, Martin Luethi <[EMAIL PROTECTED]> wrote:
>
> Maybe trial and error is the way to go...
>
I think I've fixed the Hex27 numbering issue. Martin, could you take
a look and see if it works for you now?
--
John
---
18 matches
Mail list logo
