Remove Restriction from {Generic}DofMap

[Prof Garth Wells]

See mailing list thread:

http://fenicsproject.org/pipermail/fenics/2013-September/000543.html

[Prof Garth Wells]

I'm happy to rip this out before releasing 1.4 if there are no complaints.

[Martin Sandve Alnæs]

It still has uses and no alternative, and there's no value in ripping it out before the release so I'd like to keep it.

[Prof Garth Wells]

What are its practical uses (i.e., is it any good for solving non-trivial problems)?

[Martin Sandve Alnæs]

I will use it for prototyping optimal control problems, awaiting a better implementation.

[Prof Garth Wells]

I'm going to need to take this out very soon (possibly temporarily) in order to straighten out, improve efficiency and dramatically reduce memory usage for dofmaps.

[Prof Garth Wells]

Fix Issue #118.

Remove Restriction code from dofmap, etc. Was not working with dofmap construction. Functionality will be available when mesh views are in place.

→ <<cset 717e98e8b318>>

[Maximilian Albert]

It might be worth mentioning the fact that Restriction was removed in the release notes [1] for FEniCS 1.5, ideally with a note which alternatives there are, or at least when they are expected to be available.

Is there currently a workaround to achieve the same or similar functionality? Some of my code has stopped working because of the removal of Restriction. Do I need to wait for the next release until MeshView is available, or is there an alternative (even if it is kludgy)?

[1] http://fenicsproject.org/releases/1.5/index.html

[Prof Garth Wells]

Removing milestone: 1.5 (automated comment)

[Chaffra Affouda]

Is restriction of a function space to a subdomain still broken in the trunk version? Is there a workaround?