SOLVCON is a collection of conservation-law solvers that use the space-time Conservation Element and Solution Element (CESE) method.
Install
Clone the hg repository from https://bitbucket.org/solvcon/solvcon:
$ hg clone https://bitbucket.org/solvcon/solvcon
SOLVCON needs the following packages: gcc 4.3+ (clang on OSX works as well), SCons 2+, Python 2.7, Cython 0.16+, Numpy 1.5+, LAPACK, NetCDF 4+, SCOTCH 6.0+, Nose 1.0+, Paramiko 1.14+, boto 2.29.1+, gmsh 2.5+, and VTK 5.6+.
In the contrib/ directory, you can find the scripts for installing these dependencies:
The binary part of SOLVCON should be built with SCons:
$ scons scmods
Then add the installation path to the environment variables $PATH and $PYTHONPATH.
Additional build and tests:
Building document requires Sphinx 1.1.2+, Sphinxcontrib issue tracker 0.11, and graphviz 2.28+. Once the binary of SOLVCON is built, the following commands can build the document:
$ cd doc $ make html
The built document will be available at doc/build/html/.
Unit tests should be run with Nose:
$ nosetests
Another set of tests are collected in ftests/ directory, and can be run with:
$ nosetests ftests/*
Some tests in ftests/ involve remote procedure call (RPC) that uses ssh. You need to set up the public key authentication to properly run them.
1 maintainer
Metadata
1 maintainer
Release files for SOLVCON 0.1.4
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 | |
|---|---|---|---|---|
| SOLVCON-0.1.4.tar.gz | 1.5 MB | Without provenance | Details |
Release files / SOLVCON-0.1.4.tar.gz
| Download URL | SOLVCON-0.1.4.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e12b4fae7b8b7a3b4b8a60f082e89b829eedaf8103f324a03ed9823078217e99
|
|
BLAKE2b-256 checksum How to use checksums |
eef1f590aee90567dd14b7d3bc5e71590d4d558f33dd28ab575cd3e7ddaf27b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for SOLVCON 0.1.4
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.
