Skip to content

Publishing simulation tools

Contributing biosimulation tools to BioSimulators

We welcome contributions of additional simulation tools! We encourage developers to submit tools that support BioSimulators' standard containerized command-line interface. Supporting these conventions makes it easier for other investigators to use simulators. However, BioSimulators also accepts simulation tools that are not available via standardized Docker images.

Please follow these steps to contribute a tool to BioSimulators:

  1. Annotate the capabilities of your simulation tool (e.g., supported modeling frameworks, simulation algorithms, model formats) using the BioSimulators format for the capabilities of simulation tools.

  2. Optionally, build a standardized command-line interface for your simulator. This interface should support the following conventions:

    The command-line interface should support the arguments outlined in BioSimulators' specifications for command-line interfaces for simulation tools.

    • COMBINE/OMEX archives should be used as the format for inputs to your simulator.

    • A standard modeling language such as BNGL, CellML, NeuroML, or SBML should be used to describe models.

    • SED-ML and the BioSimulators SED-ML conventions should be used to describe simulation experiments.

    • Reports of simulation results should be saved according to the BioSimulators format for reports of simulation results.

    • The process of executing COMBINE/OMEX archives should be logged using BioSimulators' format for logs of the execution of COMBINE/OMEX archives.

    BioSimulators utils provides tools for implementing these conventions. A detailed template for using BioSimulators-utils to build a command-line interface for a simulator is available here.

  3. Optionally, containerize the command-line interface for your simulator. Such an image will make it easier for others to use your tool. Containerized simulation tools should follow BioSimulators' conventions for Docker images for simulation tools.

  4. Optionally, publish your image to a public repository such as Docker Hub, GitHub Container Registry, or Quay by executing docker push { image-url }. Docker Hub, GitHub Container Registry, and Quay each provide free accounts for public images.

  5. Submit an issue to the BioSimulators GitHub repository that briefly describes the URL to the specifications of your tool. This will initiate an automated workflow that will validate your simulation tool and either commit your tool to the BioSimulators registry or report problems with your simulation tool that must be addressed. The first version of each simulation tool submitted to the BioSimulators registry will also be manually reviewed by the BioSimulators Team prior to incorporation into the BioSimulators registry.

  6. Optionally, set up your continuous integration workflow to automatically push each release to BioSimulators. Within your continuous integration workflow (e.g., CircleCI, GitHub actions, Jenkins, Travis), use the GitHub REST API to automatically create issues that submit each version of your simulator to BioSimulators.

    This requires a GitHub account and a personal access token with the public_repo scope. Instructions for creating an access token are available in the GitHub documentation.

    • Endpoint:
    • Method: POST
    • Authentication: { github-username }:{ github-person-access-token }
    • Headers:
      • Accept: application/vnd.github.v3+json
    • Body (JSON-encoded)

      • title: Submit { simulator-name } { simulator-version }
      • body:
      name: { simulator-name }
      version: "{ simulator-version }"
      specificationsUrl: { specifications-url }
      version: "{ simulator-version }"
          url: { docker-image-repo-url }:{ simulator-version }
      validateImage: true

    To skip the validation of your Docker image, or to submit a simulation tool for which there is no Docker image that provides a BioSimulators-compliant command-line entrypoint, set validateImage to false.

    Below is an example cURL command to programmatically submit a simulation tool:

    curl \
    -X POST \
    -u jonrkarr:********* \
    -H "Accept: application/vnd.github.v3+json" \ \
    -d '{"labels": ["Validate/submit simulator"], "title": "Submit tellurium 2.1.6", "body": "---\nname: tellurium\nversion: 2.1.6\nspecificationsUrl:\nvalidateImage: true\ncommitSimulator: true\n\n---"}'

    The above is implemented by the Python method biosimulators_utils.simulator_registry.submit.submit_simulator_to_biosimulators_registry. See the documentation for more information.

  7. Optionally, also publish the source code for your simulation tool to a repository such as BitBucket, GitHub, or GitLab.

  8. Optionally, also publish your simulation tool to a software repository such as CRAN (R), NPM (JavaScript), or PyPi (Python).
  9. Optionally, also register your tool with Visit to submit your tool to their registry of research tools.
  10. Optionally, also submit your Dockerfile to BioContainers. BioContainers accepts contributions via pull requests. See the BioContainers image registry for more information.

A sample continuous integration workflow for GitHub Actions is available in the template simulator repository. Instructions for setting up this workflow are in the README.

Each time a commit is pushed to the repository, the workflow executes the following tasks:

  1. Clones the repository.

  2. Installs the simulator and its dependencies.

  3. Lints the code for the simulator.

  4. Builds the Docker image for the simulator and tags the image<owner>/<repo>/<simulator_id>:<simulator_version and<owner>/<repo>/<simulator_id>:latest.

  5. Runs the unit tests for the simulator and saves the coverage data for the tests.

  6. Uploads the coverage results to Codecov.

  7. Compiles the documentation for the simulator.

Each time the repository is tagged (git tag ...; git push --tags), the workflow also runs the above tasks. If the above tasks succeed, the workflow executes the following additional tasks:

  1. Creates a GitHub release for the tag.
  2. Pushes the compiled documentation to the repository (e.g., so it can be served by GitHub pages).
  3. Builds the simulator and submits it to a software repository such as PyPI.
  4. Pushes the Docker image to the GitHub Container Registry with the above tags.
  5. Pushes the simulator to the BioSimulators Registry, via the GitHub API, to create an issue for adding a new version of the simulator to the BioSimulators database. This issue will then automatically use the BioSimulators test suite to validate the simulator and add a new version of the simulator to the database once the simulator passes the test suite.

Last update: 2022-01-20
Back to top