OK, interesting. It wasn't identified and fixed as far as I know (I
wasn't able to reproduce the bug on my system)... sounds like it
randomly stopped manifesting!
Dave
On 01/25/2012 03:59 PM, Roy Stogner wrote:
>
> This bug has gone away, and I reluctantly have to ask: did it actually
> get i
This bug has gone away, and I reluctantly have to ask: did it actually
get identified and fixed, or did it just randomly stop manifesting
when other changes were made? ;-)
---
Roy
> On 12/15/2011 09:35 AM, Roy Stogner wrote:
>>
>> I can't seem to reproduce it easily, myself! BuildBot is showin
Random number generation has caused us many issues in MOOSE as well.
Long ago we bundled in a free platform independent random number
generator which resolved all of these issues. I don't know if we'd
want to go those extremes in the libMesh library but it has worked
well for us.
Cody
Sent from
On Thu, 15 Dec 2011, John Peterson wrote:
> On Thu, Dec 15, 2011 at 7:35 AM, Roy Stogner wrote:
>>
>> but I've no idea what causes the difference.
>
> Hmm... just a thought: the RB stuff uses some random number generation stuff.
>
> Perhaps this could explain different greedy parameter selectio
John's right that there are random numbers in general, but in that
example the training sets are not randomly generated. But the way the
algorithm chooses the next parameter is by finding the one with the
maximum error bound, and as you can see this problem has the same error
bound at two diffe
On Thu, Dec 15, 2011 at 7:35 AM, Roy Stogner wrote:
>
> but I've no idea what causes the difference.
Hmm... just a thought: the RB stuff uses some random number generation stuff.
Perhaps this could explain different greedy parameter selection order
on different systems, but not outright failure?
I can't seem to reproduce it easily, myself! BuildBot is showing a
failure every time with my default build:
loadmodules intel tbb mpich2/1.2.1 mkl-pecos petsc slepc trilinos glpk vtk
&&./configure --enable-everything
but it's showing success with literally every other build I've
configured it
hmm, I can't seem to reproduce this error...?
On 12/14/2011 10:38 PM, Roy Stogner wrote:
>
> We're hitting this with my plain standard --enable-everything build,
> too:
>
> ...
>
> Basis dimension: 19
> Performing RB solves on training set
> Maximum (absolute) error bound is 0.199127
>
