PMCX-CL - Python bindings for Monte Carlo eXtreme (OpenCL) photon transport simulator

• Copyright: (C) Matin Raayai Ardakani (2022-2023) <raayaiardakani.m at northeastern.edu> and Qianqian Fang (2019-2026) <q.fang at neu.edu>
• License: GNU Public License V3 or later
• Version: 0.8.1
• URL: https://pypi.org/project/pmcxcl/
• Github: https://github.com/fangq/mcxcl

This module provides a Python binding for Monte Carlo eXtreme for OpenCL (MCXCL). For other binaries, including the standalone executable and the MATLAB bindings, see our website.

Monte Carlo eXtreme (MCX) is a fast photon transport simulation software for 3D heterogeneous turbid media. By taking advantage of the massively parallel threads and extremely low memory latency in a modern graphics processing unit (GPU), MCX is capable of performing Monte Carlo (MC) photon simulations at a blazing speed, typically hundreds to a thousand times faster than a single-threaded CPU-based MC implementation.

How to Install

• PIP: pip install pmcxcl pmcx, see https://pypi.org/project/pmcxcl/

Binary wheels are available for Linux (x86_64 and aarch64), macOS (Apple silicon and Intel) and Windows. The pmcx package provides the utility functions (detweight, meanpath, loadmc2, mcxlab post-processing etc.) that pmcxcl imports; on macOS, pip installs it as a pure-python package.

Runtime Dependencies

• CPU or GPU: An OpenCL-capable CPU or GPU; most modern CPUs or GPUs support OpenCL - an industrial-standard heterogeneous computing library and specification (https://www.khronos.org/opencl/)
• OpenCL CPU or GPU runtime/driver: Both NVIDIA and AMD GPU graphics drivers should contain out-of-box OpenCL runtimes or drivers; for Intel GPUs, one should install additional OpenCL runtime support from https://github.com/intel/compute-runtime or install the intel-opencl-icd package if the OS provides (such as Ubuntu 22.04); one can also install an open-source OpenCL runtime POCL, using package manager such as sudo apt-get install pocl-opencl-icd. However, POCL's support is largely limited to CPUs. You do not need to install CUDA SDK to use pmcxcl.
• Python: Python 3.6 and newer is required. Python 2 is not supported.
• numpy: Used to pass/receive volumetric information to/from pmcxcl. To install, use either conda or pip package managers: pip install numpy or conda install numpy
• (optional) jdata: Only needed to read/write JNIfTI output files. To install, use pip: pip install jdata on all operating systems; For Debian-based Linux distributions, you can also install to the system interpreter using apt-get: sudo apt-get install python3-jdata. See https://pypi.org/project/jdata/ for more details.
• (optional) bjdata: Only needed to read/write BJData/UBJSON files. To install, run pip install bjdata on all operating systems; For Debian-based Linux distributions, you can also install to the system interpreter using apt-get: sudo apt-get install python3-bjdata. See https://pypi.org/project/bjdata/ for more details.
• (optional) matplotlib: For plotting the results. To install, run either pip install matplotlib or conda install matplotlib

Build Instructions

Build Dependencies

• Operating System: pmcxcl and mcxcl can be compiled on most OSes, including Windows, Linux and MacOS.

• OpenCL library: compiling mcxcl or pmcxcl requires to link with libOpenCL.so on Linux, or libOpenCL.dylib on MacOS or OpenCL.dll on Windows. These libraries should have been installed by either graphics driver or OpenCL runtimes.

• Python Interpreter: Python 3.6 or above. The pip Python package manager and the wheel package (available via pip) are not required but recommended.

• C/C++ Compiler: pmcxcl can be compiled using a wide variety of C compilers, including

  • GNU GCC for Linux, MacOS (installed via MacPorts or brew), and Windows (installed via msys2, mingw64 or cygwin64)
  • Microsoft Visual Studio C/C++ Compiler for Windows.
  • Apple Clang for macOS, available via Xcode.

  Refer to each OS's online documentations for more in-depth information on how to install these compilers. MacOS provides built-in OpenCL library support.

• OpenMP: The installed C/C++ Compiler should have support for OpenMP. GCC and Microsoft Visual Studio compiler support OpenMP out of the box. Apple Clang, however, requires manual installation of OpenMP libraries for Apple Clang. The easiest way to do this is via the Brew package manager, preferably after selecting the correct Xcode version:

    brew install libomp
    brew link --force libomp
  

• CMake: CMake version 3.15 and later is required. Refer to the CMake website for more information on how to download. CMake is also widely available on package managers across all operating systems.

Build Steps

1. Ensure that cmake, python and the C/C++ compiler are all located over your PATH. This can be queried via echo $env:PATH on Windows or echo $PATH on Linux. If not, locate them and add their folder to the PATH.

2. Clone the repository and switch to the pmcxcl/ folder:

       git clone --recursive https://github.com/fangq/mcxcl.git
       cd mcxcl/pmcxcl
   

3. One can run python3 setup.py install or python3 -m pip install . to both locally build and install the module

4. If one only wants to locally build the module, one should run python3 -m pip wheel .

5. If the binary module is successfully built locally, you should see a binary wheel file pmcxcl-X.X.X-cpXX-cpXX-*.whl stored inside the mcxcl/pmcxcl folder. You can install this wheel package using python3 -m pip install --force-reinstall pmcxcl-*.whl to force installing this locally compiled pmcxcl module and overwrite any previously installed versions.

How to use

The PMCXCL module is easy to use. You can use the pmcxcl.gpuinfo() function to first list the OpenCL CPUs and GPUs available on your computer; if a device is found, you can then call the mcxlab() function, or run(), to launch a photon simulation. The device is selected by cfg['gpuid'] (1 for the first device, the default).

A simulation can be defined conveniently in two approaches - a one-liner and a two-liner:

• For the one-liner, one simply passes each MCX simulation setting as a keyword argument. The supported setting names are compatible with nearly all the input fields of the MATLAB version of MCX/MCXCL - MCXLAB

import pmcxcl
import numpy as np
import matplotlib.pyplot as plt

res = pmcxcl.run(nphoton=1000000, vol=np.ones([60, 60, 60], dtype='uint8'), tstart=0, tend=5e-9, 
               tstep=5e-9, srcpos=[30,30,0], srcdir=[0,0,1], prop=np.array([[0, 0, 1, 1], [0.005, 1, 0.01, 1.37]]))
res['flux'].shape

plt.imshow(np.log10(res['flux'][30,:, :]))
plt.show()

• Alternatively, one can also define a Python dict object containing each setting as a key, and pass on the dict object to pmcxcl.run(), or preferably, pmcxcl.mcxlab()

import pmcxcl
import numpy as np
cfg = {'nphoton': 1000000, 'vol':np.ones([60,60,60],dtype='uint8'), 'tstart':0, 'tend':5e-9, 'tstep':5e-9,
       'srcpos': [30,30,0], 'srcdir':[0,0,1], 'prop':[[0,0,1,1],[0.005,1,0.01,1.37]]}
res = pmcxcl.run(cfg)      # returns detected photon data as a concatenated 2D array res['detp']
# or alternatively/preferably (requires pmcx)
res = pmcxcl.mcxlab(cfg)   # post-processes res['detp'] and res['traj'] into dicts

The detected photon data returned by pmcxcl.mcxlab() can be post-processed with the utility functions from pmcx, for example, pmcxcl.detweight(res['detp'], cfg['prop']) computes the detected photon weights.

Log output

The messages of pmcxcl.run() - the echo of the cfg fields and the simulation log (the banner, timings and absorbed fraction) - are controlled by cfg['flog'], as in MATLAB: 2 (default) prints them to Python's sys.stdout, so they show in Jupyter notebooks; 1 prints them to the stdout of the process, and 0 does the same without the banner; a string appends them to that file. cfg['flog'] = os.devnull silences everything; errors are still raised as Python exceptions.

Reproducible simulations

By default, pmcxcl runs in the autopilot mode (cfg['autopilot']=1), where photons are dispatched to the threads dynamically and the kernel is compiled with faster but less strict math. As a result, two runs with the same cfg['seed'] agree statistically, but do not simulate the identical set of photons. To reproduce a simulation exactly, set cfg['autopilot']=0 together with a fixed cfg['seed'], and keep the thread settings (cfg['nthread'], cfg['nblocksize']) unchanged.