This release is a pre-release and may not be stable for production use.
DUNE-FEM
DUNE-VEM is a Distributed and Unified Numerics Environment module which provides implementation of a range of virtual element spaces. It is based on the interfaces defined in DUNE-FEM. In addition to the C++ implementation and extensive Python interface is provided.
If you need help, please ask on our mailinglist. Bugs can also be submitted to the DUNE-VEM bugtracker instead.
Tutorial
The general DUNE-FEM tutorial based on the Python bindings includes a number of examples showcasing the DUNE-VEM module.
Installation
Using pip
DUNE-VEM can be installed using the Package Index of Python (pip).
pip install dune-vem
See https://dune-project.org/doc/installation-pip/ for a more detailed description.
From source
For a full explanation of the DUNE installation process please read the installation notes.
When using the main branch observe the build status to make sure you get a working version.
Dependencies
DUNE-VEM requires a recent C++ compiler (e.g. g++ or clang), cmake, pkg-config (see DUNE installation for details) and depends on the following DUNE modules:
The following DUNE modules are suggested:
The following software is optional:
License
The DUNE-VEM library, headers and test programs are free open-source software, licensed under version 2 or later of the GNU General Public License.
See the file LICENSE for full copying permissions.
References
A detailed description of DUNE-FEM can be found in
-
A. Dedner, A. Hodson. A framework for implementing general virtual * element space. https://arxiv.org/abs/2208.08978
-
A. Dedner, R. Klöfkorn, M. Nolte, and M. Ohlberger. A Generic Interface for Parallel and Adaptive Scientific Computing: Abstraction Principles and the DUNE-FEM Module. Computing, 90(3-4):165--196, 2010. http://dx.doi.org/10.1007/s00607-010-0110-3
-
A. Dedner, R. Klöfkorn, and M. Nolte. Python Bindings for the DUNE-FEM module. Zenodoo, 2020 http://dx.doi.org/10.5281/zenodo.3706994
git-c679a4c339d36322fd82bc88d5b5e8a0b54542da
Metadata
Release files for dune-vem 2.10.dev20230325
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dune-vem-2.10.dev20230325.tar.gz | 1.5 MB | Without provenance | Details for dune-vem-2.10.dev20230325.tar.gz |
Release files / dune-vem-2.10.dev20230325.tar.gz
| Download URL | dune-vem-2.10.dev20230325.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
15d72ba32b04150ab880c9581f40fbbe45ec77c908a98ec804ab265c43352e04
|
|
BLAKE2b-256 checksum How to use checksums |
9ee0a8f2f6ef69b495930c656c044343621e51437bdc1847a26ffbe018d04d13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.2
|
Security for dune-vem 2.10.dev20230325
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.