Allows software operation without a connected spectrometer, useful for training and method development.

By understanding the structure of the manual—installation, interface, collection, processing, quantitation, automation, compliance, and troubleshooting—you unlock the full potential of your FTIR spectrometer. Whether you are a novice learning baseline correction or a seasoned administrator configuring 21 CFR Part 11 compliance, the Omnic 9 manual (and this comprehensive guide to using it) will remain your most trusted lab companion.

| Feature | How to enable | Practical tip | |---------|---------------|---------------| | | Right‑click a Transform block → Suggest Clean‑Up . | Review the auto‑generated Python snippet before committing; you can edit it directly in the block. | | Custom Plug‑in Development | Install the Omnic‑SDK ( npm i -g omnic-sdk ). Use omnic new-plugin my‑widget . | Keep plug‑ins stateless; any state should be persisted via the platform’s Key‑Value Store for scaling. | | Data Lineage Export | In the Lineage tab → Export Graph (GraphML) . | Import the GraphML into Gephi or Neo4j for deeper impact analysis. | | Scheduled Back‑Fill | In Pipeline Settings → Triggers choose Event‑Driven → File Arrival and enable Back‑fill (last 30 days) . | Useful when new sensors are added mid‑month – the system will retroactively fetch historic data if the source supports it. | | High‑Availability Deployment | Use the Omnic‑Cluster Helm chart on Kubernetes ( helm install omnic9 ./chart ). | Set replicaCount: 3 and configure a persistent volume for the audit log to avoid data loss. |

Before you test a sample, you must clear out any interference from the room's air.

Navigate to Experiment Setup > Bench and lower the gain setting or add an optical aperture filter.