AMS-BP is a powerful simulation tool for advanced fluorescence microscopy experiments. This guide covers both command-line usage and library integration.
Overview of the AMS workflow. A ground truth is created, a, with $f_{n}$ fluorophore types of $N_{f_{n}}$ molecules each. If applicable, the motion of these molecules is modelled using a 3D bounded FBM with fluctuating generalized diffusion coefficients and Hurst parameters. Variations are modelled as a Markov Chain and require user-defined rate constants as parameters. Different fluorophores can have different motion models. Given the microscope parameters specific to the experimental procedure to simulate, at every time $t_{j}$, the excitation intensity for each channel (b) is calculated at each fluorophore's location, c-d. For $t_{j} \rightarrow t_{j+\Delta t}$, the photophysical state trajectory of the fluorophore is simulated using the light intensity at the molecule's location as input for any light-dependent transition rates, d. For the duration that the shutter is open and light is emitted from the sample, emission filters for each channel are applied before the convolution with PSF models, e-f. The incident photons on the detector are then converted to photoelectrons and finally to digital units using the detector models provided, g.
Find detailed API references for the library at: joemans3/github.io/AMS_BP
A more detailed example is provided in the jupyter notebook in the examples. For starters refer to the VisualizingIndividualModules. Then head over to the laser modulation module which will show how to change the laser power over time in the simulations. Then view an example of a complex experiment setup for FRAP which is possible by the use of compositions of modules in this simulation library.
!!ATTENTION!! - Please note that you NEED to install the optional dependencies to run the examples in full. This is mainly for installing the Jupyter notebook extensions, matplotlib and other visualization packages. In whatever environment you install this package, make sure to install with all dependencies. As an example, for UV this would be evoking:
uv sync --all-extraswhile inside the root of the project, for syncing the environment.
- Install UV.
- Run the command:
uv tool install AMS_BP- You will have access to three CLI commands (using the uv interface):
run_AMS_BP runsim: This is the main entry point for the simulation. (seerun_AMS_BP runsim --helpfor more details)run_AMS_BP config: This is a helper tool to generate a template config file for the simulation. (seerun_AMS_BP config --helpfor more details)run_AMS_BP gui: to start the GUI. See GUI Documentation- Note: using
run_AMS_BP --helpwill show you all the available commands.
- You can now use these tools (they are isolated in their own env created by uv, which is cool).
- If using pip, make sure the environment is python >= 3.12
- Run:
pip install AMS_BPAMS-BP provides a command-line interface with three main commands:
# Generate a default configuration file
run_AMS_BP config [OPTIONS]
# Run a simulation using a configuration file
run_AMS_BP runsim CONFIG_FILE
#start the GUI
run_AMS_BP gui-o, --output_path PATH: Specify the output directory for the configuration file-r, --recursive_o: Create output directory if it doesn't exist
In addition to the CLI and programmatic API, AMS-BP comes with a graphical interface to guide users through the configuration, simulation, and analysis pipeline.
The GUI provides the following tools from a single interface:
- Create Configuration File — Launches the visual configuration builder
- Run Simulation from Config — Select a .toml file and run the simulation with logging and progress tracking
- Visualize Microscopy Data (Napari) — Open TIFF, PNG, ND2, or Zarr image files and view with the Napari viewer
- Package Logs for Sharing — Package run directories (e.g., run_2024_04_20_001) into a .zip file for archival or collaboration
To start the GUI, run:
run_AMS_BP guiPlease note, the first time the package is used it will take a minute to start. For detailed walkthrough see the GUI Documentation.
The configuration file (sim_config.toml) is divided into several key sections:
For a detailed description of the configuration file, refer to the Configuration File Reference.
version = "0.1"
length_unit = "um" # micrometers
time_unit = "ms" # milliseconds
diffusion_unit = "um^2/s" # diffusion coefficient units-
Cell Parameters
- Define cell space dimensions
-
Molecule Parameters
- Number of molecules per type
- Tracking types (constant/fbm)
- Diffusion coefficients
- State transition probabilities
-
Global Parameters
- Sample plane dimensions
- Cycle count -> Exposure time + Interval time
- Exposure and interval times
-
Fluorophore Configuration
- Any number of fluorophores
- Any number of States per fluorophore
- Fluorophore StateType: (bright, dark, bleached) -> All States must be one of these.
- Transition parameters
- Spectral properties
-
Optical Configuration
- PSF parameters
- Laser settings
- Channel configuration
- Camera settings
AMS-BP's CLI currently supports two types of experiments:
(however this can be extended when used as a library)
[experiment]
experiment_type = "time-series"
z_position = 0.0
laser_names_active = ["red", "blue"]
laser_powers_active = [0.5, 0.05]
laser_positions_active = [[5, 5, 0], [5, 5, 0]][experiment]
experiment_type = "z-stack"
z_position = [-0.5, -0.4, -0.3, -0.2, -0.1, 0, 0.1, 0.2, 0.3, 0.4, 0.5]
laser_names_active = ["red", "blue"]
laser_powers_active = [0.5, 0.05]
laser_positions_active = [[5, 5, 0], [5, 5, 0]]To run the default configuration:
- Make sure you followed the uv tool installation.
- Make a copy of the default configuration file using the command:
run_AMS_BP config- Run the sim:
run_AMS_BP runsim sim_config.toml- View the results in the newly created folder, whose name is defined in the config file.
1. Irregular cell shapes with motion models (supported with release of v0.2.0)
2. Stimulated Emission models
3. STORM workflow examples
4. CTRW motion models
5. Simpler configurations
NOTE: Please note that this application DOES NOT currently model the process of stimulated emission, and as such is not suitable for simulating stimulated emission microscopy (STED)-type experiments. Work in this area is ongoing.