FEMContext users,
Release 0.9.2 contained an update to the FEMContext API in preparation for
hiding public members of the FEMContext class. The original impetus was for
having a clean API that worked with vector-valued elements. 0.9.2 is the
last release where one can get by without this API. The
All -
libMesh-0.9.2 is available for download. There have been a few minimal bug
fixes since -rc1. Additionally, the new blocked DOF support has been defaulted
to off, but can be enabled via ./configure.
Important changes include
* PETSc 3.4 support
* PETSc BAIJ matrix support for blocke
On Jul 18, 2013, at 9:12 AM, Roy Stogner wrote:
> Give me an hour to test tweaking up a tolerance in adjoints_ex3 before
> you tag? That still fails on buildbot in a few corner configurations
> (single precision, highly parallel stuff depending on partitioning).
>
> There's one other buildbot f
On Thu, 18 Jul 2013, Kirk, Benjamin (JSC-EG311) wrote:
On Jul 18, 2013, at 9:03 AM, Roy Stogner wrote:
Perhaps we should default the blocked matrix configure option to
disabled until we know more?
… I'm OK with that solution. I can update the change log to
describe the new feature as opt
On 07/18/2013 12:08 PM, Kirk, Benjamin (JSC-EG311) wrote:
> On Jul 18, 2013, at 9:03 AM, Roy Stogner wrote:
>
>> On Thu, 18 Jul 2013, David Knezevic wrote:
>>
>>> The issue for me is that this also arises in a lot of application codes
>>> that me and my colleagues use.
>> Hmm... I wonder if this
On Jul 18, 2013, at 9:03 AM, Roy Stogner wrote:
>
> On Thu, 18 Jul 2013, David Knezevic wrote:
>
>> The issue for me is that this also arises in a lot of application codes
>> that me and my colleagues use.
>
> Hmm... I wonder if this is the case for less savvy users as well.
I don't think so
On Thu, 18 Jul 2013, David Knezevic wrote:
> The issue for me is that this also arises in a lot of application codes
> that me and my colleagues use.
Hmm... I wonder if this is the case for less savvy users as well.
Perhaps we should default the blocked matrix configure option to
disabled until
On 07/18/2013 12:01 PM, Kirk, Benjamin (JSC-EG311) wrote:
> On Jul 18, 2013, at 8:59 AM, David Knezevic
> wrote:
>
>> The issue for me is that this also arises in a lot of application codes
>> that me and my colleagues use. We can't use
>> '-mat_new_nonzero_allocation_err false' for larger scale
On Thu, 18 Jul 2013, Kirk, Benjamin (JSC-EG311) wrote:
> On Jul 4, 2013, at 8:15 AM, David Knezevic wrote:
>
>>> The reason I ask is that we've identified what I believe to be a bug
>>> with Petsc block matrices where they are not honoring
>>> KEEP_NONZERO_PATTERN. This is causing a ton of mall
On Jul 18, 2013, at 8:59 AM, David Knezevic wrote:
> The issue for me is that this also arises in a lot of application codes
> that me and my colleagues use. We can't use
> '-mat_new_nonzero_allocation_err false' for larger scale problems since
> it runs very slowly (presumably due to the mall
On 07/18/2013 11:54 AM, Kirk, Benjamin (JSC-EG311) wrote:
> On Jul 4, 2013, at 8:15 AM, David Knezevic wrote:
>
>>> The reason I ask is that we've identified what I believe to be a bug
>>> with Petsc block matrices where they are not honoring
>>> KEEP_NONZERO_PATTERN. This is causing a ton of ma
On Jul 4, 2013, at 8:15 AM, David Knezevic wrote:
>> The reason I ask is that we've identified what I believe to be a bug
>> with Petsc block matrices where they are not honoring
>> KEEP_NONZERO_PATTERN. This is causing a ton of mallocs for us in
>> MOOSE. So, for now, we're just disabling bloc
12 matches
Mail list logo
