- Use
copy(deepcopy=True)
when checkpointing to make checkpointing more user-friendly and secure. IMPORTANT: might increase runtime, please open an issue if you face serious problems. #172 - Add unit tests for checkpointing. #173
- Add required version of
mpi4py
to<4
to avoid crash during installation. #181 - Remove checks for FEniCS installation and python3 from
setup.py
since the approach is deprecated. #182
- Additionally support checkpoints being provided as a list or tuple (of FEniCS Functions). #170
- Drop support for preCICE 2.x version, as this is a breaking release.
- Update adapter to use preCICE v3 API #153.
- Remove functionality to define mesh connectivity in 2D cases in the form of triangles due to lack of testing and compatibility problems (might be added again). See #162.
- Adding CITATION.cff to link the adapter repository to the relevant publication in the journal SoftwareX.
- Add functionality to define mesh connectivity in 2D cases in the form of triangles.
- Adding functionality for 3D cases with PointSource objects at coupling boundaries. See PRs #133, #146 and #147.
- Fixing an issue of the
config
object not being able to find the adapter configuration file in a Jupyter notebook. See PR #144
- Reduce complexity of initialization to reduce runtime for large cases. See PR #135
- Raise warning, if FEniCS is not found on system. See PR #130
- Add test for python3 setup.py sdist. See PR #127
- Only warn during initialization, if duplicate boundary point is found for point sources.
- Remove deprecated package
fenicsadapter
. Don't useimport fenicsadapter
. Please useimport fenicsprecice
. See PR #121
- The paper FEniCS-preCICE: Coupling FEniCS to other Simulation Software (in preparation) describes features, usage and API of the adapter.
- The software is called FEniCS-preCICE adapter, the corresponding python package
fenicsprecice
. Our software uses the naming proposed in PR #85. fenicsprecice
is published via PyPI. See PR #94.- FEniCS PointSource and Expressions are used to create boundary conditions for coupling.
- The adapter uses a
SegregatedRBFinterpolationExpression
for interpolation, if an Expression is used. See PR #83. - The adapter supports one-way coupling and two-way coupling.
- The adapter supports explicit and implicit coupling schemes.
- The adapter supports checkpointing and subcycling.
- The adapter supports up to one read and one write data set.
- The current state of the adapter API was mainly designed in PR #59.
- Supports parallel solvers for Expressions, but not for PointSources as coupling boundary conditions. See PR #71.