On Wed, Apr 20, 2016 at 3:32 PM, Roy Stogner
wrote:
>
> On Wed, 20 Apr 2016, John Peterson wrote:
>
> We should probably just call prepare_for_use() from
>> TriangleInterface::triangulate() to avoid issues like this...
>>
>
> Agreed. That should be safe for most old code, too; duplicate calls
>
On Wed, 20 Apr 2016, John Peterson wrote:
> We should probably just call prepare_for_use() from
> TriangleInterface::triangulate() to avoid issues like this...
Agreed. That should be safe for most old code, too; duplicate calls
to prepare_for_use() are redundant but not forbidden.
(The only ex
On Wed, Apr 20, 2016 at 2:31 PM, Praphat Fernandes <
[email protected]> wrote:
> Thanks John! Calling mesh.prepare_for_use() right after the triangulation
> step did the trick.
>
> What does mesh.prepare_for_use do ?
>
A lot of different things actually, but in this case I think probabl
Thanks John! Calling mesh.prepare_for_use() right after the triangulation
step did the trick.
What does mesh.prepare_for_use do ?
Thanks for your help.
Regards,
Xavier
On Wed, Apr 20, 2016 at 1:09 PM, John Peterson wrote:
>
>
> On Wed, Apr 20, 2016 at 1:54 PM, Praphat Fernandes <
> fernande
On Wed, Apr 20, 2016 at 1:54 PM, Praphat Fernandes <
[email protected]> wrote:
> Hello,
>
> I'm attempting to use a mesh(like the one generated in Misc Example 6,
> using the Triangle Interface) to solve a Poisson problem like Intro.
> Example 3.
>
> Here are the problems I encounter:
>
Hello,
I'm attempting to use a mesh(like the one generated in Misc Example 6,
using the Triangle Interface) to solve a Poisson problem like Intro.
Example 3.
Here are the problems I encounter:
1. Within the assemble_poisson function,
MeshBase::const_element_iterator el =
mesh.active_lo
