bheEASyMesh
Tool for creating simple VTK unstructured grid meshes (3D prism elements) with BHEs (line elements) for use in OpenGeoSys 6 HeatTransportBHE simulations. Besides, the extraction of surface meshes and the application of temperature ICs is possible. The meshing is based on the Bhe_Meshing tool by Philip Hein (Shao et al., 2016) and uses GMSH (Geuzaine et al., 2009).
Meshes contain:
- 3D prism mesh with horizontal element layers
- A selected number of BHEs, which are represented as line elements
- Diersch's ideal node distance around BHE-elements (Diersch et al., 2011)
- A chosen number of optional horizontal refinement boxes in the mesh
- Extraction of surfacemeshes to define BC's or IC's in OpenGeoSys
- An optional temperature IC as depth dependent profile or fixed temperature which can be applied to the mesh and if needed to surfacemeshes
There are two modes in the Software:
=>"simple" Meshes:
- Simple meshes with two different material groups to be used for geological homogeneous models with an area with groundwater flow
- the software automatically adjusts the vertical layers over the user-defined default element height
- refined layers in the transition zones (BHE top/bottom, aquifer top/bottom) by user-defined number of refined layers and a separate element height for refined areas
=>"layered" Meshes:
- manual definition of any number of layers
- number of elements, height of the elements and material ID can be freely selected for each layer
For more instructions, see Meshing_example.ipynb, where there are tutorials for both meshing modes.
====================================
Diersch et al. (2011): Finite element modeling of borehole heat exchanger systems Part 2.Numerical simulation. In: Computers & Geosciences 37, pages 1136-1147.
Geuzaine C et al. (2009) Gmsh: A 3-D finite element mesh generator with built-in pre- and post-processing facilities. International Journal for Numerical Methods in Engineering 79, pages 1309-1331.
Shao et al. (2016): Geoenergy Modeling II Shallow Geothermal Systems. Springer.
Metadata
Release files for bheEASyMesh 0.2.3
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 | |
|---|---|---|---|---|
| bheEASyMesh-0.2.3.tar.gz | 11.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bheEASyMesh-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.7 kB
Release files / bheEASyMesh-0.2.3.tar.gz
| Download URL | bheEASyMesh-0.2.3.tar.gz |
|---|---|
| Size | 11.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
714e60038ed547cb00a10ec9530f6b0500c2f15ea518434e69b2589f95c2e03e
|
|
BLAKE2b-256 checksum How to use checksums |
35d1e3af3fcdc02b923da4aebc9b1cb7864c23a127339679602a1d2d22725985
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / bheEASyMesh-0.2.3-py3-none-any.whl
| Download URL | bheEASyMesh-0.2.3-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
af74caacb13b2c28aeec563f863e6ddd569c64f9550dc479a3279ba59278525c
|
|
BLAKE2b-256 checksum How to use checksums |
0757796eba7c241f2443bf6ad5f8a1a3372a00a0ead91fdceb723231081e37d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for bheEASyMesh 0.2.3
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.