zarr-particle-tools 0.3.4__tar.gz

zarr_particle_tools-0.3.4/.github/workflows/conventional-commits.yml

@@ -0,0 +1,22 @@
+# Validates PR title follows conventional commits
+name: conventional-commits
+permissions:
+  contents: read
+
+on:
+  pull_request:
+    branches: [main]
+    types:
+      - edited
+      - opened
+      - synchronize
+      - reopened
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+jobs:
+  conventional_commit_title:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: chanzuckerberg/github-actions/.github/actions/conventional-commits@9a7a0d55060523befd055d301c29d9190cd0244f

zarr_particle_tools-0.3.4/.github/workflows/py-formatting.yml

@@ -0,0 +1,26 @@
+name: Python Linting
+
+permissions:
+  contents: read
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+jobs:
+  pre_commit_checks:
+    name: pre-commit checks
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd
+      - uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c
+        with:
+          python-version: "3.12.6"
+      - name: Install action-validator with asdf
+        uses: asdf-vm/actions/install@b7bcd026f18772e44fe1026d729e1611cc435d47
+        with:
+          tool_versions: |
+            action-validator 0.6.0
+      - name: check linting
+        uses: pre-commit/action@2c7b3805fd2a0fd8c1884dcaebf91fc102a13ecd

zarr_particle_tools-0.3.4/.github/workflows/pytest.yml

@@ -0,0 +1,105 @@
+name: Run Pytest
+permissions:
+  contents: read
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  workflow_dispatch:
+
+concurrency:
+  group: pytest
+  cancel-in-progress: true
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+        include:
+          - python-version: "3.10"
+            cache: true
+
+    steps:
+      - name: Maximize build space (#1)
+        uses: mathio/gha-cleanup@aca3d43a05bf564f5fc69acb929a65b01797f22b
+        with:
+          remove-browsers: true
+          verbose: true
+
+      - name: Maximize build space (#2)
+        run: |
+          set +e
+          sudo apt-get purge temurin-*-jdk adoptopenjdk-* adoptium-ca-certificates openjdk-* session-manager-plugin azure-cli google-cloud-cli heroku
+          sudo apt-get purge postgresql-* libpq-dev libmysqlclient* msodbcsql* mssql-tools unixodbc-dev mysql-client* mysql-common mysql-server* php*-*sql sphinxsearch mongodb*
+          sudo rm -rf /usr/share/dotnet
+          sudo rm -rf /usr/local/lib/android
+          sudo rm -rf /opt/ghc
+          sudo rm -rf /usr/local/lib/terraform
+          sudo rm -rf /usr/lib/jvm/ /usr/local/graalvm /usr/share/java/selenium-server*.jar
+          sudo rm -rf /usr/share/mysql* /opt/mssql-tools /usr/local/sqlpackage
+          sudo rm -rf /usr/local/bin/aliyun /usr/local/bin/aws /usr/local/bin/aws_completer /usr/local/aws-cli /usr/local/aws /usr/local/aws-sam-cli /usr/local/bin/azcopy* /usr/share/az_* /opt/az /usr/bin/az /usr/share/google-cloud-sdk /usr/lib/google-cloud-sdk /usr/local/bin/bicep /usr/local/bin/oc /usr/local/bin/oras /usr/local/lib/heroku
+          docker rm -vf $(docker ps -aq)
+          docker rmi -f $(docker images -aq)
+          docker system df
+
+      - uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd
+
+      - name: Set up Python
+        uses: actions/setup-python@e797f83bcb11b83ae66e0230d6156d7c80228e7c
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install uv
+          uv pip install --system -e .[dev]
+
+      - name: Restore test data from cache
+        id: cache
+        uses: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830
+        with:
+          path: tests/data
+          key: zenodo-17529862
+
+      - name: Download test data from Zenodo (cache miss)
+        if: steps.cache.outputs.cache-hit != 'true'
+        shell: bash
+        run: |
+          set -euxo pipefail
+          mkdir -p tests/data
+          cd tests/data
+
+          # Download both files with retries and resume
+          curl -L --fail --retry 5 --retry-delay 5 --continue-at - \
+            -o zarr_particle_tools_test_data_large.tar.gz \
+            "https://zenodo.org/records/17529862/files/zarr_particle_tools_test_data_large.tar.gz?download=1"
+
+          curl -L --fail --retry 5 --retry-delay 5 --continue-at - \
+            -o zarr_particle_tools_test_data_small.tar.gz \
+            "https://zenodo.org/records/17529862/files/zarr_particle_tools_test_data_small.tar.gz?download=1"
+
+      - name: Save test data to cache
+        if:  ${{ matrix.cache && steps.cache.outputs.cache-hit != 'true' && github.ref == 'refs/heads/main' }}
+        uses: actions/cache/save@0057852bfaa89a56745cba8c7296529d2fc39830
+        with:
+          path: tests/data
+          key: zenodo-17529862
+
+      - name: Extract test data from tar.gz files
+        run: |
+          # Extract
+          cd tests/data
+          for f in *.tar.gz; do tar -xzf "$f"; done
+
+      - name: List contents
+        run: ls -lah tests/data
+
+      - name: Run tests
+        run: |
+          pytest -n auto -vvv

zarr_particle_tools-0.3.4/.github/workflows/release-please.yml

@@ -0,0 +1,64 @@
+name: Create Release PRs
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+  issues: write
+  pull-requests: write
+
+jobs:
+  release-please:
+    concurrency:
+      group: ${{ github.workflow }}-${{ github.ref }}
+      cancel-in-progress: true
+
+    runs-on: ubuntu-latest
+    steps:
+      - name: release please
+        uses: googleapis/release-please-action@16a9c90856f42705d54a6fda1823352bdc62cf38
+        id: release
+        with:
+          manifest-file: ".release-please.manifest.json"
+          config-file: "release-please.config.json"
+          target-branch: "main"
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+    outputs:
+      paths_released: ${{ steps.release.outputs.paths_released }}
+
+  publish-pypi-package:
+    name: Build and publish Python package to PyPI
+    runs-on: ubuntu-latest
+    needs: release-please
+    if: contains(needs.release-please.outputs.paths_released, '.')
+    environment:
+      name: pypi
+      url: https://pypi.org/p/zarr-particle-tools
+    permissions:
+      id-token: write # IMPORTANT: this permission is mandatory for trusted publishing
+    steps:
+      - name: Checkout ref branch
+        uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd
+        with:
+          ref: ${{ github.ref }}
+          fetch-depth: 0
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@5a7eac68fb9809dea845d802897dc5c723910fa3
+        with:
+          version: "0.7.13"
+          python-version: "3.12"
+
+      - name: build
+        run: |
+          uv build
+
+      - name: Publish distribution 📦 to PyPI
+        uses: pypa/gh-action-pypi-publish@ed0c53931b1dc9bd32cbe73a98c7f6766f8a527e
+        with:
+          packages-dir: dist

zarr_particle_tools-0.3.4/.gitignore

@@ -0,0 +1,219 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# analysis results
+mrc_comparison_results*/
+
+# test output files
+tests/output/
+
+# test data (input) files
+tests/data/
+
+# demo scripts and whatnot 
+demo/

zarr_particle_tools-0.3.4/.pre-commit-config.yaml

@@ -0,0 +1,12 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.12.10
+    hooks:
+      - id: ruff
+        args: [--fix, --exit-non-zero-on-fix]
+        types_or: [python, pyi]
+
+  - repo: https://github.com/psf/black
+    rev: 25.1.0
+    hooks:
+      - id: black

zarr_particle_tools-0.3.4/.release-please.manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.3.4"
+}

zarr_particle_tools-0.3.4/CHANGELOG.md

@@ -0,0 +1,54 @@
+# Changelog
+
+## [0.3.4](https://github.com/czimaginginstitute/zarr-particle-tools/compare/zarr-particle-tools-v0.3.3...zarr-particle-tools-v0.3.4) (2025-11-17)
+
+
+### 🐞 Bug Fixes
+
+* Remove CCPEM-pipeliner extra dependency. ([#16](https://github.com/czimaginginstitute/zarr-particle-tools/issues/16)) ([1ca9f32](https://github.com/czimaginginstitute/zarr-particle-tools/commit/1ca9f3260bc47613caba2f90efb4d64433bccba2))
+
+## [0.3.3](https://github.com/czimaginginstitute/zarr-particle-tools/compare/zarr-particle-tools-v0.3.2...zarr-particle-tools-v0.3.3) (2025-11-17)
+
+
+### 🧹 Miscellaneous Chores
+
+* Enable publishing workflow for PyPI ([#14](https://github.com/czimaginginstitute/zarr-particle-tools/issues/14)) ([3b1fa32](https://github.com/czimaginginstitute/zarr-particle-tools/commit/3b1fa32e61150e758adc92bd79e6d2966c4546b5))
+
+## [0.3.2](https://github.com/czimaginginstitute/zarr-particle-tools/compare/zarr-particle-tools-v0.3.1...zarr-particle-tools-v0.3.2) (2025-11-17)
+
+
+### 🧹 Miscellaneous Chores
+
+* Address medium security vulnerabilities. ([#11](https://github.com/czimaginginstitute/zarr-particle-tools/issues/11)) ([bdd500b](https://github.com/czimaginginstitute/zarr-particle-tools/commit/bdd500b5a0ac668169544d8d3dad7fa125af8147))
+
+## [0.3.1](https://github.com/czimaginginstitute/zarr-particle-tools/compare/zarr-particle-tools-v0.3.0...zarr-particle-tools-v0.3.1) (2025-11-17)
+
+
+### 🐞 Bug Fixes
+
+* add CONTRIBUTING.md ([#8](https://github.com/czimaginginstitute/zarr-particle-tools/issues/8)) ([d1a6a07](https://github.com/czimaginginstitute/zarr-particle-tools/commit/d1a6a071c10ba2a48c973dda187155d6220957f2))
+* use caching for pytest only on main ([#7](https://github.com/czimaginginstitute/zarr-particle-tools/issues/7)) ([c2f7f99](https://github.com/czimaginginstitute/zarr-particle-tools/commit/c2f7f99218f145fac2f5ca2e6e3671cf431de506))
+
+## [0.3.0](https://github.com/czimaginginstitute/zarr-particle-tools/compare/zarr-particle-tools-v0.2.0...zarr-particle-tools-v0.3.0) (2025-11-14)
+
+
+### ✨ Features
+
+* add rich logging, minor README updates, add tests & bugfix extraction from data portal ([#4](https://github.com/czimaginginstitute/zarr-particle-tools/issues/4)) ([b9feb7e](https://github.com/czimaginginstitute/zarr-particle-tools/commit/b9feb7e90464dfb33e09e7650b319ecb849ba624))
+
+
+### 🐞 Bug Fixes
+
+* pytest caching ([#5](https://github.com/czimaginginstitute/zarr-particle-tools/issues/5)) ([8102fd9](https://github.com/czimaginginstitute/zarr-particle-tools/commit/8102fd9297085fafcfb912f1cba7c44a90ec3f5e))
+
+## [0.2.0](https://github.com/czimaginginstitute/zarr-particle-tools/compare/zarr-particle-tools-v0.1.0...zarr-particle-tools-v0.2.0) (2025-11-14)
+
+
+### ✨ Features
+
+* setup ci/cd pytest and improve tests ([#2](https://github.com/czimaginginstitute/zarr-particle-tools/issues/2)) ([552c2ad](https://github.com/czimaginginstitute/zarr-particle-tools/commit/552c2ad1a51eed3ba637cd68524c542d00c97b37))
+
+
+### 🧹 Miscellaneous Chores
+
+* add RP, prep for open source ([#1](https://github.com/czimaginginstitute/zarr-particle-tools/issues/1)) ([add0ae1](https://github.com/czimaginginstitute/zarr-particle-tools/commit/add0ae1ba0ba1ff3b93751b153ae18ec344e492f))

zarr_particle_tools-0.3.4/CONTRIBUTING.md

@@ -0,0 +1,159 @@
+# Contributing to zarr-particle-tools
+
+Thank you for your interest in contributing to zarr-particle-tools! This document provides guidelines and instructions for contributing to the project.
+
+## Ways to Contribute
+
+There are many ways to contribute to zarr-particle-tools:
+
+- **Report bugs**: Open an issue describing the bug and how to reproduce it
+- **Suggest features**: Open an issue describing the feature you'd like to see
+- **Improve documentation**: Fix typos, clarify instructions, or add examples
+- **Write tests**: Increase test coverage or add tests for edge cases
+- **Fix bugs**: Submit a pull request fixing an open issue
+- **Add features**: Implement new functionality or address limitations listed in the README
+
+## Getting Started
+
+### Development Setup
+
+1. **Fork and clone the repository**:
+   ```bash
+   git clone git@github.com:YOUR-USERNAME/zarr-particle-tools.git
+   cd zarr-particle-tools
+   ```
+
+2. **Create a conda environment** (recommended):
+   ```bash
+   conda create -n zarr-particle-tools-dev python=3.12
+   conda activate zarr-particle-tools-dev
+   pip install uv
+   ```
+
+3. **Install the package in development mode**:
+   ```bash
+   uv pip install -e .[dev]
+   ```
+
+4. **Set up pre-commit hooks**:
+   ```bash
+   pre-commit install
+   ```
+
+   This will automatically run code formatters and linters before each commit.
+
+### Download Test Data (Optional)
+
+To run the full test suite, you'll need to download the test data:
+
+```bash
+mkdir -p tests/data
+cd tests/data
+
+# Download test data from Zenodo
+curl -L --fail --retry 5 --retry-delay 5 --continue-at - \
+  -o zarr_particle_tools_test_data_large.tar.gz \
+  "https://zenodo.org/records/17338016/files/zarr_particle_tools_test_data_large.tar.gz?download=1"
+curl -L --fail --retry 5 --retry-delay 5 --continue-at - \
+  -o zarr_particle_tools_test_data_small.tar.gz \
+  "https://zenodo.org/records/17338016/files/zarr_particle_tools_test_data_small.tar.gz?download=1"
+
+# Extract
+for f in *.tar.gz; do tar -xzf "$f"; done
+```
+
+## Development Workflow
+
+### Making Changes
+
+1. **Create a new branch** for your changes:
+   ```bash
+   git checkout -b your-feature-branch
+   ```
+
+2. **Make your changes** following the code style guidelines below
+
+3. **Run tests** to ensure your changes don't break existing functionality:
+   ```bash
+   pytest
+   ```
+
+4. **Commit your changes** with a clear, descriptive commit message:
+   ```bash
+   git add .
+   git commit -m "Add feature X" -m "Detailed description of changes"
+   ```
+
+5. **Push to your fork**:
+   ```bash
+   git push origin your-feature-branch
+   ```
+
+### Code Style
+
+This project uses automated code formatting and linting tools:
+
+- **[Black](https://black.readthedocs.io/)**: Code formatter with line length 120
+- **[Ruff](https://docs.astral.sh/ruff/)**: Fast Python linter
+
+Pre-commit hooks will automatically format your code when you commit. You can also run these tools manually:
+
+```bash
+# Format code with Black
+black src/ tests/
+
+# Run Ruff linter
+ruff check src/ tests/ --fix
+```
+
+### Code Guidelines
+
+- Follow PEP 8 style guidelines (enforced by Ruff)
+- Write clear, descriptive variable and function names
+- Add docstrings to all public functions and classes
+- Keep functions focused and modular
+- Add type hints where appropriate
+- Comment complex logic or algorithms
+
+### Testing
+
+- Write tests for new features or bug fixes
+- Place tests in the `tests/` directory
+- Run the test suite with `pytest`
+- Run tests in parallel with `pytest -n auto` (requires pytest-xdist)
+- Ensure all tests pass before submitting a pull request
+
+The test suite compares output with RELION 5.0 to ensure numerical precision. Different tolerance levels are used for:
+- float16 data (relaxed tolerance due to reduced precision)
+- Experimental data (relaxed tolerance due to noise)
+
+### Documentation
+
+- Update the README.md if you add new features or change existing behavior
+- Add examples for new command-line options
+- Update docstrings for modified functions
+- Add entries to CHANGELOG.md for notable changes
+
+## Submitting a Pull Request
+
+1. **Ensure your code passes all tests** and follows the code style guidelines
+2. **Update documentation** as needed
+3. **Push your changes** to your fork
+4. **Open a pull request** against the `main` branch of the main repository
+5. **Describe your changes** in the pull request description:
+   - What problem does it solve?
+   - What changes did you make?
+   - Are there any breaking changes?
+   - Have you added tests?
+
+## Code of Conduct
+
+This project adheres to the Contributor Covenant [code of conduct](https://github.com/chanzuckerberg/.github/blob/main/CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [opensource@chanzuckerberg.com](mailto:opensource@chanzuckerberg.com).
+
+## Security Issues
+
+If you believe you have found a security issue, please responsibly disclose by contacting us at [security@chanzuckerberg.com](mailto:security@chanzuckerberg.com). Do not open a public issue.
+
+## License
+
+By contributing to zarr-particle-tools, you agree that your contributions will be licensed under the [MIT License](LICENSE).

zarr_particle_tools-0.3.4/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Chan Zuckerberg Imaging Institute (CZII)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.