Ok it's all committed now... let me know if you have any problems with it.
The update of Exodus only caused a couple of compile errors that were easy
to fix.
I did end up modifying both exodus and nemesis to #include in a
couple of files. It was giving warnings about implicit declaration of
mal
On Fri, Jul 11, 2008 at 11:29 AM, Derek Gaston <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 11, 2008 at 9:49 AM, John Peterson <[EMAIL PROTECTED]> wrote:
>>
>> Try to use your best programming judgment as well. If something
>> actually seems dangerous/might cause a problem in some use cases, I
>> woul
On Fri, Jul 11, 2008 at 9:49 AM, John Peterson <[EMAIL PROTECTED]> wrote:
> Try to use your best programming judgment as well. If something
> actually seems dangerous/might cause a problem in some use cases, I
> would definitely fix it. Sometimes warnings are good for stuff like
> that :)
>
Wow
On Jul 11, 2008, at 9:27 AM, Roy Stogner wrote:
>> Should I modify the source?
>
> Only if you can convince the developers upstream to do the same.
>
>> Should I modify CFLAGS to turn these warnings off?
>
> I think so.
>
>> Basically, what's the policy on warnings from contrib?
>
> Officially, I
On Fri, 11 Jul 2008, Derek Gaston wrote:
> I've got it all setup and building... the only issue is that it has
> some warnings (in opt) like so:
>
> Is this going to be acceptable?
Yes, but not preferrable.
> Should I modify the source?
Only if you can convince the developers upstream to do th
On Jul 11, 2008, at 9:18 AM, John Peterson wrote:
> Cool. I assume this is GPL'd or LGPL'd or in some way distributable?
Yeah - it's the same as Exodus... essentially do what you like but
retain the COPYRIGHT file.
> I think if at all possible try to fix any warnings under our normal
> compila
On Fri, Jul 11, 2008 at 10:12 AM, Derek Gaston <[EMAIL PROTECTED]> wrote:
> All,
>
> I'm adding a new library to contrib: Nemsis. It's the ExodusII
> parallel decomposition API... it will allow us to read and write
> parallel decomposed Exodus files.
Cool. I assume this is GPL'd or LGPL'd or in
All,
I'm adding a new library to contrib: Nemsis. It's the ExodusII
parallel decomposition API... it will allow us to read and write
parallel decomposed Exodus files.
I've got it all setup and building... the only issue is that it has
some warnings (in opt) like so:
ne_gneat.c:82: warning
> Ooops, of course, this is what you are already doing. Sorry, haven't
> had coffee yet :-)
>
> But I still think there may be a way to tell PETSc to avoid
> recomputing the preconditioner at every timestep.
>
From the petsc manual:
"When solving multiple linear systems of the same size with
On Fri, Jul 11, 2008 at 9:12 AM, John Peterson <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 11, 2008 at 2:15 AM, Mathias Nenning <[EMAIL PROTECTED]> wrote:
>>
>> So, is there a easy way to handle this problem...
>>
>
> You may need to look around the petsc documentation. I believe you
> can also use L
On Fri, Jul 11, 2008 at 2:15 AM, Mathias Nenning <[EMAIL PROTECTED]> wrote:
>
> So, is there a easy way to handle this problem...
>
You may need to look around the petsc documentation. I believe you
can also use LU as a *preconditioner* in which case the iterative
solver converges in one iteratio
Hello,
I'm using the class NewmarkSystem. For solving the equation system I
need to use a direct Solver.
For this reason I start my programm like this:
./programm -pc_type lu
The only drawback is that the Solver now calculates the LU-decomposition
at every time step, as far as I know.
But this
12 matches
Mail list logo
