mesh-entities-broken
Bug #713081 reported by
Anders Logg
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DOLFIN |
Fix Released
|
High
|
Unassigned |
Bug Description
The following code prints 3, 0 but should print 3, 3:
from dolfin import *
mesh = UnitSquare(2, 2)
cell = Cell(mesh, 0)
print cell.num_
Perhaps a broken typemap for uint*?
Changed in dolfin: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → 0.9.10 |
Changed in dolfin: | |
status: | Confirmed → Fix Committed |
Changed in dolfin: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This looks like a Heisenbug to me!
When I put a print statement into the typemap it works, when I remove the
print statement it appears...
With print statement ("size connectivity X"):
In [4]: print cell.num_ entities( 0), len(cell. entities( 0))
3size connectivity 3
3
without:
In [4]: print cell.num_ entities( 0), len(cell. entities( 0))
3 0
Puzzled...
Johan
On Friday February 4 2011 05:05:23 Anders Logg wrote: entities( 0), len(cell. entities( 0))
> Public bug reported:
>
> The following code prints 3, 0 but should print 3, 3:
>
> from dolfin import *
>
> mesh = UnitSquare(2, 2)
> cell = Cell(mesh, 0)
>
> print cell.num_
>
> Perhaps a broken typemap for uint*?
>
> ** Affects: dolfin
> Importance: High
> Status: Confirmed
>
> ** Changed in: dolfin
> Status: New => Confirmed
>
> ** Changed in: dolfin
> Importance: Undecided => High
>
> ** Changed in: dolfin
> Milestone: None => 0.9.10