Thread Previous • Date Previous • Date Next • Thread Next |
I suggest adding an overloaded version of compute_vertex_values which does not take the mesh as an argument for Functions (since the mesh is available). Any objections? -- Anders
--- Begin Message ---
- To: logg@xxxxxxxxx
- From: Doug Arnold <question210000@xxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 01 Oct 2012 01:25:53 -0000
- Authentication-results: mx.google.com; spf=pass (google.com: best guess record for domain of bounces@xxxxxxxxxxxxx designates 91.189.90.7 as permitted sender) smtp.mail=bounces@xxxxxxxxxxxxx
- Delivered-to: logg@xxxxxxxxx
- Reply-to: question210000@xxxxxxxxxxxxxxxxxxxxx
- Sender: bounces@xxxxxxxxxxxxx
Question #210000 on DOLFIN changed: https://answers.launchpad.net/dolfin/+question/210000 Status: Answered => Solved Doug Arnold confirmed that the question is solved: Many thanks, Anders. BTW, for others reading this, the syntax for dolfin 1.0.0 is vertex_values = np.zeros(mesh.num_vertices(), dtype='d') v.compute_vertex_values(vertex_values, mesh) -- You received this question notification because you are a member of DOLFIN Team, which is an answer contact for DOLFIN.
--- End Message ---
Thread Previous • Date Previous • Date Next • Thread Next |