bbtoolsflver-sdm --input data.fastq --filter-quality 30 After the conversion and install, validate that the filter version loads correctly. Validation Test sdm query --pkg=bbtoolsflver # Expected output: STATUS: INSTALLED | VERSION: flver-1.0.0 Run a functional test:
chmod +x /usr/local/bin/bbtoolsflver-sdm Now, within your SDM workflow, call: bbtoolsflver to sdm install
For more advanced use (e.g., integrating with Ansible or Puppet), use the SDM’s local repository feature — serve your converted .deb or .rpm via a simple HTTP server and point the SDM to that URL. This ensures that bbtoolsflver becomes a first-class citizen in your automated infrastructure. Article last updated: October 2025. For specific troubleshooting, consult the BBMap Google Group or your SDM vendor documentation. bbtoolsflver-sdm --input data
# Using WiX: heat directory, candle, light heat dir bbtoolsflver -gg -sfrag -out bbtoolsflver.wxs candle bbtoolsflver.wxs light bbtoolsflver.wixobj -o bbtoolsflver.msi # Import MSI into SCCM as an Application. The key challenge with bbtoolsflver is ensuring SDM recognizes the filter flag when calling BBTools. Article last updated: October 2025
Remember: always verify the filter version with --help after installation. If the SDM still fails to recognize the flag, you likely need to symlink the old filter binary to a standard name (e.g., ln -s /opt/bbtoolsflver/filter_fl /usr/local/bin/filter ).
