Skip to main content
  • Home
  • Development
  • Documentation
  • Donate
  • Operational login
  • Browse the archive

swh logo
SoftwareHeritage
Software
Heritage
Archive
Features
  • Search

  • Downloads

  • Save code now

  • Add forge now

  • Help

Raw File Download

To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
Select below a type of object currently browsed in order to display its associated SWHID and permalink.

  • content
content badge Iframe embedding
swh:1:cnt:ac20f7779b286c37b352a38a53c7105ab473a857

This interface enables to generate software citations, provided that the root directory of browsed objects contains a citation.cff or codemeta.json file.
Select below a type of object currently browsed in order to generate citations for them.

  • content
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Supporting source code and post-processing scripts for the article:

Zhou, X., Wang, Z. J., Camps, J., Tomek, J., Santiago, A., Quintanas, A., ... & Rodriguez, B. (2024). Clinical phenotypes in acute and chronic infarction explained through human ventricular electromechanical modelling and simulations. eLife, 13. https://doi.org/10.7554/eLife.93002.1

Cellular model is based on https://github.com/jtmff/torord with modifications for modelling post-myocardial infarction border zone and remote zone remodelling. 

Alya input files for running the simulations can be found at https://doi.org/10.5281/zenodo.13993395 and the Alya binary executables can be made available upon request. Post-processing scripts in this repository are designed to produce the figures shown in the published article. 

back to top

Software Heritage — Copyright (C) 2015–2025, The Software Heritage developers. License: GNU AGPLv3+.
The source code of Software Heritage itself is available on our development forge.
The source code files archived by Software Heritage are available under their own copyright and licenses.
Terms of use: Archive access, API— Content policy— Contact— JavaScript license information— Web API