On Fri, 16 Apr 2010, Boyce Griffith wrote:
> On 4/16/10 1:15 PM, Roy Stogner wrote:
>>
>> On Fri, 16 Apr 2010, Boyce Griffith wrote:
>>>
>>> Thanks! Another hopefully quick question --- what is the argument i to
>>> Mesh::point()? Is i supposed to be a dof index? (I am trying to
>>> extract the
On 4/16/10 1:15 PM, Roy Stogner wrote:
>
> On Fri, 16 Apr 2010, Boyce Griffith wrote:
>>
>> Thanks! Another hopefully quick question --- what is the argument i to
>> Mesh::point()? Is i supposed to be a dof index? (I am trying to
>> extract the values and spatial locations of each of the local DO
On Fri, 16 Apr 2010, Boyce Griffith wrote:
> On 4/16/10 12:45 PM, Roy Stogner wrote:
>>
>> On Fri, 16 Apr 2010, Boyce Griffith wrote:
>>
>>> What is the mapping from the libMesh DOF indexing scheme to the global
>>> PETSc indexing scheme?
>>
>> libMesh index i -> PETSc global index i. :-)
>>
On 4/16/10 12:45 PM, Roy Stogner wrote:
>
> On Fri, 16 Apr 2010, Boyce Griffith wrote:
>
>> What is the mapping from the libMesh DOF indexing scheme to the global
>> PETSc indexing scheme?
>
> libMesh index i -> PETSc global index i. :-)
>
> Not the most efficient thing to do with ghosted vectors
On Fri, 16 Apr 2010, Boyce Griffith wrote:
> What is the mapping from the libMesh DOF indexing scheme to the global
> PETSc indexing scheme?
libMesh index i -> PETSc global index i. :-)
Not the most efficient thing to do with ghosted vectors, but any
future change would be by adding a new API,
Hi, Folks --
What is the mapping from the libMesh DOF indexing scheme to the global
PETSc indexing scheme? And if the mapping is non-trivial, is there an
easy way to access it?
Thanks!
-- Boyce
--
Download Intel® Par
