VCell Moving Boundary Solver

A C++ solver library for moving-boundary problems in biological systems. A single build produces three artifacts:

Artifact	Description
`MovingBoundarySolver`	Standalone command-line binary
`libMovingBoundaryLib`	Linkable static (or shared) library
`vcellmbsolver_py`	Python extension module (pybind11)

Prerequisites

All platforms

Dependency	Notes
CMake ≥ 3.13	https://cmake.org/download/
C++14 compiler	GCC 7+, Clang 6+, MSVC 2017+
HDF5 (C + C++)	See platform sections below
Python 3 + headers	Python 3.8+ recommended
pybind11	`pip install pybind11` or system package
All former VCell monorepo dependencies (FronTier, ExpressionParser,
vcommons) are bundled in this repo and built automatically — no external
paths required.

Building

Ubuntu / Debian

# System dependencies
sudo apt-get install cmake libhdf5-dev python3-dev python3-pip
pip3 install pybind11

# Configure (substitute your actual library paths)
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release

# Build everything
cmake --build build --parallel

Output files land in build/bin/:

build/bin/
  MovingBoundarySolver        # binary
  libMovingBoundaryLib.a      # static library
  vcellmbsolver_py.cpython-*.so  # Python module

macOS

# Dependencies via Homebrew
brew install cmake hdf5 python pybind11

# Configure
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release

# Build everything
cmake --build build --parallel

For Apple Silicon the build system detects the architecture automatically and sets -DCMAKE_OSX_ARCHITECTURES=arm64. On Intel Macs it sets x86_64.

Windows (Visual Studio)

Install prerequisites:

CMake
Python 3 (check "Add to PATH")
HDF5: use the official HDF Group Windows installer or vcpkg (vcpkg install hdf5)
pybind11: pip install pybind11 or vcpkg (vcpkg install pybind11)

cmake -S . -B build

cmake --build build --config Release --parallel

If using vcpkg, add -DCMAKE_TOOLCHAIN_FILE=C:\vcpkg\scripts\buildsystems\vcpkg.cmake to the configure step so CMake finds the vcpkg-installed packages automatically.

Output files land in build\bin\Release\.

Build options

CMake variable	Default	Description
`CMAKE_BUILD_TYPE`	`Release`	`Release`, `Debug`, `RelWithDebInfo`, `MinSizeRel`
`BUILD_SHARED_LIBS`	`OFF`	Build `libMovingBoundaryLib` as a shared library instead of static
`BUILD_TESTING`	`ON`	Also build the `TestMovingBoundary` test executable
`VARIABLE_SPECIES_STORAGE`	`OFF`	Enable dynamic species storage (`-DMB_VARY_MASS`)

Example — debug build, shared library, no tests:

cmake -S . -B build \
  -DCMAKE_BUILD_TYPE=Debug \
  -DBUILD_SHARED_LIBS=ON \
  -DBUILD_TESTING=OFF \
cmake --build build --parallel

Running the tests

Tests are built by default (BUILD_TESTING=ON). After a successful build:

cd build
ctest --output-on-failure

Test suites

All three suites run automatically when you invoke ctest. The Python tests require pytest (pip install pytest).

Suite	Name in ctest	Framework
Moving boundary unit tests (~150 cases)	`TestMovingBoundary.*`	Google Test
Expression parser smoke test	`ExpressionParserTest`	custom main
Python wrapper tests	`PyVcellMbSolver`	pytest

Python test prerequisites

No manual setup required. CMake creates an isolated virtual environment in build/python_venv/ at configure time and installs pytest into it automatically. The venv is recreated on every cmake -S . -B build run.

The Python tests import vcellmbsolver_py (the compiled extension) and vcellmbsolver (the pure-Python wrapper in python/). ctest sets PYTHONPATH so both are importable from the build tree without installation.

Useful ctest options

# Run in parallel
ctest --output-on-failure -j$(nproc)

# Run only tests whose name matches a pattern
ctest --output-on-failure -R "algo"
ctest --output-on-failure -R "ExpressionParser"
ctest --output-on-failure -R "PyVcellMbSolver"

# List all registered tests without running them
ctest -N

# Show full output even for passing tests
ctest -V

Running the Python tests directly

After configuring, the venv already has pytest installed. Run the suite directly using the venv's Python:

PYTHONPATH=build/bin:python build/python_venv/bin/python -m pytest python/tests -v

On Windows, substitute build\python_venv\Scripts\python.exe.

Skipping tests

Pass -DBUILD_TESTING=OFF at configure time to skip building and registering the test executables entirely (this also disables the Python tests):

cmake -S . -B build -DBUILD_TESTING=OFF

Using the binary

./build/bin/MovingBoundarySolver <input.xml> <output.h5>

The input file format is described in metadata/MovingBoundarySolverInputFile.docx and validated by Solver/MovingBoundarySetup.xsd.

Linking the library

Add to your project's CMakeLists.txt:

find_library(MB_LIB MovingBoundaryLib HINTS /path/to/vcell-mbsolver/build/bin)
find_path(MB_INCLUDE MovingBoundaryParabolicProblem.h
    HINTS /path/to/vcell-mbsolver/Solver/include)

target_link_libraries(my_target PRIVATE ${MB_LIB})
target_include_directories(my_target PRIVATE ${MB_INCLUDE})

Or install the project first and use the installed headers under <prefix>/include/vcell-mbsolver/.

Using the Python module

The bindings are shipped as the pyvcell_mbsolver package: the compiled extension is the private submodule pyvcell_mbsolver._core, and the high-level wrapper (MovingBoundarySolver, observer base classes) is the package itself.

import sys
sys.path.insert(0, "/path/to/vcell-mbsolver/build/bin")

import pyvcell_mbsolver
from pyvcell_mbsolver import MovingBoundarySolver   # high-level wrapper
from pyvcell_mbsolver import _core                  # low-level C++ API
# See python/pyvcellmbsolver.cpp for the exposed _core API

After cmake --install build --prefix /usr/local, the package is installed to the active Python's site-packages and importable directly:

import pyvcell_mbsolver

Python package & wheels

The repository also ships a PEP 517 build configuration (pyproject.toml, using the scikit-build-core backend) that drives the same CMake build to produce an installable Python wheel. The wheel contains only the pyvcell_mbsolver package (the _core extension and its pure-Python wrapper) — not the C++ library, CLI binary, or headers.

Install from a downloaded wheel

CI builds redistributable wheels for Linux (x86_64 + arm64) and macOS (x86_64 + arm64, macOS 15+) and uploads them as workflow artifacts (see the Wheels GitHub Actions workflow). Download the wheel for your platform/Python version and:

pip install pyvcell_mbsolver-<version>-<tags>.whl
python -c "import pyvcell_mbsolver; from pyvcell_mbsolver import _core; print('ok')"

The wheels are self-contained: the shared HDF5 libraries are vendored in by the wheel-repair step (auditwheel / delocate), so no system HDF5 install is required to use a wheel.

Windows is not currently supported. The bundled FronTier library is Unix/GCC code that does not compile under MSVC (its POINT/boolean types clash with the Windows SDK and it relies on GCC anonymous-struct extensions). Windows users can build/run under WSL using the Linux wheels.

Build a wheel locally

Building from source still needs the native toolchain and dependencies from the Prerequisites section (CMake, a C++14 compiler, HDF5, Boost):

pip install build
python -m build --wheel          # writes dist/vcellmbsolver-*.whl
pip install dist/vcellmbsolver-*.whl

pip install . works too. Wheel builds set BUILD_TESTING=OFF and OPTION_TARGET_MESSAGING=OFF automatically (see [tool.scikit-build] in pyproject.toml).

Publishing to PyPI

The Wheels workflow has a publish job that uploads the built wheels and sdist to PyPI via trusted publishing (OIDC — no stored API token). It runs only on v* tag pushes and stays dormant until a one-time setup is done on PyPI:

Register the project on PyPI (claim the pyvcell_mbsolver name).
Under the project's Publishing settings, add a trusted publisher:
- Owner: virtualcell, Repository: vcell-mbsolver
- Workflow: wheels.yml, Environment: pypi
Create the pypi environment in the repo settings (optionally with reviewers/branch protection).

Once configured, pushing a vX.Y.Z tag builds all wheels and publishes them. Until then, normal pushes and PRs simply produce downloadable wheel artifacts.

Dry run on TestPyPI first (recommended)

The workflow also has a publish-testpypi job to rehearse the release against TestPyPI before touching real PyPI. It runs only when the workflow is manually dispatched with the testpypi flag, and needs its own one-time setup mirroring the above:

Create a TestPyPI account (separate from PyPI; 2FA required).
At https://test.pypi.org/manage/account/publishing/, add a pending publisher:
- PyPI Project Name: pyvcell_mbsolver
- Owner: virtualcell, Repository: vcell-mbsolver
- Workflow: wheels.yml, Environment: testpypi
Create a testpypi environment in the repo settings.

Then trigger the dry run (no tag needed):

gh workflow run wheels.yml -f testpypi=true

(or Actions → Wheels → Run workflow, check the box). It builds all wheels + sdist and uploads them to TestPyPI; skip-existing keeps repeat runs of the same version from failing. Verify at https://test.pypi.org/project/pyvcell-mbsolver/, then do the real release by tagging vX.Y.Z.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

pyvcell_mbsolver-1.0.2.tar.gz (2.0 MB view details)

Uploaded Jun 24, 2026 Source

Built Distributions

If you're not sure about the file name format, learn more about wheel file names.

The dropdown lists show the available interpreters, ABIs, and platforms. Enable javascript to be able to filter the list of wheel files.

pyvcell_mbsolver-1.0.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (3.4 MB view details)

Uploaded Jun 24, 2026 CPython 3.13manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

pyvcell_mbsolver-1.0.2-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl (3.2 MB view details)

Uploaded Jun 24, 2026 CPython 3.13manylinux: glibc 2.27+ ARM64manylinux: glibc 2.28+ ARM64

pyvcell_mbsolver-1.0.2-cp313-cp313-macosx_15_0_x86_64.whl (3.4 MB view details)

Uploaded Jun 24, 2026 CPython 3.13macOS 15.0+ x86-64

pyvcell_mbsolver-1.0.2-cp313-cp313-macosx_15_0_arm64.whl (3.0 MB view details)

Uploaded Jun 24, 2026 CPython 3.13macOS 15.0+ ARM64

pyvcell_mbsolver-1.0.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (3.4 MB view details)

Uploaded Jun 24, 2026 CPython 3.12manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

pyvcell_mbsolver-1.0.2-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl (3.2 MB view details)

Uploaded Jun 24, 2026 CPython 3.12manylinux: glibc 2.27+ ARM64manylinux: glibc 2.28+ ARM64

pyvcell_mbsolver-1.0.2-cp312-cp312-macosx_15_0_x86_64.whl (3.4 MB view details)

Uploaded Jun 24, 2026 CPython 3.12macOS 15.0+ x86-64

pyvcell_mbsolver-1.0.2-cp312-cp312-macosx_15_0_arm64.whl (3.0 MB view details)

Uploaded Jun 24, 2026 CPython 3.12macOS 15.0+ ARM64

pyvcell_mbsolver-1.0.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (3.4 MB view details)

Uploaded Jun 24, 2026 CPython 3.11manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

pyvcell_mbsolver-1.0.2-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl (3.2 MB view details)

Uploaded Jun 24, 2026 CPython 3.11manylinux: glibc 2.27+ ARM64manylinux: glibc 2.28+ ARM64

pyvcell_mbsolver-1.0.2-cp311-cp311-macosx_15_0_x86_64.whl (3.4 MB view details)

Uploaded Jun 24, 2026 CPython 3.11macOS 15.0+ x86-64

pyvcell_mbsolver-1.0.2-cp311-cp311-macosx_15_0_arm64.whl (3.0 MB view details)

Uploaded Jun 24, 2026 CPython 3.11macOS 15.0+ ARM64

pyvcell_mbsolver-1.0.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl (3.4 MB view details)

Uploaded Jun 24, 2026 CPython 3.10manylinux: glibc 2.27+ x86-64manylinux: glibc 2.28+ x86-64

pyvcell_mbsolver-1.0.2-cp310-cp310-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl (3.2 MB view details)

Uploaded Jun 24, 2026 CPython 3.10manylinux: glibc 2.27+ ARM64manylinux: glibc 2.28+ ARM64

pyvcell_mbsolver-1.0.2-cp310-cp310-macosx_15_0_x86_64.whl (3.4 MB view details)

Uploaded Jun 24, 2026 CPython 3.10macOS 15.0+ x86-64

pyvcell_mbsolver-1.0.2-cp310-cp310-macosx_15_0_arm64.whl (3.0 MB view details)

Uploaded Jun 24, 2026 CPython 3.10macOS 15.0+ ARM64

File details

Details for the file pyvcell_mbsolver-1.0.2.tar.gz.

File metadata

Download URL: pyvcell_mbsolver-1.0.2.tar.gz
Upload date: Jun 24, 2026
Size: 2.0 MB
Tags: Source
Uploaded using Trusted Publishing? Yes
Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for pyvcell_mbsolver-1.0.2.tar.gz
Algorithm	Hash digest
SHA256	`65e1b5e4508762f32178e19da7755451812feb8a56a624f4df340a8cff4273b9`
MD5	`3d35611530a44d7e006d720d33a08d1b`
BLAKE2b-256	`3031f4ed5bff042ff7610d7bf4628ae4f5ce42cb8a07101a9658768eb4abb7a2`

Algorithm	Hash digest
SHA256	`e94a211a5a8a8a54d55c51a12c988b185b2d30e48f7cbdf0df862090c57b4cb9`
MD5	`8903a0136dca42926588d2f433ba3ef6`
BLAKE2b-256	`fc8a5bc62bd1d477e2703570815a8c0e653d27c46d74dd41999061970edc3203`

Algorithm	Hash digest
SHA256	`1280fec3320ab3507e18fa64bf29d64c835541ef5f3496b26d3e833b64a0caae`
MD5	`9bd4a917eef5b49c0ac7a3bf5273861a`
BLAKE2b-256	`3463470fa42672fc94872485d043b465a1f0b143e9048cdf5c72b4175a418389`

Algorithm	Hash digest
SHA256	`32bf8606e09e5b148934a5de409d7cd56a61c0d879acde7c40fe69dfb178e198`
MD5	`8287cae0e8f646348761e7801ea16470`
BLAKE2b-256	`3b92bc9759182c5369d3cc904ec02090e84ee3bebe5aba1c588b369f976e2702`

Algorithm	Hash digest
SHA256	`ddf2d03836bb34fe46ca10f9c949ec4c50c2bb1d1e24adcefed4eeb618c1ce81`
MD5	`bb45c1060dc5b507ed44e3bf2bb1b4af`
BLAKE2b-256	`ca13923fff063e723dfd8f7be4328f61830a89408e2e526772cbb6e5fb04d830`

Algorithm	Hash digest
SHA256	`2b2d3e8cdefb3ccc0380ed20892790fda85e94b9a00301c77e2f09f2ad45d040`
MD5	`5b38f9ffc60a6e6cf264283fbe86d927`
BLAKE2b-256	`2a455970837d24764d179f37569ea846e3bb620dcd9ed02fa1e4e224ec726b9a`

Algorithm	Hash digest
SHA256	`05feaf92b7dbf9a9a2906542dc2a3be889c85fd0148c4f4294622b6294d57778`
MD5	`4465e7c62e1424e1d486792d56b61c24`
BLAKE2b-256	`93a8e659d94408204f6a187b0c7355ba10159305e5cc8afd5474b5a8b12bf4d3`

Algorithm	Hash digest
SHA256	`8d7350c47bea003da9a97d2facdefe7132a6094f21580760e16f9e7ec2e48ad5`
MD5	`8140931306aa595ea7fd76da279f4f68`
BLAKE2b-256	`eace49d1d5c03faf867b18083fce4398ca1212026d8bc605f32131db638b90ba`

Algorithm	Hash digest
SHA256	`10006403a9ea7030641619d3c401ff7c36625018f87d50b6398699b33f28e3e7`
MD5	`67a984fd5d7a6d867b6cba6c5f6a3ced`
BLAKE2b-256	`f9492d0907e1d5cf46df761c1f5d4b9419ef3f6237dd86b9096afcff8a59ee98`

Algorithm	Hash digest
SHA256	`33e91717eabf66bd3364abbb05d937f84bf6cf05d7083dfa37adb00d580e744f`
MD5	`07e5a1afd47774cf08416847a4545b8c`
BLAKE2b-256	`ab3cacbcee5597611266fe3cfbc0c85fb7640dc3a7fd7c29aa4f8312540751fa`

Algorithm	Hash digest
SHA256	`f3dfee0c812114bb1f1bb61787a899d4dc4375f465b06fb601801ae6da1fcc49`
MD5	`7b477c9235677518b93af3c621599148`
BLAKE2b-256	`455154cd610c5d135f2cb6198347b75c70ed0fce70bccc42d2df7cdd7223de0a`

Algorithm	Hash digest
SHA256	`805659d32464d0836483486e4384d702c5f8ab5a74d6dacff7327cca87bf3c5c`
MD5	`583926fee7efc4fa2b01098ba29b474e`
BLAKE2b-256	`39b767328e9ae671647519eab08579cf8f4f3d211b42287b0694f153b53b0b6a`

Algorithm	Hash digest
SHA256	`69e3c2d03c48bdfb8b7347372a36b231b34274a26979321bd5763ba93263abc8`
MD5	`569810790e4aa54ccb8d965388159e43`
BLAKE2b-256	`99ba232ee546a24a86eb9ba3c2fab766ed9aea837a1e7608b13541442f4217d3`

Algorithm	Hash digest
SHA256	`aa8e5674e610a2f228370ce07d8d361e5b05e1eabff4db71a246084505ed79a8`
MD5	`dd51392021fc4ffbc862ff42b0eb8e18`
BLAKE2b-256	`3247cff8b6b312b1c4ff5aaa16e188a7bd46a4df9bff1f0130d50479fd90b4cc`

Algorithm	Hash digest
SHA256	`6e9dce303eda3879c10262256b9bcc587ce17efa65735a0a73c72f47ee0f75e9`
MD5	`7ac1445af66d7cda925c04d8c04de9bb`
BLAKE2b-256	`e4fafc7036dee0883f78de00177e66aa44af928527bf9b1b351d2058495c2fd9`

Algorithm	Hash digest
SHA256	`3ffe7b994e460e71ac7bd9fe5e7b2e0e5a37c3cc01c90b0395fb153cdd117d45`
MD5	`06efc29e7b73817389526c28fbc11ec1`
BLAKE2b-256	`a8fd4b77b170f85068c2dcb0478b9ac516e1cc7d6658be79fbe94ed28fee1f32`

Algorithm	Hash digest
SHA256	`7e3b8a4e9d75f5babdbd7f00b2be0e949d0462a4a9744d851cfae31bcb123b97`
MD5	`52e7c386a75ea0c38c84b7ba3357f3da`
BLAKE2b-256	`4580f2452ec305eabdfb965241d63d35ebdc55c412cadc1b7d32d677341d5534`

pyvcell-mbsolver 1.0.2

VCell Moving Boundary Solver

Prerequisites

All platforms

Building

Ubuntu / Debian

macOS

Windows (Visual Studio)

Build options

Running the tests

Test suites

Python test prerequisites

Useful ctest options

Running the Python tests directly

Skipping tests

Using the binary

Linking the library

Using the Python module

Python package & wheels

Install from a downloaded wheel

Build a wheel locally

Publishing to PyPI

Dry run on TestPyPI first (recommended)

Project links

Key dates

1 maintainer

GitHub Statistics

License

Requires

Classifiers

Download files

Source Distribution

Built Distributions

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes