On Tue, Jun 17, 2008 at 4:16 PM, John Peterson <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 17, 2008 at 4:02 PM, Roy Stogner <[EMAIL PROTECTED]> wrote:
>>
>> On Tue, 17 Jun 2008, John Peterson wrote:
>>
>>> On Tue, Jun 17, 2008 at 2:11 PM, Benjamin Kirk <[EMAIL PROTECTED]>
>>> wrote:
>>>
Do any of
On Tue, Jun 17, 2008 at 4:02 PM, Roy Stogner <[EMAIL PROTECTED]> wrote:
>
> On Tue, 17 Jun 2008, John Peterson wrote:
>
>> On Tue, Jun 17, 2008 at 2:11 PM, Benjamin Kirk <[EMAIL PROTECTED]>
>> wrote:
>>
>>> Do any of you have access to "The finite element method" vol. 1 by
>>> Zienkiewicz & Taylor?
On Tue, 17 Jun 2008, John Peterson wrote:
> On Tue, Jun 17, 2008 at 2:11 PM, Benjamin Kirk <[EMAIL PROTECTED]> wrote:
>
>> Do any of you have access to "The finite element method" vol. 1 by
>> Zienkiewicz & Taylor? Pg. 222 is referenced as the source for orders 1-5,
>> and I want to make sure th
> I do like CPPUNIT. It has it's drawbacks... but there's not really
> any reason to use anything else. In particular Boost.Test has _many_
> drawbacks (as Boost stuff often does)... mainly that it's just tough
> to work with. CPPUNIT is straightforward and does it's job well.
OK, the libme
I do like CPPUNIT. It has it's drawbacks... but there's not really
any reason to use anything else. In particular Boost.Test has _many_
drawbacks (as Boost stuff often does)... mainly that it's just tough
to work with. CPPUNIT is straightforward and does it's job well.
Here at INL I'm
> That's a nasty one. I would never have seen that -- I'd be to focused
> on making sure the weights and points were correct to worry if the
> vector was too long!
Yeah, if you ran on pure tets you likely were OK as the extra entries were
default constructed to 0 weight. When I ran a hex or pris
On Tue, 17 Jun 2008, Benjamin Kirk wrote:
> Have we settled in on CPPUNIT as our unit-testing framework? I'm ready to
> reorganize the unit test directory if so.
Sounds good to me. It looks like Boost.Test and something called
CxxTest have a few advantages, but nothing worth switching for.
---
On Tue, Jun 17, 2008 at 2:11 PM, Benjamin Kirk <[EMAIL PROTECTED]> wrote:
> Have we settled in on CPPUNIT as our unit-testing framework? I'm ready to
> reorganize the unit test directory if so.
>
> On a totally related issue, I was just expanding the quadrature unit tests
> and found a bug in QGau
Have we settled in on CPPUNIT as our unit-testing framework? I'm ready to
reorganize the unit test directory if so.
On a totally related issue, I was just expanding the quadrature unit tests
and found a bug in QGauss for Tets at 5th-order. The issue is that the
points/weights vector is resized t
Would it be easy to do one or more of the following:
1) Allow --enable-ifem compiled versions of libMesh to read
--disable-ifem generated restart files
2) Generate more useful error messages when such a read attempt (or
the reverse sort of read attempt) fails?
There's a lot more we could eventu
10 matches
Mail list logo
