On 6/2/10 3:42 PM, Roy Stogner wrote:
>
> On Wed, 2 Jun 2010, Boyce Griffith wrote:
>
On 6/1/10 7:19 PM, Roy Stogner wrote:
>
> On Tue, 1 Jun 2010, Boyce Griffith wrote:
>
>> I guess there must be some other necessary DOFs in the default
>> send_list?
>
> Not for
On Wed, 2 Jun 2010, Boyce Griffith wrote:
>>> On 6/1/10 7:19 PM, Roy Stogner wrote:
On Tue, 1 Jun 2010, Boyce Griffith wrote:
> I guess there must be some other necessary DOFs in the default
> send_list?
Not for enforce_constraints_exactly(), there shouldn't...
>> On 6/1/10 7:19 PM, Roy Stogner wrote:
>>>
>>> On Tue, 1 Jun 2010, Boyce Griffith wrote:
>>>
I guess there must be some other necessary DOFs in the default
send_list?
>>>
>>> Not for enforce_constraints_exactly(), there shouldn't...
And indeed there don't appear to be. I was initial
On 6/1/10 7:42 PM, Roy Stogner wrote:
>
> On Tue, 1 Jun 2010, Boyce Griffith wrote:
>
>> On 6/1/10 7:19 PM, Roy Stogner wrote:
>>>
>>> On Tue, 1 Jun 2010, Boyce Griffith wrote:
>>>
I guess there must be some other necessary DOFs in the default
send_list?
>>>
>>> Not for enforce_constrai
On Tue, 1 Jun 2010, Boyce Griffith wrote:
> On 6/1/10 7:19 PM, Roy Stogner wrote:
>>
>> On Tue, 1 Jun 2010, Boyce Griffith wrote:
>>
>>> I guess there must be some other necessary DOFs in the default send_list?
>>
>> Not for enforce_constraints_exactly(), there shouldn't...
>
> Well, using the
On 6/1/10 7:19 PM, Roy Stogner wrote:
>
> On Tue, 1 Jun 2010, Boyce Griffith wrote:
>
>> I guess there must be some other necessary DOFs in the default send_list?
>
> Not for enforce_constraints_exactly(), there shouldn't...
Well, using the full send list seems to work correctly, at least in the
On Tue, 1 Jun 2010, Boyce Griffith wrote:
> I guess there must be some other necessary DOFs in the default send_list?
Not for enforce_constraints_exactly(), there shouldn't...
In the library it's a little complicated because we have to be sure to
expand out recursive constraints before adding t
On 6/1/10 6:47 PM, Boyce Griffith wrote:
>
>
> On 6/1/10 6:30 PM, Roy Stogner wrote:
>>
>> On Tue, 1 Jun 2010, Boyce Griffith wrote:
>>
>>> On 6/1/10 6:14 PM, Roy Stogner wrote:
>>>
Would a couple read-only accessor functions,
DofMap::constraints_begin() and DofMap::constraints_end(), b
On 6/1/10 6:30 PM, Roy Stogner wrote:
>
> On Tue, 1 Jun 2010, Boyce Griffith wrote:
>
>> On 6/1/10 6:14 PM, Roy Stogner wrote:
>>
>>> Would a couple read-only accessor functions,
>>> DofMap::constraints_begin() and DofMap::constraints_end(), be
>>> sufficient?
>>
>> I think so.
>
> I settled on c
On Tue, 1 Jun 2010, Boyce Griffith wrote:
> On 6/1/10 6:14 PM, Roy Stogner wrote:
>
>> Would a couple read-only accessor functions,
>> DofMap::constraints_begin() and DofMap::constraints_end(), be
>> sufficient?
>
> I think so.
I settled on constraint_rows_begin()/end() for the names; let me kno
On 6/1/10 6:14 PM, Roy Stogner wrote:
>
> On Tue, 1 Jun 2010, Boyce Griffith wrote:
>
>> On 6/1/10 6:01 PM, Roy Stogner wrote:
>>>
>>> On Tue, 1 Jun 2010, Boyce Griffith wrote:
>>>
Is there a mechanism to access the data stored in _dof_constraints,
i.e., to loop over the list of constra
On Tue, 1 Jun 2010, Boyce Griffith wrote:
> On 6/1/10 6:01 PM, Roy Stogner wrote:
>>
>> On Tue, 1 Jun 2010, Boyce Griffith wrote:
>>
>>> Is there a mechanism to access the data stored in _dof_constraints,
>>> i.e., to loop over the list of constrained rows?
>>
>> for (DofConstraints::const_ite
On 6/1/10 6:01 PM, Roy Stogner wrote:
>
> On Tue, 1 Jun 2010, Boyce Griffith wrote:
>
>> Is there a mechanism to access the data stored in _dof_constraints,
>> i.e., to loop over the list of constrained rows?
>
> for (DofConstraints::const_iterator it=_dof_constraints.begin();
> it != _dof_constr
On Tue, 1 Jun 2010, Boyce Griffith wrote:
> Is there a mechanism to access the data stored in _dof_constraints, i.e., to
> loop over the list of constrained rows?
for (DofConstraints::const_iterator it=_dof_constraints.begin();
it != _dof_constraints.end(); ++it)
{
unsign
>> Would it work simply to append the send_list associated with the
>> DofMap to my list of ghosted dofs, e.g.,
>>
>> const vector& send_list = dof_map.get_send_list();
>> vector ghost_dofs = ...;
>> ghost_dofs.insert(ghost_dofs.end(), send_list.begin(),
>> send_list.end());
>> AutoPtr > ghosted_so
On Tue, 1 Jun 2010, Boyce Griffith wrote:
> Would it work simply to append the send_list associated with the DofMap to my
> list of ghosted dofs, e.g.,
>
> const vector& send_list = dof_map.get_send_list();
> vector ghost_dofs = ...;
> ghost_dofs.insert(ghost_dofs.end(), send_list.begin(),
On 6/1/10 4:57 PM, Roy Stogner wrote:
>
> On Tue, 1 Jun 2010, Boyce Griffith wrote:
>
>> Are there specific ghost DOFs that are required if I wish to enforce DOF
>> constraints, e.g., periodic boundary conditions?
>
> You should only need to ensure that, on the processor which owns the
> constraine
On Tue, 1 Jun 2010, Boyce Griffith wrote:
> Are there specific ghost DOFs that are required if I wish to enforce DOF
> constraints, e.g., periodic boundary conditions?
You should only need to ensure that, on the processor which owns the
constrained DoF, every dependency of that constrained DoF i
Hi, Folks --
I am working on a code in which I need to make use of a non-standard
parallel distribution of elements to processors. Because this
distribution seems likely not to be well-suited for most operations, I
perform most operations using whatever data distribution is determined
by libM
19 matches
Mail list logo
