PhysioBlocks
PhysioBlocks allows the simulation of dynamical models of physiological systems.
User Levels
They are several use cases for PhysioBlocks depending on the user profile:
- Level 1: Configure and run physiological systems simulation (for pre-existing systems)
- Level 2: Create new systems with existing blocks without writing code
- Level 3: Write and add new blocks to the library.
Principle
- A Net (system) is built from Nodes and Blocks connected by those nodes.
- At each node in the net, connected blocks share Degrees of Freedom (ex: pressure) and send Fluxes that verify Kirchhoff Law.
- ModelComponents concatenate blocks equations to the global system (if necessary, for modularity purposes within the block)
Interactions
Level 1: Configure and run a simulation: JSON
- Update the model parameters
Level 2: Create Nets: JSON
- Declare the nodes, the blocks, and the block - nodes connections
Level 3: Write and add models to the library: Python
- Declare the quantities to use in the model
- Write the fluxes and equations
Documentation
Here are the links to the sections of the full documentation:
Quick start
Complete instructions are available in the documentation. This instructions will enable you to launch a reference simulation.
Installation
This project requires a recent version of python installed. Then:
pip install physioblocks
Configuration
To configure PhysioBlocks Launcher:
# Create an empty folder where you want to store simulations results.
mkdir $LAUNCHER_FOLDER_PATH$
# Configure the folder
python -m physioblocks.launcher.configure -d $LAUNCHER_FOLDER_PATH$ -v
Launch a simulation
With a Launcher folder configured:
# Move to your configured launcher folder
cd $LAUNCHER_FOLDER_PATH$
# Launch a reference simulation
python -m physioblocks.launcher references/spherical_heart_sim.jsonc -v -s QuickStart
Results will be available in the $LAUNCHER_FOLDER_PATH/simulations/QuickStart series folder:
- the csv files contain the simulation results.
- the html files allow you to visualize the results.
- the log and json files are here for debug purposes.
Metadata
Release files for physioblocks 2.0.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 | |
|---|---|---|---|---|
| physioblocks-2.0.0.tar.gz | 29.4 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| physioblocks-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.0 MB
Release files / physioblocks-2.0.0.tar.gz
| Download URL | physioblocks-2.0.0.tar.gz |
|---|---|
| Size | 29.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
83cb9518af848fcf1329f57715f6964e6d7740449b42a0690967fcd63cc856b3
|
|
BLAKE2b-256 checksum How to use checksums |
b9872ad7ff763be6a5c93e79c37f20d2331a3a747121f7a94c2bffde1b799ea6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.20
|
Release files / physioblocks-2.0.0-py3-none-any.whl
| Download URL | physioblocks-2.0.0-py3-none-any.whl |
|---|---|
| Size | 603.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c9e20b13a302516c38a3ed31c70df25a0aafe5fe431059d9d8b359979a60f5f6
|
|
BLAKE2b-256 checksum How to use checksums |
969881d3fab932af7ddb724255effa141ee7c13add30c8c4c4206e071e605844
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.20
|
Security for physioblocks 2.0.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.