Repository navigation
fp-tools v0.2.8
Windows single-cell limitation found during post-release validation: per-cell analysis can fail when a fragment index (.tbi) is present and pysam is unavailable in the Windows bundle. Group-level analysis completed, but the new PBMC tutorial's per-cell stage exposed this error. Upgrade to v0.2.9, which passed the complete tutorial through both published desktop applications. The existing v0.2.8 artifacts have not been replaced.
fp-tools v0.2.8 corrects command documentation and makes the first analysis easier to follow.
- Corrected the documented aggregate CSV export flags and shared-axis help. Clarified that single-cell AnnData inputs need genomic-bin counts, matching barcodes, and a selected-feature mask.
- Added platform-specific checksum and Python-environment instructions, shell guidance, and clearer GUI launch instructions. Docker examples bind the GUI to localhost and use a release-pinned source version.
- Made the ENCODE helper check dependencies before downloading, support macOS checksums, reuse verified files, and resume interrupted downloads.
- Fixed the package-description logo URL, rewrote the summary for researchers, added a practical glossary, and renamed “API Reference” to “Command reference” while preserving URLs.
- Added a complete 14.3 MB real PBMC chromosome-22 tutorial: 300 cells, matched count matrix and fragments, hg38 reference, blacklist, regions, portable YAML, provenance, and checksums. Download
fp-tools-pbmc-chr22-demo-v1.zipand its.sha256file below.
Production scientific methods and defaults are unchanged. The PBMC subset demonstrates execution; it does not validate binding or reproduce the larger PBMC figures. Research-branch methods and manuscript files are not included.
Install with python -m pip install --upgrade fp-tools-bio==0.2.8, or download the Windows executable or Apple Silicon DMG. Verify desktop downloads against SHA256SUMS.txt; the tutorial, runtime, and container archives have separate checksums.
Local validation: 633 tests passed, one skipped; 30 documentation/helper tests and 34 release/runtime tests passed. Strict documentation builds, the 33-page browser audit at three viewport sizes, console checks, 18 YAML dry runs, and package metadata checks passed. The complete real PBMC workflow and resume passed on Linux.