Vector assignment flawed

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

Bug Description

Current vector assignment is based around duplicating vectors rather than assigning values. We need to support three 'types' of assignment:

1) Assign just values for equal-length vectors. This can work using GenericVector::get_local and GenericVector::set, and should permit the assignment of values to a vector for a vector based on a different backend

2) Copy values for equal length vectors with identical parallel layout (VecCopy in PETSc). This is fast and is supported by backends. Typical use would be updating a vector in a time dependent or nonlinear problem

3) Assign entire object to another. This is duplication (VecDuplicate, followed by VecCopy in PETSc).

A question is what is the best interface for this?

Changed in dolfin:
milestone: none → 1.1.0
status: New → Confirmed
Changed in dolfin:
milestone: 1.1.0 → 1.0-rc2
status: Confirmed → Fix Committed
importance: Undecided → High
Anders Logg (logg)
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.