1 file was added to this release more than 14 days after its initial publication. Inspect the release files before installing.
blitzdg
blitzdg is an open-source library offering discontinuous Galerkin (dg) solvers for common partial differential equations systems using blitz++ for array and tensor manipulations in a C++ environment or NumPy as a Python 3 library.
Shallow Water Wave Example blitzdg output
Building From Source
Build and development support has broadened from linux only to Mac OSX and Windows systems. Tested with GNU make (written to be cross-platform) and g++ on linux/MinGW64, clang++ on Mac OSX High Sierra, and MSVC on Windows. Our build system depends on the cross-platform cmake tooling for Makefile generation.
git clone https://github.com/dsteinmo/blitzdg.gitcd blitzdg && ./pull-deps.shcmake . && make advec1d && ./bin/advec1d(This binary is a 1D advection equation solver.).- Run unit tests with
make test.
Dependencies
cmakeblitz++SuiteSparse (umfpack, cxsparse)LAPACKmetisigloofor BDD-style testing.vtkfor visualization in Paraview.boost-python3for python bindings.boost-numpy3for numpy C++ interoperability.
Dependency installation is outlined in pull-deps.sh (tested on Ubuntu and Mac OSX).
Windows
Our windows distribution was recently switched from MinGW to MSVC in order to achieve better support for graphics APIs, so support is lacking at the moment. Instructions will be made available here soon.
Contributing
We accept pull requests from public forks, and we use pull requests as the primary delivery mechanism of any new code within the base repository.
If you add code, please write tests using the igloo testing framework that is included as a project dependency. Your code additions will be subject to peer review and will be run through our Travis-CI continuous integration process.
Interested developers should consult the Guidelines for Contributing before getting started.
Maintainer
Lead Developers
Documentation
We actively maintain an interactive set of docs using Doxygen for end-user consumption.
The documentation is available on github pages at https://wqcg.github.io/blitzdg and is kept synchronized with the master branch via automation.
License
This project is licensed under the GNU Public License Version 3.
Our license choice is driven by the desire to keep this project and any of its derivative works open-source for public consumption by developers, mathematicians, scientists, engineers, and anyone else who might be interested in this project.
Contact
Any questions regarding the project may be addressed via email to the project maintainer.
Metadata
Release files for pyblitzdg 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
File added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release files before installing.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyblitzdg-1.0.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.17+ x86-64 | Details for pyblitzdg-1.0.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| pyblitzdg-1.0.3-cp39-cp39-manylinux_2_12_x86_64.manylinux2010_x86_64.whl | CPython 3.9 | CPython 3.9 | Linux glibc 2.12+ x86-64 | Details for pyblitzdg-1.0.3-cp39-cp39-manylinux_2_12_x86_64.manylinux2010_x86_64.whl |
Total release size: 66.5 MB
Release files / pyblitzdg-1.0.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | pyblitzdg-1.0.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 30.2 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
db296572689dbc1a237cdcc2031a28c2d5c2eb057a95e8dde5c3e1e02c556992
|
|
BLAKE2b-256 checksum How to use checksums |
6a37e228ad5cb099f23ee2e6f87ba8e5d14b47a87830d1c5ee0826aecf20d5e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.0
|
Release files / pyblitzdg-1.0.3-cp39-cp39-manylinux_2_12_x86_64.manylinux2010_x86_64.whl
| Download URL | pyblitzdg-1.0.3-cp39-cp39-manylinux_2_12_x86_64.manylinux2010_x86_64.whl |
|---|---|
| Size | 36.3 MB |
| Tags | CPython 3.9 Linux glibc 2.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
4860c90e063bb6fd1b61793b83a3e33c3467f87de0a9d275ac7f28b18510c36d
|
|
BLAKE2b-256 checksum How to use checksums |
d16b9305b39fb5c51561b78c8248f9a4c92dd0027aa97949e37e5f6d45450619
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.2
|
Security for pyblitzdg 1.0.3
Upload timing
Release file added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
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.