Number of coordinates returned by getVtxArrCoords
Tim Tautges
tautges at mcs.anl.gov
Tue Oct 19 20:26:39 CDT 2010
Fine.
- tim
On 10/19/2010 09:10 AM, Carl Ollivier-Gooch wrote:
> Hello, all.
>
> Ting sent me an email asking why a 2D mesh is required to return three
> coordinates for every vert from this call. So I went trolling in the
> email archives, and found that the most recent discussion we had of this
> (at least in email) was last April. Summarizing that discussion,
> hopefully correctly:
>
> Mark Miller: Prefers that we specify one or the other, with a preference
> towards two coords for the 2D case.
>
> Carl and Karen: Prefer that we specify one or the other, with no
> particular preference between 2 and 3 coords in 2D.
>
> Tim: Prefers to leave this implementation dependent.
>
> Given that status, I propose the following as a (near) consensus:
>
> getVtxArrCoords will return two coords per vertex in 2D and three in 3D
> (that is, the number of coordinates returned will be num_verts_returned
> * geom_dim). Unless I hear violent objections in the interim, I'll
> update the docs (and unit test) Friday morning.
>
> Carl
>
--
================================================================
"You will keep in perfect peace him whose mind is
steadfast, because he trusts in you." Isaiah 26:3
Tim Tautges Argonne National Laboratory
(tautges at mcs.anl.gov) (telecommuting from UW-Madison)
phone: (608) 263-8485 1500 Engineering Dr.
fax: (608) 263-4499 Madison, WI 53706
More information about the tstt-interface
mailing list