On Thu, Dec 6, 2012 at 4:19 PM, Roy Stogner wrote:
>
> If we just switched to devel as the default we'd merely replace "my
> program crashed" with "my program was way too slow", which may even be
> worse in that it's less likely to elicit an email allowing us to help
> fix the problem.
>
Taking P
On Thu, 6 Dec 2012, Kirk, Benjamin (JSC-EG311) wrote:
On Dec 6, 2012, at 3:44 PM, Derek Gaston wrote:
We're a bit closer to "code users" (ie, non-code developers) than
you guys are though... so that policy might make more sense for us.
Really what we should probably be doing is make 'devel
On Dec 6, 2012, at 3:44 PM, Derek Gaston wrote:
> We're a bit closer to "code users" (ie, non-code developers) than you guys
> are though... so that policy might make more sense for us.
Really what we should probably be doing is make 'devel' mode the default -
kinda like PETSc, you can turn of
On Thu, Dec 6, 2012 at 2:22 PM, Roy Stogner wrote:
> My general rule is not to do self-testing in opt mode when that
> testing has any time or memory cost.
>
> Now that you got me to think about it: in this case the costs are "a
> handful of operations and one word of memory per EquationSystems
>
On Thu, 6 Dec 2012, Derek Gaston wrote:
This is what I was thinking as well... although why wrap it in
NDEBUG? This isn't time sensitive... so we should probably just
always do this check.
My general rule is not to do self-testing in opt mode when that
testing has any time or memory cost.
N
On Thu, 6 Dec 2012, John Peterson wrote:
>> It's a bug we should probably be trying to detect and assert against
>> in library code, though... I'm not sure how to do easily without also
>> accidentally asserting against valid usage patterns, though.
>
> And how would you do it in a complicated wa
On Thu, Dec 6, 2012 at 1:59 PM, Roy Stogner wrote:
>
> On Thu, 6 Dec 2012, Jens Lohne Eftang wrote:
>
>> I'm having several EquationSystems,
>
> More importantly, you're attaching several EquationSystems to the same
> mesh. This is a bug; you'll need to instead get a mesh.clone() if you
> want a
On Thu, 6 Dec 2012, Jens Lohne Eftang wrote:
> I'm having several EquationSystems,
More importantly, you're attaching several EquationSystems to the same
mesh. This is a bug; you'll need to instead get a mesh.clone() if you
want a new EquationSystems attached to an identical mesh.
It's a bug w
Hi all,
I'm having several EquationSystems, and also several Systems within each
EquationSystems, and I'm using ExodusII_IO().write_equation_systems()
for plotting.
In optimized mode I do get correct results, but in devel or debug mode I
get an error when plotting. I've cooked up a minimalisti
