On Mon, 7 Apr 2014, David Knezevic wrote:
>>> This does sound nasty... Do you see a good general solution here?
>>
>> I think it should always be safe to "move" a constraint onto a
>> not-yet-constrained dof. The only remaining catch is the interaction
>> with PeriodicBoundary constraints, wher
>>> The first nasty case I can think of is the combination of a simple
>>> constraint on a vertical or horizontal wall (deltax = 0 or deltay = 0,
>>> obviously gets applied to the deltax dof or the deltay dof
>>> respectively) with a previously applied compound constraint on a
>>> neighboring diag
On Mon, 7 Apr 2014, David Knezevic wrote:
>> Nope. The solver should easily handle multiple constraints
>> *affecting* a dof, but since we write each constraint row into the
>> matrix in place of the row corresponding to some dof's test function,
>> we need to have a way of choosing which dof ge
>>
>> I would hope that the solver can handle the case of multiple constraints
>> on a dof.
>
> Nope. The solver should easily handle multiple constraints
> *affecting* a dof, but since we write each constraint row into the
> matrix in place of the row corresponding to some dof's test function,
>
On Mon, 7 Apr 2014, David Knezevic wrote:
> On 04/06/2014 11:50 PM, Roy Stogner wrote:
>>
>> Where to start is "what do we want the API to look like"; I'm not even
>> sure if this can cleanly fit in DirichletBoundary or if we'd want to
>> create some kind of new CoupledDirichletBoundary (or bette
On 04/06/2014 11:50 PM, Roy Stogner wrote:
>
> On Sun, 6 Apr 2014, David Knezevic wrote:
>
>> Is it possible to impose a linear constraint on the variables in a
>> system using a DirichletBoundary object?
>
> Currently, no.
>
>> The case I'm thinking of is in elasticity, where you want set the
>> d
