pulse

pulse: A python package based on FEniCS for solving problems in cardiac mechanics - Published in JOSS (2019)

https://github.com/finsberg/pulse

Science Score: 100.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
    Found CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
    Found 5 DOI reference(s) in README and JOSS metadata
  • Academic publication links
    Links to: joss.theoj.org
  • Committers with academic emails
    1 of 8 committers (12.5%) from academic institutions
  • Institutional organization owner
  • JOSS paper metadata
    Published in Journal of Open Source Software

Keywords from Contributors

hydrology energy-systems

Scientific Fields

Mathematics Computer Science - 63% confidence
Last synced: 6 months ago · JSON representation ·

Repository

A software for solving problems in cardiac mechanics

Basic Info
Statistics
  • Stars: 16
  • Watchers: 2
  • Forks: 13
  • Open Issues: 5
  • Releases: 8
Created over 7 years ago · Last pushed 6 months ago
Metadata Files
Readme Contributing License Citation

README.md

Anaconda-Server Badge Anaconda-Server Badge CI Platform status codecov pre-commit.ci status

pulse

A software for solving problems in cardiac mechanics.

Overview

pulse is a software based on FEniCS that aims to solve problems in cardiac mechanics (but is easily extended to solve more general problems in continuum mechanics). pulse is a results of the author's PhD thesis, where most of the relevant background for the code can be found.

While FEniCS offers a general framework for solving PDEs, pulse specifically targets problems in continuum mechanics. Therefore, most of the code for applying compatible boundary conditions, formulating the governing equations, choosing appropriate spaces for the solutions and applying iterative strategies etc. are already implemented, so that the user can focus on the actual problem he/she wants to solve rather than implementing all the necessary code for formulating and solving the underlying equations.

Installation instructions

Install with pip

pulse can be installed directly from PyPI python3 -m pip install fenics-pulse or you can install the most recent development version python3 -m pip install git+https://github.com/finsberg/pulse.git

Install with conda

You can also install the package using conda conda install -c conda-forge pulse

Docker

It is also possible to use Docker. There is a prebuilt docker image using the development version of FEniCS, python3.10 and pulse. You can get it by typing docker pull ghcr.io/finsberg/pulse:latest

Requirements

  • FEniCS version 2019.1.0 or newer (older versions might work but is not tested against anymore)

Note that if you install FEniCS using anaconda then you will not get support for parallel HDF5 see e.g this issue.

Getting started

Check out the demos in the demo folder. These demos are currently in jupyter notebook format. If you want to run them as python files you can convert the notebooks to .py files using e.g jupytext

If you have a question about how to use the software you can ask a question or start a new discussion in the discussion section

Automated test

Test are provided in the folder tests. You can run the test with pytest python3 -m pytest tests -vv

Documentation

Documentation can be found at finsberg.github.io/pulse You can create documentation yourselves by typing make html in the root directory.

Citing

If you use pulse in your own research, please cite the JOSS paper

@article{pulse, doi = {10.21105/joss.01539}, url = {https://doi.org/10.21105/joss.01539}, year = {2019}, month = {sept}, publisher = {The Open Journal}, volume = {4}, number = {41}, pages = {1539}, author = {Henrik Finsberg}, title = {pulse: A python package based on FEniCS for solving problems in cardiac mechanics}, journal = {The Journal of Open Source Software} }

Known issues

  • If you encounter errors with h5py try to uninstall it (pip uninstall h5py) and then re-install it without installing any binary packages, i.e python3 -m pip install h5py --no-binary=h5py

Contributing

See CONTRIBUTING.md

Owner

  • Name: Henrik Finsberg
  • Login: finsberg
  • Kind: user
  • Location: Oslo, Norway
  • Company: Simula Research Laboratoy

Senior Research Engineer working with Scientific Computing and Computational Physiology

JOSS Publication

pulse: A python package based on FEniCS for solving problems in cardiac mechanics
Published
September 24, 2019
Volume 4, Issue 41, Page 1539
Authors
Henrik Nicolay Topnes Finsberg ORCID
Simula Research Laboratory, Oslo, Norway
Editor
Tania Allard ORCID
Tags
FEniCS Cardiac Mechanics Finite Element Method Continuum Mechanics

Citation (CITATION.cff)

cff-version: 1.2.0
message: "If you use this software, please cite it as below."
authors:
- family-names: "Finsberg"
  given-names: "Henrik"
  orcid: "https://orcid.org/0000-0003-3766-2393"
title: "pulse"
version: 2022.1.3
doi: 10.21105/joss.01539
license: LGPL-3.0
date-released: 2019-09-24
url: "https://github.com/finsberg/pulse"

GitHub Events

Total
  • Watch event: 2
  • Push event: 37
  • Pull request event: 3
  • Fork event: 1
  • Create event: 2
Last Year
  • Watch event: 2
  • Push event: 37
  • Pull request event: 3
  • Fork event: 1
  • Create event: 2

Committers

Last synced: 7 months ago

All Time
  • Total Commits: 526
  • Total Committers: 8
  • Avg Commits per committer: 65.75
  • Development Distribution Score (DDS): 0.198
Past Year
  • Commits: 7
  • Committers: 3
  • Avg Commits per committer: 2.333
  • Development Distribution Score (DDS): 0.429
Top Committers
Name Email Commits
Henrik Finsberg h****f@s****o 422
pre-commit-ci[bot] 6****] 82
Alexandra Diem a****m@g****m 11
zoraiz r****2@y****m 3
Joakim Sundnes s****s@s****o 3
mjsadeghinia m****a@o****m 2
Daniel S. Katz d****z@i****g 2
jvbrink j****s@s****o 1
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 18
  • Total pull requests: 105
  • Average time to close issues: 3 months
  • Average time to close pull requests: 7 days
  • Total issue authors: 6
  • Total pull request authors: 6
  • Average comments per issue: 4.06
  • Average comments per pull request: 0.06
  • Merged pull requests: 102
  • Bot issues: 0
  • Bot pull requests: 78
Past Year
  • Issues: 0
  • Pull requests: 5
  • Average time to close issues: N/A
  • Average time to close pull requests: 1 day
  • Issue authors: 0
  • Pull request authors: 3
  • Average comments per issue: 0
  • Average comments per pull request: 0.0
  • Merged pull requests: 3
  • Bot issues: 0
  • Bot pull requests: 1
Top Authors
Issue Authors
  • finsberg (5)
  • jingbinzhao415 (4)
  • melund (4)
  • wilburmao (3)
  • Tao-Bath (1)
  • ramayzoraiz (1)
Pull Request Authors
  • pre-commit-ci[bot] (80)
  • finsberg (19)
  • mjsadeghinia (4)
  • danielskatz (2)
  • mansoryashka (1)
  • jvbrink (1)
  • ramayzoraiz (1)
Top Labels
Issue Labels
enhancement (2)
Pull Request Labels

Packages

  • Total packages: 2
  • Total downloads:
    • pypi 215 last-month
  • Total docker downloads: 176
  • Total dependent packages: 2
    (may contain duplicates)
  • Total dependent repositories: 2
    (may contain duplicates)
  • Total versions: 39
  • Total maintainers: 1
pypi.org: fenics-pulse

A python library based on FEniCS that aims to solve problems in continuum mechanics, in particular cardiac mechanics

  • Homepage: https://finsberg.github.io/pulse/
  • Documentation: https://finsberg.github.io/pulse/
  • License: GNU LESSER GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the additional permissions listed below. 0. Additional Definitions. As used herein, "this License" refers to version 3 of the GNU Lesser General Public License, and the "GNU GPL" refers to version 3 of the GNU General Public License. "The Library" refers to a covered work governed by this License, other than an Application or a Combined Work as defined below. An "Application" is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class defined by the Library is deemed a mode of using an interface provided by the Library. A "Combined Work" is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined Work was made is also called the "Linked Version". The "Minimal Corresponding Source" for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version. The "Corresponding Application Code" for a Combined Work means the object code and/or source code for the Application, including any data and utility programs needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work. 1. Exception to Section 3 of the GNU GPL. You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL. 2. Conveying Modified Versions. If you modify a copy of the Library, and, in your modifications, a facility refers to a function or data to be supplied by an Application that uses the facility (other than as an argument passed when the facility is invoked), then you may convey a copy of the modified version: a) under this License, provided that you make a good faith effort to ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy. 3. Object Code Incorporating Material from Library Header Files. The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and templates (ten or fewer lines in length), you do both of the following: a) Give prominent notice with each copy of the object code that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the object code with a copy of the GNU GPL and this license document. 4. Combined Works. You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following: a) Give prominent notice with each copy of the Combined Work that the Library is used in it and that the Library and its use are covered by this License. b) Accompany the Combined Work with a copy of the GNU GPL and this license document. c) For a Combined Work that displays copyright notices during execution, include the copyright notice for the Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and this license document. d) Do one of the following: 0) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the Application with a modified version of the Linked Version to produce a modified Combined Work, in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source. 1) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (a) uses at run time a copy of the Library already present on the user's computer system, and (b) will operate properly with a modified version of the Library that is interface-compatible with the Linked Version. e) Provide Installation Information, but only if you would otherwise be required to provide such information under section 6 of the GNU GPL, and only to the extent that such information is necessary to install and execute a modified version of the Combined Work produced by recombining or relinking the Application with a modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Corresponding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Corresponding Source.) 5. Combined Libraries. You may place library facilities that are a work based on the Library side by side in a single library together with other library facilities that are not Applications and are not covered by this License, and convey such a combined library under terms of your choice, if you do both of the following: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities, conveyed under the terms of this License. b) Give prominent notice with the combined library that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 6. Revised Versions of the GNU Lesser General Public License. The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that published version or of any later version published by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any version of the GNU Lesser General Public License ever published by the Free Software Foundation. If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public statement of acceptance of any version is permanent authorization for you to choose that version for the Library.
  • Latest release: 2025.0.0
    published 9 months ago
  • Versions: 31
  • Dependent Packages: 2
  • Dependent Repositories: 1
  • Downloads: 215 Last month
  • Docker Downloads: 176
Rankings
Docker downloads count: 2.4%
Dependent packages count: 3.2%
Forks count: 11.4%
Average: 12.0%
Stargazers count: 16.1%
Downloads: 17.2%
Dependent repos count: 21.5%
Maintainers (1)
Last synced: 6 months ago
conda-forge.org: pulse

pulse is a python library based on FEniCS that aims to solve problems in continuum mechanics, in particular cardiac mechanics.

  • Versions: 8
  • Dependent Packages: 0
  • Dependent Repositories: 1
Rankings
Dependent repos count: 24.4%
Average: 44.1%
Forks count: 46.2%
Dependent packages count: 51.6%
Stargazers count: 54.3%
Last synced: 6 months ago

Dependencies

.github/workflows/github-pages.yml actions
  • actions/cache v2 composite
  • actions/checkout v2 composite
  • peaceiris/actions-gh-pages v3 composite
.github/workflows/main.yml actions
  • actions/cache v2 composite
  • actions/checkout v2 composite
  • nick-invision/retry v2 composite
environment.yml conda
  • gmsh
  • jupyter
  • jupyterlab
  • ldrb
  • pulse
.github/workflows/docker-image.yml actions
  • actions/checkout v3 composite
  • docker/build-push-action v3 composite
  • docker/login-action v2 composite
  • docker/metadata-action 98669ae865ea3cffbcbaa878cf57c20bbf1c6c38 composite
  • docker/setup-buildx-action v2 composite
  • docker/setup-qemu-action v2 composite
.github/workflows/pypi.yml actions
  • actions/checkout v3 composite
  • actions/setup-python v4 composite
  • pypa/gh-action-pypi-publish release/v1 composite
Dockerfile docker
  • ghcr.io/scientificcomputing/fenics-gmsh 2023-08-16 build
pyproject.toml pypi
  • daiquiri *
  • h5py *
  • numpy *
  • scipy *