CellSium Readme
CellSium - Cell Simulator for microfluidic microcolonies
CellSium example simulation result
Front Matter
CellSium is a cell simulator developed for the primary application of generating realistically looking images of bacterial microcolonies, which may serve as ground truth for machine learning training processes.
Publication
If you use CellSium within scientific research, we ask you to cite our publication:
Sachs CC, Ruzaeva K, Seiffarth J, Wiechert W, Berkels B, Nöh K (2022) CellSium: versatile cell simulator for microcolony ground truth generation Bioinformatics Advances, Volume 2, Issue 1, 2022, vbac053, doi: 10.1093/bioadv/vbac053
It is available on the Bioinformatics Advances homepage at DOI: 10.1093/bioadv/vbac053 <https://doi.org/10.1093/bioadv/vbac053>.
Documentation
The documentation to CellSium can be built using Sphinx, or be found readily built at Read the Docs.
License
CellSium is available under the BSD license (see LICENSE.rst / license section).
Installation
Installation using pip
CellSium can be installed via pip, ideally create and activate an environment beforehand to install CellSium in.
> python -m pip install cellsium
Installation using conda
CellSium is available in the modsim Anaconda channel as well, using packages from the conda-forge channel. It can be installed with the following commands:
> conda install -c modsim -c conda-forge -y cellsium
Usage
Once installed, run CellSium via python -m cellsium, specifying the desired entrypoint and options, such as outputs.
CellSium is built modular, various output modules can be activated simultaneously. To get an overview of the available options,
use the --help switch. Furthermore, the main mode of setting tunable parameters are so called tunables, which can
be set from the command line using the -t switches. A list of tunables can be shown using the --tunables-show argument.
> python -m cellsium --help
usage: __main__.py [-v] [-q] [-c CELL] [-p] [-w] [-o OUTPUT] [-h] [-m MODULE]
[--Output {COCOOutput,CsvOutput,FluorescenceRenderer,GenericMaskOutput,JsonPickleSerializer,MeshOutput,NoisyUnevenIlluminationPhaseContrast,PhaseContrastRenderer,PlainRenderer,PlotRenderer,QuickAndDirtyTableDumper,SvgRenderer,TiffOutput,TrackMateXML,UnevenIlluminationPhaseContrast,YOLOOutput}]
[--PlacementSimulation {Box2D,Chipmunk,NoPlacement}] [-t TUNABLE] [--tunables-show] [--tunables-load TUNABLES_LOAD] [--tunables-save TUNABLES_SAVE]
optional arguments:
-h, --help show this help message and exit
-o OUTPUT, --output-file OUTPUT
-w, --overwrite
-p, --prefix
-c CELL, --cell CELL
-q, --quiet
-v, --verbose
-m MODULE, --module MODULE
--Output {COCOOutput,CsvOutput,FluorescenceRenderer,GenericMaskOutput,JsonPickleSerializer,MeshOutput,NoisyUnevenIlluminationPhaseContrast,PhaseContrastRenderer,PlainRenderer,PlotRenderer,QuickAndDirtyTableDumper,SvgRenderer,TiffOutput,TrackMateXML,UnevenIlluminationPhaseContrast,YOLOOutput}
--PlacementSimulation {Box2D,Chipmunk,NoPlacement}
-t TUNABLE, --tunable TUNABLE
--tunables-show
--tunables-load TUNABLES_LOAD
--tunables-save TUNABLES_SAVE
You can for example run a default simulation by just starting CellSium, the results will be shown interactively using matplotlib:
> python -m cellsium
For more in-depth usage examples, please see the examples section of the documentation.
Docker
An alternative to installing CellSium locally is running it via Docker. To run CellSium without interactive (GUI) elements, the following Docker command can be used, with parameters to CellSium being appended.
> docker run --tty --interactive --rm --volume `pwd`:/data --user `id -u` ghcr.io/modsim/cellsium
To use interactive (GUI) elements such as the PlotRenderer, an X server must be reachable; under Linux the following command can be used:
> docker run --tty --interactive --rm --volume `pwd`:/data --user `id -u` --env DISPLAY=$DISPLAY --volume /tmp/.X11-unix:/tmp/.X11-unix ghcr.io/modsim/cellsium
Metadata
Release files for cellsium 1.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 | Actions |
|---|---|---|---|---|
| cellsium-1.0.0.tar.gz | 48.7 kB | Without provenance | Details for cellsium-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cellsium-1.0.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for cellsium-1.0.0-py2.py3-none-any.whl |
Total release size: 110.3 kB
Release files / cellsium-1.0.0.tar.gz
| Download URL | cellsium-1.0.0.tar.gz |
|---|---|
| Size | 48.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
293136969d372306c9c62c64d86e4f613bd4bf0730e324794e41f031ce4a9352
|
|
BLAKE2b-256 checksum How to use checksums |
76fb020401a01cdcdd08b9044a1ab25ca81f38035d2fe3bc114c52b432063eba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.14
|
Release files / cellsium-1.0.0-py2.py3-none-any.whl
| Download URL | cellsium-1.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 61.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
a031cc453d66ceec31d28aee14f705a354544de7e9b56b04a7cab23e7e2a03ed
|
|
BLAKE2b-256 checksum How to use checksums |
27a84648a69c5a7140d04a1f6b22b58462d52325a1b26566b04730ca459a0740
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.14
|
Security for cellsium 1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.