Implementation of changing lambdas and mus over subdomain interface
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 14
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
```cpp
void LinElastSolver::BuildDomainOperators()
{
// SanityCheckOnCoeffs();
as.SetSize(numSub);
for (int m = 0; m < numSub; m++)
{
as[m] = new BilinearForm(fes[m]);
as[m]->AddDomainIntegrator(new ElasticityIntegrator(*(lambda_c[m]), *(mu_c[m])));
if (full_dg)
{
as[m]->AddInteriorFaceIntegrator(
new DGElasticityIntegrator(*(lambda_c[m]), *(mu_c[m]), alpha, kappa));
}
}
a_itf = new InterfaceForm(meshes, fes, topol_handler);
a_itf->AddIntefaceIntegrator(new InterfaceDGElasticityIntegrator(lambda_c[0], mu_c[0], alpha, kappa));
}
```
How should the last line be handled?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with LinElastSolver::BuildDomainOperators and inspect InterfaceDGElasticityIntegrator alongside ElasticityIntegrator and DGElasticityIntegrator. Determine how changing lambda_c and mu_c across subdomains should be represented at the interface; the work is done when the final interface-integrator construction handles those coefficients consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100