dolfin team mailing list archive

[Joachim Berdal Haga <jobh@xxxxxxxxx>]

Forgot to CC list.


On 6 February 2013 00:00, Joachim Berdal Haga <jobh@xxxxxxxxx> wrote:

> Plotting must be updated, but that should be simple enough. Line 344 of
> VTKPlottableMesh.cpp):
>         values->SetValue(3*i+d, indata[i+num_vertices*d]);
>
> ...indata is the result of compute_vertex_values, d is the DOLFIN spatial
> dimension, vtk spatial dimension is always 3.
>
> -j.
>
>
>
> On 5 February 2013 23:41, Anders Logg <logg@xxxxxxxxx> wrote:
>
>> On Tue, Feb 05, 2013 at 07:33:37PM +0000, Garth N. Wells wrote:
>> > For mixed/vector-values functions,
>> > GenericFunction::compute_vertex_values(..) returns the values in a
>> > vector as
>> >    [u0, u1, u2, u3, u4, . . . . . . , v0, v1, v2, v3, . . . , w0, w1,
>> > w2, w3, . . . .]
>> > This isn't very convenient for post-processing, where the order is
>> usually
>> >    [u0, v0, w0, u1, v1, w1, u2, v2, w2, . . . un, vn, wn]
>> > Any opinions on changing the ordering?
>>
>> This was at some point decided by the way in which Viper preferred to
>> get the values. Since Viper has been replaced, we're free to change as
>> long as there is no issue with the reimplemented plotting.
>>
>> This feature is low-level enough that we might change it at will, but
>> we need to remember it for the next set of release notes.
>>
>> --
>> Anders
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dolfin
>> Post to     : dolfin@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dolfin
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>