> them.
>
> And do test the code with a ".msh" file using example 1. Let me know
> if you have any questions.
>
> Vijay
>
> On Tue, Oct 27, 2009 at 7:16 PM, Arvind Ajoy wrote:
> > Thanks for the immediate replies.
> >
> > @Vijay : I look forward t
.
@Dave : I am using r3510. Could the problem arise from the fact that ex1.C
uses the function mesh.read( ) is there something special that needs to
be done for Gmsh
meshes?
Regards
Arvind
On Wed, Oct 28, 2009 at 4:56 AM, Roy Stogner wrote:
>
> On Wed, 28 Oct 2009, Arvind Ajoy wrote:
light on this issue?
Thanks.
Regards
Arvind Ajoy
The Gmsh in.geo file is as under
==
a = 1;
// 436
// +++
//
//
//
//
// +++
// 125
Point(1) = {0, 0, 0};
Point(2) = {a, 0, 0} ;
Point(3) = {a
n why libmesh-0.6.2
generates errors against petsc-2.3.3-13; however, I thought that the latest
svn code of libmesh would compile against the latest petsc and slepc
versions.
Any ideas as to how I can resolve these issues? Also, please let me know
which version of Petsc / Slepc works successfully ag
n Thu, Jul 10, 2008 at 6:42 PM, Roy Stogner <[EMAIL PROTECTED]> wrote:
>
> On Thu, 10 Jul 2008, Arvind Ajoy wrote:
>
> (d)Compiled Slepc-2.3.3(including latest patches) from source.
>>
>> With libmesh-0.6.2, this results in the followi
3; however, I thought that the latest
svn code of libmesh would compile against the latest petsc and slepc
versions.
Any ideas as to how I can resolve these issues? Also, please let me know
which version of Petsc / Slepc works successfully against libmesh-0.6.2 and
the
