Comments (8)
If we take a look at https://github.com/precice/tutorials/issues/13#issuecomment-443029988, we see that RBF functions are not necessarily the ideal choice for interpolation.
If we use linear interpolation instead, we need connectivity information and we have to generalize the implementation in f69a016 to support arbitrary coupling interfaces. Currently only straight boundaries that are parallel to the y-axis are supported.
Using linear interpolation with connectivity information allows us to use the nearest projection mapping, in the end. This will be helpful for working on https://github.com/precice/tutorials/issues/11.
from fenics-adapter.
Can we directly access the interpolant inside preCICE to avoid the additional interpolation step?
Not really. Also, another problem then would be how to convert this interpolant to a description that FEniCS understands.
Does FEniCS allow defining boundary conditions / expressions from nodal data instead of functions?
Can we ask on a FEniCS mailing list? This should be a quite natural feature. Also needed if you want to read boundary conditions from a file etc., so others should also have this problem.
This should not be something to implement in the adapter, but directly in FEniCS.
from fenics-adapter.
Another possible approach for creating an interpolant from point data: use (generalized) moving least squares. See work of Paul Kuberry for more details. Compadre toolkit offers a Python Interface and might be useful.
from fenics-adapter.
If we create a piecewise linear interpolant (like e.g. here), this has a major problem: The FEniCS solver always "sees" a piecewise linear function, even if the point data that we interpolate does not originate from such a function. If we, for example, use a second or higher order function space as finite element basis (see here), this will lead to problems like an incorrect flux computation. We should use higher order interpolation instead (see here) to avoid problems.
from fenics-adapter.
In Nutils, we can simply use the Gauss Points of the function. This completely avoids an additional interpolation step inside the adapter. See here.
from fenics-adapter.
The fenics-adapter now provides means for the user to choose between the two strategies RBF interpolation and polynomial interpolation (7afb0e0).
from fenics-adapter.
In #38 FEniCS' PointSource
has been used for correctly dealing with point sources (e.g. nodal forces) that are mapped in a conservative fashion. This is an alternative strategy to the interpolation of point data as explained above. Note that the approach based on interpolation gave wrong results and the approach using a PointSource
is the correct one.
More details on this will follow in the thesis of @richahert
from fenics-adapter.
This issue is closed by #83. @richahert 's thesis can be found here: https://mediatum.ub.tum.de/node?id=1520579
from fenics-adapter.
Related Issues (20)
- Compute CouplingExpression from point data via Minimization on P0DG function space HOT 9
- Reactivate systemtest HOT 2
- from fenics import * avoids publishing HOT 2
- Properly define FEniCS dependency? HOT 3
- Outdated documentation regarding actions HOT 4
- Homogenize citation information HOT 4
- Support FEniCSx HOT 1
- The Config object can not find the adapter configuration file HOT 1
- Error at any run: "Illegal instruction (core dumped)" on Ubuntu 21.10
- Restrictions on using adapter for 3D cases HOT 7
- Painfully slow mapping with volumetric coupling HOT 1
- Installation issues for fenics version (2:0.4.1.2) HOT 5
- Mesh connectivity information not defined for all scenarios in 2D and 3D cases
- Remove duplicates in citation information HOT 1
- precice/fenics-adapter:latest is not stable but the develop release HOT 2
- Volume coupling and nearest projection mapping do not integrate well and are untested
- recommended install fails under Ubuntu HOT 2
- Make limitations of the adapter more evident in the documentation
- Double-boundary points warning HOT 2
- Support checkpointing of multiple fields
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fenics-adapter.