On Wed, Aug 20, 2008 at 12:12 PM, Benjamin Kirk <[EMAIL PROTECTED]>wrote:
> I will focus my effort on initializing the sparse matrix sparsity
> pattern...
Sounds good.
I think that in order to stay out of your way, I'm going to start writing
the interface for the AztecOO linear solver.
Derek
-
> Let's coordinate on this. Like I mentioned a little while ago, the hardest
> thing for me to get a grasp on is the parallel map / graph and how that
> translates into an Epetra_Map nudge, nudge wink wink
I will focus my effort on initializing the sparse matrix sparsity pattern...
>> You know, this is how I originally had things set up, but it seems
>> to be at
>> odds with the "make install" target. Try configuring trilinos with
>> the
>> --prefix="$TRILINOS_DIR" , then do a make install, and you will see
>> what I
>> mean.
>
> Aha! Now, what was in there makes more sens
On Aug 20, 2008, at 12:00 PM, Benjamin Kirk wrote:
> You know, this is how I originally had things set up, but it seems
> to be at
> odds with the "make install" target. Try configuring trilinos with
> the
> --prefix="$TRILINOS_DIR" , then do a make install, and you will see
> what I
> mean
> I just committed a change that modifies what the $TRILINOS_DIR environment
> variable should be set to. I'm not really sure what I was thinking before...
> but now it makes more sense.
>
> What you do is set it to the build directory in which you built Trilinos.
> This is more in line with the
I just committed a change that modifies what the $TRILINOS_DIR environment
variable should be set to. I'm not really sure what I was thinking
before... but now it makes more sense.
What you do is set it to the build directory in which you built Trilinos.
This is more in line with the Trilinos Use
On Wed, Aug 20, 2008 at 11:32 AM, Benjamin Kirk <[EMAIL PROTECTED]>wrote:
> In other news, I just installed trilinos/8.0.8 and will see if I can push
> the integration a little further, again..
>
Ben... I'm also working on this right now (with Trilinos 8.0.8). I'm going
to commit a few changes s
On Wed, Aug 20, 2008 at 11:20 AM, Roy Stogner <[EMAIL PROTECTED]> wrote:
> Yup, I committed it to libmesh_common.h this morning.
Thanks!
> We'll eventually want to handle those differently, I think, but not
> before 0.6.3 final. I've thought more about your idea of putting a
> location-specif
>> Uh oh. What specifically are you referring to being not implemented?
>
> Specifically... all of the Trilinos stuff has NotImplemented throws in it.
>
> Of course, people really shouldn't be hitting that anyway (we don't advertise
> the Trilinos support yet). But, if some enterprising person
On Wed, 20 Aug 2008, Derek Gaston wrote:
Specifically... all of the Trilinos stuff has NotImplemented throws in
it.
Of course, people really shouldn't be hitting that anyway (we don't
advertise the Trilinos support yet). But, if some enterprising person
did compile with Trilinos support and t
On Wed, Aug 20, 2008 at 9:32 AM, John Peterson <[EMAIL PROTECTED]> wrote:
> Uh oh. What specifically are you referring to being not implemented?
>
Specifically... all of the Trilinos stuff has NotImplemented throws in it.
Of course, people really shouldn't be hitting that anyway (we don't
adver
>> But if we ship a release (like we just did) which has NotImplemented
>> stuff being thrown then we're not giving either our users or
>> ourselves very much info when someone runs into these cases.
Uh oh. What specifically are you referring to being not implemented?
--
John
-
Oh, and I almost forgot to mention:
> If our intention is to really never use NotImplemented (except for
> whenever we're internally developing new features) that might be
> fine.
I'm thinking that NotImplemented throws will become a permanent part
of some library components: if someone tries to
On Wed, 20 Aug 2008, Derek Gaston wrote:
> For now, I do think I'll add another constructor for NotImplemented
> that takes a string so that you can do:
>
> LIBMESH_THROW(libMesh::NotImplemented("Something::somehwere()");
I don't like that; in theory we can get at least that much info
automatica
The macro sounds more like what I was thinking
That said, the idea behind being able to pass a string in is that all
of your errors could have the same formatting. This is opposed to
just outputting something to std::cerr yourself first then
throwing which means every error will pro
15 matches
Mail list logo
