Frequently asked questions
What is the fastest way to try Chipper with my data?
Add the instrument, then upload one or more representative files from Investigate → Log Files. Start with a file whose outcome is already known so you can validate the parsed activity.
Can I upload multiple files at once?
Yes. Every file must be assigned to an instrument, use an extension permitted for that instrument type, and be no larger than 48 MiB.
When should I use the Log Collector instead?
Use the collector for logs written on a Windows instrument PC, especially files that grow while a run is in progress. Use an existing cloud source when logs already land in AWS S3, Azure Blob Storage, or Google Cloud Storage.
Why is a processed file showing zero events?
The file can be valid even when no enabled rule matches it. Check that the file is attributed to the right instrument type, then open Configure → Rules → Rules Library and enable the relevant rules.
When do methods and runs appear?
Chipper can identify basic method activity and reconstruct runs before a process model is trained. Availability depends on the instrument data and account configuration.
Why does a run say “Not scored”?
The run does not yet have a process-model verdict. Its identity, method, instrument, timing, outcome, events, and files can still be useful for investigation.
How much history does a process model need?
A tuned process model generally needs around three months of repeated run history, depending on method frequency and data quality. Basic ingestion and observability begin sooner.
Does every event create an alert?
No. Monitoring-only rules create events without alerts. Add an alerting condition to a rule, or enable alerting on an SPC control, when a signal needs a response.
What is the difference between a rule threshold and SPC?
A rule threshold evaluates a deterministic event, duration, count, or value boundary. SPC evaluates how a numeric measurement behaves relative to a statistical baseline and selected pattern rules.
Does Chipper replace our LIMS or ELN?
No. Chipper is a read-only observability and process-intelligence layer that complements systems of record and instrument control software.
Can Chipper control or schedule instruments?
No. Chipper does not currently control instruments, trigger protocols, or schedule work between devices.