BoundaryMesh is wrong in 1D

Bug #1063013 reported by Garth Wells
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DOLFIN
Fix Released
Medium
Garth Wells

Bug Description

BoundaryMesh gets it wrong in 1D (which is breaking 1D in parallel). Instead of picking up the end vertices, it picks up vertices one position away from the end. The code

    from dolfin import *
    mesh = UnitInterval(3)
    bmesh = BoundaryMesh(mesh)
    info(bmesh, True)

prints

    0: 0.333333
    1: 0.666667

when it should print

    0: 0.0
    1: 1.0

Anders Logg (logg)
Changed in dolfin:
status: New → Confirmed
assignee: nobody → Anders Logg (logg)
Changed in dolfin:
status: Confirmed → In Progress
assignee: Anders Logg (logg) → Garth Wells (garth-wells)
importance: Undecided → Medium
Changed in dolfin:
status: In Progress → Fix Committed
Changed in dolfin:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.