Abstraction layer for running numerical hydrodynamics software
jelly is supposed to abstract away the technical complexities of running numerical moving-mesh hydrodynamics simulations using Arepo. It generates input files and wraps the invocation of simulation runs.
Code status
Examples
There are a couple of examples in the examples/ directory in the form of simple Python scripts. Note that you need to have jelly in your Python path to run them.
Tests
We use nosetests for unit testing.
To run the tests install the nose package and call nosetests from the base directory.
You can also install and use tox to run the tests for different python versions.
Metadata
Release files for jelly 0.1.0
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 |
|---|---|---|---|---|
| jelly-0.1.0.tar.gz | 11.9 kB | Without provenance | Details for jelly-0.1.0.tar.gz |
Release files / jelly-0.1.0.tar.gz
| Download URL | jelly-0.1.0.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7dfc7b0bbdd6c168d5865c0f5e452a76cefe8a5027f09c75dbc081244b14b19f
|
|
BLAKE2b-256 checksum How to use checksums |
1bf96957adbc1f71c0966d065d2cf6d8cd80a7f94a97809c418828f8aaa44e3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for jelly 0.1.0
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.