On Thu, 3 Jun 2010, Vijay S. Mahadevan wrote:
> Also, looking at your changes, I'm just curious on why you removed the
> implicitly_active() check.
Given two options for code, each of which might be faster:
> That could save a lot of "variable.active_on_subdomain()" calls
> since the variable a
Great. I'll update soon and check if everything runs smoothly.
Also, looking at your changes, I'm just curious on why you removed the
implicitly_active() check. That could save a lot of
"variable.active_on_subdomain()" calls since the variable active on
all subdomains is the default case. And, if
On Thu, 3 Jun 2010, Vijay S. Mahadevan wrote:
> I think this should be done for the project_vector method too.
It should.
> I did not do this before but if you think this is required, you can
> add that also.
Done.
The fix I committed to SVN is slightly simpler than your patch. It
works on
I think this should be done for the project_vector method too. I did
not do this before but if you think this is required, you can add
that also.
Vijay
On Thu, Jun 3, 2010 at 8:52 AM, Roy Stogner wrote:
>
> On Thu, 3 Jun 2010, Vijay S. Mahadevan wrote:
>
>> I have encountered segfaults while us
On Thu, 3 Jun 2010, Vijay S. Mahadevan wrote:
> I have encountered segfaults while using projection of exact solution
> when using variables that are defined in specific subdomains. I traced
> the problem to system_projection.C and found that the fix is to check
> whether the variable is defined
Hi,
I have encountered segfaults while using projection of exact solution
when using variables that are defined in specific subdomains. I traced
the problem to system_projection.C and found that the fix is to check
whether the variable is defined for the subdomain in question before
performing the
